Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

{
  "mcpServers": {
    "x402-doctor": {
      "type": "http",
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp"
    }
  }
}

claude mcp add --transport http x402-doctor https://x402-doctor.tsharpe.workers.dev/mcp

[mcp_servers.x402-doctor]
url = "https://x402-doctor.tsharpe.workers.dev/mcp"

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "x402-doctor": {
      "type": "remote",
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp",
      "enabled": true
    }
  }
}

{
  "mcpServers": {
    "x402-doctor": {
      "type": "http",
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=x402-doctor&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8veDQwMi1kb2N0b3IudHNoYXJwZS53b3JrZXJzLmRldi9tY3AifQ%3D%3D"
}

{
  "servers": {
    "x402-doctor": {
      "type": "http",
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "x402-doctor": {
      "httpUrl": "https://x402-doctor.tsharpe.workers.dev/mcp"
    }
  }
}

extensions:
  "x402-doctor":
    enabled: true
    name: "x402-doctor"
    type: streamable_http
    uri: "https://x402-doctor.tsharpe.workers.dev/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2024-11-05; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene71 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
fail
tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: probe_x402_endpoint (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_checks (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); explain_defect (readOnlyHint, destructiveHint, idempotentHint, openWorldHint)
pass
tools.token_costabout 292 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

3 tools, about 292 tokens to load them all · tool set 5bb6902a60eb · checked 2026-10-19 10:52 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 92 / 100

provenance85

liveness99

freshness85

hygiene100

+repository +dns-namespace +website +reachable +uptime-96% ~updated-63d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://x402-doctor.tsharpe.workers.dev/mcp` streamable-http	none	yes	96%	128 ms	2024-11-05	2026-10-19

Tools (3)

`explain_defect`	Full explanation of one rule by id — what it checks, why it matters, how to fix it, and where the rule came from. Use when you want the reasoning without re-probing.
`list_checks`	The whole rule table. Knowing what was NOT checked is part of knowing what a clean result means.
`probe_x402_endpoint`	Probe an x402 seller endpoint and report what it observes about it. Performs the handshake a paying client would: GET with no X-PAYMENT header, then checks the 402 challenge against 16 rules. Every finding says whether the rule comes from the x402 spec or from an observed facilitator rejection. Reports status "healthy" (nothing to report), "advisories" (only warn/info findings — the endpoint works), "defects_found" (at least one error-severity finding), "not_x402" or "unreachable".

Schemas: list_tools.

Also listed as

1 other active names share this repository: com.twelvepermissions/twelve-permissions

Similar MCP servers

More from com.twelvepermissions

Official server.json

{
  "name": "com.twelvepermissions/x402-doctor",
  "title": "x402 Doctor",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/tsharpe2282-web/twelve-permissions",
    "source": "github",
    "subfolder": "doctor"
  },
  "websiteUrl": "https://x402-doctor.tsharpe.workers.dev",
  "description": "Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it."
}