x402-doctor
MCP serverDev toolsDiagnose x402 seller endpoints: what is wrong with your 402 challenge, and how to fix it.
Available today. Use it from your connected AI after setup.
No other account needed.
Add ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.
Then ask your AI: use the probe x402 endpoint tool from x402-doctor
Install x402-doctor
The server’s own address, for the clients that take one directly. Or connect ahel onceand every client you use reads it from one address, with the account kept on ahel rather than in each client’s config.
Claude Code
claude mcp add --transport http --scope user x402-doctor 'https://x402-doctor.tsharpe.workers.dev/mcp'Run it once in your project, then open /mcp to approve any sign-in the server asks for.
Claude Desktop
https://x402-doctor.tsharpe.workers.dev/mcpAdd a custom connector in Settings, paste this address, and approve the sign-in.
Cursor
cursor://anysphere.cursor-deeplink/mcp/install?name=x402-doctor&config=eyJ1cmwiOiJodHRwczovL3g0MDItZG9jdG9yLnRzaGFycGUud29ya2Vycy5kZXYvbWNwIn0=Open the link and Cursor adds the server at that address.
ChatGPT
https://x402-doctor.tsharpe.workers.dev/mcpIn Settings, enable Developer mode, create an MCP app, and paste this address. Your plan and workspace must allow custom apps.
Codex
codex mcp add x402-doctor --url 'https://x402-doctor.tsharpe.workers.dev/mcp'Run it once, then sign in with codex mcp login x402-doctor if the server asks for an account.
From the project's README
As published by tsharpe2282-web/twelve-permissions in README.md. This repository publishes several servers, so only the opening is shown here.
Twelve NFTs on XRP Ledger mainnet. Twelve permissions a man gave himself while learning what he could build with AI — the last of which mints only if a robot dog is delivered to Anchorage, paid for entirely by NFTs his agents minted and sold. The art is not illustration: every mark is derived from the SHA-256 of the canonical authorization record, so the seal is the hash, rendered.
This repository exists so you don't have to take any of that on trust. It holds the generator, the canonical records, and the server source. Re-run them yourself.
Collection: https://twelvepermissions.com/
Issuer: rHEiuaYLNQ4UdLqeUrnE9AwEHqsDMr9g9R (taxon 12, 5% royalty)
Verify a seal from first principles
No dependencies. Node only.
node generate.js # regenerates every seal from events.json
git status # should report no changes
The second line is the test. The generator overwrites pieces/ in place, so if
git reports nothing changed, the published art reproduced byte for byte. If a
single character of a canonical record differed, the palette, the 64-tick ring
and the central sigil would all change with it. Forging a seal means breaking
SHA-256.
Shortened here. Read the whole README on GitHub.
Tools it offers (3)
What this server listed when ahel dialed its public endpoint in Sep 2026, with no key and no account of yours. The names are the server’s own.
probe_x402_endpointexplain_defectlist_checks
Signals
- Last commit
- Sep 2026
Advanced
- Delivery
- x402-doctor MCP server → your ahel connector (mcp.ahel.ai) → your AI.
- Item type
- mcp-server
- Key
com-twelvepermissions-x402-doctor- Source
- github.com/tsharpe2282-web/twelve-permissions
- Hosted endpoint
https://x402-doctor.tsharpe.workers.dev/mcp