Other · Remote MCP server
x402 Doctor
Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.twelvepermissions/x402-doctor- Version
- 1.0.0
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-08-17
- Updated
- 2026-08-17
- Publisher
- com.twelvepermissions · 2 servers with pages here
- Namespace
- Namespace verified by the MCP Registry via the domain twelvepermissions.com · how
- Website
- x402-doctor.tsharpe.workers.dev
- Repository
- github.com/tsharpe2282-web/twelve-permissions (folder doctor)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://x402-doctor.tsharpe.workers.dev/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- x402-doctor 1.0.0 · protocol 2024-11-05
- Tools discovered
- 3:
probe_x402_endpoint,explain_defect,list_checks - Checked on
- 2026-10-05
How to connect x402 Doctor
x402 Doctor is a remote MCP server: there is nothing to install. Its endpoint is https://x402-doctor.tsharpe.workers.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from com.twelvepermissions
| Server | Runs |
|---|---|
| Twelve PermissionsBrowse, verify and buy Twelve Permissions NFTs on XRP Ledger. Every claim is checkable. | Remote · HTTPLive check: ✓ handshake |
More other servers
| Server | Runs |
|---|---|
| X02 File HostingUpload, find, organize and share files on your X02 account with scoped, revocable access. | Remote · HTTPLive check: sign-in required |
| x402 Bazaar Listing MonitorChecks x402 Bazaar resource listings against the public discovery catalog and flags drops. | Remote · HTTPLive check: ✓ handshake |
| X402 Bazaar MCPCheck, then act, on Base and NEAR: token-safety gates, then swaps at price - over x402. | Local · stdio |
| x402 Discovery MCPDiscover x402 APIs by capability, price & trust. Powered by x402Scout. | Remote · SSELive check: ✗ no handshake |
| x402 Market Intelligence + Russian Web AccessCheck x402 endpoints before paying: liveness, price history, farm detection. Plus RU web access. | Remote · HTTPLive check: ✓ handshake |
| X402 MCPPay for HTTP APIs and charge for your own: x402 micropayments in USDC on Base. | Remote · HTTPLive check: ✓ handshake |
| X402 MCP ServerPay-per-call x402 tools on Base: web extract/render, burn-once secret vault, chart, GeoTIFF. | Local · stdio |
| X402 MCP ServerJMT x402: 35 pay-per-call Base/USDC tools for agents, auto-paid via x402 v2. No API key. | Local · stdio |