Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
Connect Remote server
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"
}
}
}
{
"servers": {
"x402-doctor": {
"type": "http",
"url": "https://x402-doctor.tsharpe.workers.dev/mcp"
}
}
}
Settings > Connectors > Add custom connector
URL: https://x402-doctor.tsharpe.workers.dev/mcp
Tools 3 found in our last check
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 facili…
explain_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.
Details
| Endpoint | https://x402-doctor.tsharpe.workers.dev/mcp (Streamable HTTP) |
| First published | 17 Aug 2026 |
| Last updated | 17 Aug 2026 |
| Registry name | com.twelvepermissions/x402-doctor |
More other servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
