X402 Doctor MCP server
{
"mcpServers": {
"twelvepermissions-x402-doctor": {
"type": "http",
"url": "https://x402-doctor.tsharpe.workers.dev/mcp"
}
}
}{
"mcpServers": {
"twelvepermissions-x402-doctor": {
"type": "http",
"url": "https://x402-doctor.tsharpe.workers.dev/mcp"
}
}
}{
"mcpServers": {
"twelvepermissions-x402-doctor": {
"type": "http",
"url": "https://x402-doctor.tsharpe.workers.dev/mcp"
}
}
}{
"servers": {
"twelvepermissions-x402-doctor": {
"type": "http",
"url": "https://x402-doctor.tsharpe.workers.dev/mcp"
}
}
}{
"mcpServers": {
"twelvepermissions-x402-doctor": {
"type": "http",
"url": "https://x402-doctor.tsharpe.workers.dev/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.0
What it does
X402 Doctor is a diagnostic tool for testing HTTP 402 Payment Required endpoints. It checks seller-side x402 implementations against specification requirements and known failure modes, reporting what is wrong and how to fix it.
- Test your 402 payment endpoint to ensure it complies with the x402 specification and common implementation patterns.
- Debug why a payment facilitator is rejecting your 402 challenge responses.
- Verify that your endpoint follows best practices for HTTP headers, schema validation, and payment requirement formatting.
Tools this server exposes
| Tool | Does |
|---|---|
| probe | Sends a test handshake to a 402 endpoint and reports compliance issues with fixes. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.