Diagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it. Connect the official x402 Doctor MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http x402-doctor https://x402-doctor.tsharpe.workers.dev/mcpRun in your terminal, then restart Claude Code.
x402 Doctor · https://x402-doctor.tsharpe.workers.dev/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “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 head.”
“Use “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 reas.”
“Use “list_checks”: The whole rule table. Knowing what was NOT checked is part of knowing what a clean result means.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how x402 Doctor holds up.
Operated by x402 Doctor (workers.dev) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If x402 Doctor adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose x402 Doctor in the gate directory. No sign-in needed.
x402 Doctor's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
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 head
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 reas
list_checks — The whole rule table. Knowing what was NOT checked is part of knowing what a clean result means.
https://x402-doctor.tsharpe.workers.dev/mcpYes — x402 Doctor operates its own remote MCP server at x402-doctor.tsharpe.workers.dev. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick x402 Doctor in the directory. No account or sign-in is needed. From then on, x402 Doctor's tools are available in every client you've connected to gate.
No. x402 Doctor runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect x402 Doctor in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up x402 Doctor in: Claude · Claude Code · ChatGPT · Cursor · VS Code