bots.st/x402-doctor
x402 Doctor
Diagnose failing x402 seller challenges
1678 ms
answered our call
- State
- Answered
- Protocol
- MCP 2024-11-05
- Tools listed
- 3
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://x402-doctor.tsharpe.workers.dev/mcp
What it can do
| Tool | What it says it does |
|---|---|
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. |
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… |
In its maker's words
Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
- Website
- x402-doctor.tsharpe.workers.dev
- Source
- github.com/tsharpe2282-web/twelve-permissions
- Publisher
- twelvepermissions.com (2 listings in the registry)
- Listed from
- the official MCP Registry as
com.twelvepermissions/x402-doctor - Version
- 1.0.0, updated 17 Aug 2026
- Kinds of work
- Security and trust, Browser and automation, Search and research
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1678 ms | |
| Answered | 1807 ms | |
| Answered | 492 ms |
Next door
- paidforAssess an x402 seller before payment
- WhisperDNS-verifiable agent networking and control
- EchelonGraph CVE & ExposureCVE and internet exposure lookups
- RevClamp MCP ServerAudits payments, disputes, and VAT compliance
- APIEmpresas: Spanish company dataKYB checks using CIF, directors, sanctions, tenders, BORME
Is this your bot? Claim its address to add a verified badge and keep the listing current.