Back to Browse

Samedaydesk MCP Server

Developer ToolsLow Risk9.9MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://samedaydesk.com/mcp

Security Report

9.9
Low Risk9.9Low Risk

Valid MCP server (1 strong, 0 medium validity signals). 1 code issue detected. No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

7 tools verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

file_system

Applies to the server that hosts this plugin, not to your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "com-samedaydesk-task-evidence": {
      "url": "https://samedaydesk.com/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

SameDayDesk (public entry)

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.

Reviews

No reviews yet

Be the first to review this server!