NestDaddy

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.

Connect Remote server

Terminal
claude mcp add --transport http x402-doctor https://x402-doctor.tsharpe.workers.dev/mcp
~/.cursor/mcp.json
{
  "mcpServers": {
    "x402-doctor": {
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "x402-doctor": {
      "type": "http",
      "url": "https://x402-doctor.tsharpe.workers.dev/mcp"
    }
  }
}
Claude Desktop
Settings > Connectors > Add custom connector
URL: https://x402-doctor.tsharpe.workers.dev/mcp

Tools 3 found in our last check

  • 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 facili…

  • 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.

Details

Endpointhttps://x402-doctor.tsharpe.workers.dev/mcp (Streamable HTTP)
First published17 Aug 2026
Last updated17 Aug 2026
Registry namecom.twelvepermissions/x402-doctor

More other servers See all

Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.