All servers · Agent payments (x402)
x402 Doctor
com.twelvepermissions/x402-doctor · v1.0.0
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2024-11-05 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
Connect
streamable-http · https://x402-doctor.tsharpe.workers.dev/mcp
claude mcp add --transport http x402-doctor https://x402-doctor.tsharpe.workers.dev/mcp{
"mcpServers": {
"x402-doctor": {
"url": "https://x402-doctor.tsharpe.workers.dev/mcp"
}
}
}Tools as reported by the server
probe_x402_endpointProbe 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. Repoexplain_defectFull 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_checksThe whole rule table. Knowing what was NOT checked is part of knowing what a clean result means.
Repository · Website · JSON · Text for agents · Registry updated 2026-08-17