x402 Doctor
by x402-doctor.tsharpe.workers.dev in Other
Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
https://x402-doctor.tsharpe.workers.dev/mcp
Last 30 days
- Uptime
- 100%
- Response time
- 142 ms typical, 142 ms slowest 5%
- Last check
- 7 h ago
- Next check
- any minute now
How to call it
Add it to any MCP client that supports remote servers.
{
"mcpServers": {
"x402-doctor": {
"type": "http",
"url": "https://x402-doctor.tsharpe.workers.dev/mcp"
}
}
}3 tools
- 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 facilit
- 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.
Security scan
- No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time |
|---|---|---|---|
| 7 h ago | Passed | 200 | 142 ms |