SameDayDesk (public entry)

MCP serverProductivity

Readiness checks, a paid Fix Pack, TaskMarket reads, and caller-declared funnel evidence.

Then ask your AI: use SameDayDesk (public entry) to check ai readiness

Details

Available today. Use it as a step in a pipeline you build, or from your connected AI.

Add it as a step in a pipeline you build on Ahel, or connect Ahel to Claude, ChatGPT, Cursor, Claude Code or Codex and ask your AI to use it.

Install SameDayDesk (public entry)

The server’s own address, for the clients that take one directly. Or connect Ahel once and every client you use reads it from one address, with the account kept on Ahel rather than in each client’s config.

  • Claude Code

    claude mcp add --transport http --scope user samedaydesk-public-entry 'https://samedaydesk.com/mcp'

    Run it once in your project, then open /mcp to approve any sign-in the server asks for.

  • Claude Desktop

    https://samedaydesk.com/mcp

    Add a custom connector in Settings, paste this address, and approve the sign-in.

  • Cursor

    cursor://anysphere.cursor-deeplink/mcp/install?name=samedaydesk-public-entry&config=eyJ1cmwiOiJodHRwczovL3NhbWVkYXlkZXNrLmNvbS9tY3AifQ==

    Open the link and Cursor adds the server at that address.

  • ChatGPT

    https://samedaydesk.com/mcp

    In Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.

  • Codex

    codex mcp add samedaydesk-public-entry --url 'https://samedaydesk.com/mcp'

    Run it once, then sign in with codex mcp login samedaydesk-public-entry if the server asks for an account.

From the project's README

As published by epistemedeus/samedaydesk in README.md.

Public helpers for free discovery and offline result reuse. Node 22.x. The commands below use plain ESM under tools/; no npm install is required.

Start with the examples below, then open the helper documentation for options and error handling.

Docs (in-repo)

DocPurpose
tools/presence/FOR-AGENTS-COLD-READ.mdFree discovery when apex TLS/connect fails
tools/presence/REGISTRY-CONSUMER.mdMCP Registry version=latest pitfall
tools/result-reuse/README.mdOffline source → task-memory observation
tools/offer-routing/README.mdTask → existing SameDayDesk/Neomorphic offer
tools/offer-routing/capability-limits-matrix.jsonMachine-readable capability/limits matrix

Live free catalogs (no pay): https://agents.samedaydesk.com/llms.txt and https://agents.samedaydesk.com/.well-known/skills/index.json. Apex https://samedaydesk.com/for-agents may TLS/connect-fail; cold-read falls back to those alternates.

Free / live vs offline fixtures

ModeNetworkPaymentHow
Offline fixture cold-readnonenonepreferFixture: true → outcome: "offline_fixture"
Live cold-readfree HTTP onlynonedefault resolve → often alternate_live when apex fails
Result-reuse preview/exportnone (local JSON)nonefixtures + --opt-in to write

These helpers do not require a purchase. Paid extract/batch routes are separate.

Exact commands (clean checkout)

From the repository root (no install):

1. Offline cold-read (no network)

node --input-type=module -e 'import {resolveForAgentsColdRead} from "./tools/presence/for-agents-cold-read.mjs"; console.log(JSON.stringify(await resolveForAgentsColdRead({preferFixture:true}), null, 2))'

Expected: outcome: "offline_fixture", paid: false, liveObserved: false.

2. Live cold-read (free HTTP only; optional)

node --input-type=module -e 'import {resolveForAgentsColdRead} from "./tools/presence/for-agents-cold-read.mjs"; console.log(JSON.stringify(await resolveForAgentsColdRead(), null, 2))'

Expected when apex transport fails but agents.* respond: outcome: "alternate_live", paid: false.

3. Result-reuse preview and export on in-repo fixtures

PILOT_EXAMPLE_DIR="$(mktemp -d)"
NOW="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
node tools/result-reuse/cli.mjs preview \
  --input tools/result-reuse/fixtures/accepted-page-change.json \
  --task-id vendor-watch --subject vendor-page-result --sequence 1 --clock "$NOW"

node tools/result-reuse/cli.mjs export \
  --input tools/result-reuse/fixtures/accepted-page-change.json \
  --task-id vendor-watch --subject vendor-page-result --sequence 1 --clock "$NOW" \
  --opt-in --out "$PILOT_EXAMPLE_DIR/reuse-observation.json"
printf 'Saved example in %s\n' "$PILOT_EXAMPLE_DIR"

Record-kind fixture:

PILOT_EXAMPLE_DIR="$(mktemp -d)"
NOW="$(date -u +%Y-%m-%dT%H:%M:%SZ)"
node tools/result-reuse/cli.mjs export \
  --input tools/result-reuse/fixtures/accepted-record-report.json \
  --task-id vendor-watch --subject record-export --sequence 1 --clock "$NOW" \
  --opt-in --out "$PILOT_EXAMPLE_DIR/reuse-record-observation.json"
printf 'Saved example in %s\n' "$PILOT_EXAMPLE_DIR"

Expected written observation: schema: "neomorphic.task-memory.observation.v1"; export requires --opt-in plus caller clock/task/subject/sequence.

Task → existing offer (cold selection)

When the job is known, route with the matrix before paying or treating a sample as live:

node tools/offer-routing/route-job.mjs tools/offer-routing/fixtures/complete-issue-discussion.job.json

Expected: ok: false, selected: null, exit code 2 and complete_issue_acquisition_unavailable. Neither paid /extract nor task-kit packaging acquires a complete discussion. This matrix does not advertise the pending issue-evidence acquisition pack. For historical fixture composition use fixtures/supplied-issue-brief.job.json under tools/offer-routing/. The MoltJobs SDK pack runs a disposable local HTTP rehearsal; its shipped runner refuses --live, even with credentials. Hosted archives are downloads, not hosted job execution. Routing does not evaluate acceptance criteria or authorize payment.

Verify the cited examples

npm run test:public-entry

That script runs the offline cold-read and fixture export commands cited above (no network, no payment). Existing focused suites: npm run test:presence, npm run test:result-reuse, npm run test:offer-routing.

Tools it offers (7)

What this server listed when Ahel dialed its public endpoint in Oct 2026, with no key and no account of yours. The names are the server’s own.

  • check_ai_readiness
  • check_agent_readiness
  • generate_complete_fix_pack
  • plan_taskmarket_delegation
  • browse_taskmarket_tasks
  • track_taskmarket_task
  • project_funnel_evidence

Signals

Last commit
Oct 2026
Advanced
Delivery
task-evidence MCP server → your Ahel connector (mcp.ahel.ai) → your AI.
Item type
mcp-server
Key
com-samedaydesk-task-evidence
Source
github.com/epistemedeus/samedaydesk
Hosted endpoint
https://samedaydesk.com/mcp