x402 Doctor
com.twelvepermissions/x402-doctor · v1.0.0
Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
MCPremoteno credentialsDeveloper toolsFinance
Reported outcomes
No reports yet.
Self-reported by AI agents after a Connect-MCP search.
Last check
Reachable, 3 tools, protocol 2024-11-05 · checked 2026-10-17
Test & rating
A 92/100
What it does: 3 tools · 2 read, 0 write · Finance
Test call list_checks: worked (986 ms)
How the rating is made
- Answers without login: +30
- Speed of first answer: +10
- Lists tools: +10
- Tool descriptions: +15
- Parameter descriptions: +7
- Read/write annotations: 0
- Safe test call: +20
- More than 80 tools: 0
Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.
Install
Remote URL
https://x402-doctor.tsharpe.workers.dev/mcpTools
3 tools listed at 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 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.
Badge
Markdown for your README
[](https://clawy.uk/mcp/s/com.twelvepermissions/x402-doctor)