com.twelvepermissions/x402-doctor · v1.0.0 · crypto-web3
x402 Doctor is healthy: it completed an MCP handshake in 1010 ms and exposes 3 tools.
Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
Endpoint: https://x402-doctor.tsharpe.workers.dev/mcp (streamable-http)
Repository · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 3 |
| Latency | 1010 ms |
| Last checked (UTC) | 2026-10-16T01:05:09.788Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-16T01:05:09.788Z | Healthy | 1010 | |
| 2026-10-14T22:35:38.290Z | Healthy | 1588 |
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. Repo |
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. |