x402 Doctor
REMOTE · X402-DOCTOR.FIZZL.EU
Is this x402/MPP API safe to pay? $0.001 preflight, fixes, a $0.25 test purchase. Free quick check.
Available components
Last scanned (20 hours ago)
Scores higher than 86% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3728 tokens (~233/item across 16 items; 16 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 0
- Tool “x402_preflight_batch” rewrote its description, which is the text the model reads security
- Tool “x402_diagnose” rewrote its description, which is the text the model reads security
- Tool “x402_preflight_deep” rewrote its description, which is the text the model reads security
- Tool “x402_delivery_check” rewrote its description, which is the text the model reads security
- Tool “x402_preflight” rewrote its description, which is the text the model reads security
- Tool “x402_fix” rewrote its description, which is the text the model reads security
- 17 Nov 26 0
- New tool “x402_facilitator_status” functional
- 14 Nov 26 0
- Tool “x402_trust_add” rewrote its description, which is the text the model reads security
- 13 Nov 26 0
- “feedback” added an optional parameter “payment” cosmetic
- “x402_preflight” added an optional parameter “pay_to” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 11 Nov 26 0
- Stability: 0.97 → pass security
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://x402-doctor.fizzl.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=x402-doctor.fizzl.eu | CN=WE1,O=Google Trust Services,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c7fa5144fa2ac47e139230d05157d3e8 |
| SANs: x402-doctor.fizzl.eu | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of x402-doctor.fizzl.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | DS published | 35926 | 8 | Verified |
| fizzl.eu. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none'; base-uri 'none'; object-src 'none' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://x402-doctor.fizzl.eu/mcp | Verified | 200 | |
| http (plaintext) | http://x402-doctor.fizzl.eu/mcp | HTTPS enforced | 301 | https://x402-doctor.fizzl.eu/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_payment_proof Check an x402 payment proof (free) ~103
Free: after paying an x402 endpoint, pass the PAYMENT-RESPONSE header it returned (X-PAYMENT-RESPONSE in v1). Returns the transaction, network and payer it names, whether that transaction exists on-chain and succeeded, and which USDC moved from whom to whom, with an explorer link. Read-only. Limited to 10 calls per hour.
| Name | Type | Req | Description |
|---|---|---|---|
| header | string | yes | The PAYMENT-RESPONSE header value (base64 JSON) |
| Name | Type | Req | Description |
|---|---|---|---|
| checks | array | – | – |
| decoded | object | – | Transaction, network and payer named in the header |
| explorer | string|null | – | Explorer link for the transaction |
| onchain | – | – | Whether the transaction exists and succeeded, and the USDC transfers |
| overall | string | yes | pass, warn or fail |
No examples provided.
concordium_badge_check Concordium badge lookup (free) ~223
Free: look up an agent in Concordium's Agent Registry (CIS-8004) by its badge, the CIS-2 token address an Agent Card carries, or by the longer Agent ID that Concordium's registry app shows. Returns whether the badge is valid (Active, the card at agent_uri hashes to the metadata_hash on chain, and that card carries this badge), the owner account (tied to a verified identity), the agent wallet, the origins the card lists, and the CIS-8 key the agent binds with the address it stands for and whether the CIS-8 registry still holds it. To check the payTos of an x402 endpoint against its seller's badge, use x402_payee_check. Read-only. Shares the free limit of 10 calls per hour.
| Name | Type | Req | Description |
|---|---|---|---|
| badge | string | yes | The badge (e.g. Mf22oVsbu3vf4Jb1cga49), its ccd:<genesis>/cis-2:<address> form, or the registry app's Agent ID |
| Name | Type | Req | Description |
|---|---|---|---|
| agentUri | string|null | – | – |
| agentWallet | string|null | – | – |
| badge | string | yes | The badge as its short CIS-2 token address (an Agent ID is turned into it) |
| card | string|null | – | match, mismatch or unread |
| card_origins | – | – | The origins the anchored card lists as the agent's own |
| external_key | – | – | The key the agent binds with CIS-8: namespace, key_type, the address it stands for, and still_bound (the CIS-8 registry still holds it for the owner) |
| issues | array | yes | Why it is not valid; empty when valid |
| network | string|null | – | mainnet or testnet, from the badge's own registry contract |
| owner | string|null | – | The owner account: a Concordium account, tied to a verified identity at the protocol level |
| status | string|null | – | – |
| tokenId | string|number|null | – | – |
| valid | boolean | yes | Active, the card at agent_uri hashes to the metadata_hash on chain, and the card carries this badge |
No examples provided.
feedback Send feedback (free) ~142
Report a bug, a missing feature or anything else about this service, in a structured way. Free. A person reads every report; nothing is run or changed automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| contact | string | – | Optional: how to reach you about it |
| endpoint | string | – | Optional: the route or tool it is about, e.g. /v1/token |
| message | string | yes | What happened or what you need |
| payment | object | – | Optional: the payment it is about, when a paid call went wrong: its transaction (with the network) or a receipt id |
| type | string | – | bug, feature (something missing) or other |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Report id, to refer to it later |
| note | string | – | – |
| received | boolean | yes | true: a person will read it |
| service | string | – | – |
| type | string | – | – |
No examples provided.
verify_receipt Verify a signed x402 Doctor answer (free) ~208
Free: check the signed receipt that every paid x402 Doctor answer carries (diagnose, preflight, batch, deep, fix, delivery check; HTTP or MCP), for example to prove later which verdict you got before paying an endpoint. Pass the whole answer as response. Returns valid, the signer and whether it is an x402 Doctor signer; with route and input also whether the receipt is for exactly that request. A changed verdict or receipt fails. Read-only, nothing is stored. Same as POST /api/v1/verify.
| Name | Type | Req | Description |
|---|---|---|---|
| input | object | – | The tool arguments you sent (MCP), or the query parameters as strings (HTTP) |
| response | object | yes | The whole paid answer as you received it, including its receipt |
| route | string | – | The request it answered: "mcp <tool name>" for an MCP answer (e.g. "mcp x402_preflight"), "GET /api/v1/preflight" for an HTTP one |
| Name | Type | Req | Description |
|---|---|---|---|
| input_matches | boolean | – | Only with route and input: whether the receipt is for exactly that request |
| known_signer | boolean|null | – | Whether that address is a current, retired or certified x402 Doctor signer |
| reason | string | – | Why it is not valid |
| signer | string | – | The address that signed it |
| signer_status | string|null | – | current, retired or certified |
| valid | boolean | yes | true: signed by an x402 Doctor signer, unchanged, and (when route and input are given) for that request |
No examples provided.
x402_delivery_check Have an x402 endpoint bought once: paid and delivered? ($0.25 via x402) ~262
Paid ($0.25 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand, Stellar or NEAR, or in RLUSD on the XRP Ledger): not a reading but a purchase. x402 Doctor buys the endpoint once (at most $0.1, USDC on Base, from its own wallet) with the example input its listing declares, checks the answer against the declared output schema, has TypeSafe's Jev judge whether it is what was paid for, and measures the charge on chain. Answers with a job id at once; follow it with x402_delivery_status (free), the result usually comes within minutes. The endpoint must get a "go" from the pre-payment check and be payable in USDC on Base; otherwise it is refused before payment. Same as GET /api/v1/delivery-check. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves later which verdict you got.
| Name | Type | Req | Description |
|---|---|---|---|
| method | string | – | HTTP method of the paid route (default: GET, then POST) |
| url | string | yes | The x402 endpoint to buy once (https, someone else's, payable in USDC on Base) |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | Only on an unpaid call: the x402 payment options |
| endpoint_price_usd | number|null | – | – |
| id | string|null | – | The job id: pass it to x402_delivery_status |
| receipt | – | – | Signed receipt (EIP-191) binding the answer to your arguments |
| status | string|null | – | queued, then done |
| status_url | string|null | – | – |
| url | string|null | – | – |
No examples provided.
x402_delivery_status Status of a delivery check (free) ~81
Free: the status of a delivery check ordered with x402_delivery_check (or GET /api/v1/delivery-check): awaiting_payment, queued or done, and once done the result: paid_and_delivered, the outcome, the charge measured on chain and the transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The job id x402_delivery_check answered with |
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| result | – | – | Once done: paid_and_delivered, result, charged_usd, transaction, cache (could a CDN serve the paid answer to callers who did not pay) |
| status | string | yes | awaiting_payment, queued or done |
| status_url | string|null | – | – |
| url | string|null | – | – |
No examples provided.
x402_diagnose Diagnose an x402 endpoint ($0.01 via x402) ~281
Paid ($0.01 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand, Stellar or NEAR, or in RLUSD on the XRP Ledger): diagnose an x402 endpoint the way a paying agent would, without paying it: the 402 challenge format, every accepts[] option, the resource URL, Solana settlement readiness, which wallets can pay, Bazaar/OpenAPI discovery and the browser paywall. Returns every check with pass/warn/fail and a fix hint. For the endpoint's owner or a developer debugging it; to decide whether to pay someone else's endpoint, use x402_preflight. Same as GET /api/v1/diagnose. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves later which verdict you got.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Example JSON request body, for a POST route that checks its input before the 402 (implies POST). Without it, {} is sent and the requestBody example in the endpoint's /openapi.json is tried. |
| method | string | – | HTTP method of the paid route (default: GET, then POST) |
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | Only on an unpaid call: the x402 payment options |
| checks | – | – | Every check with its status, message and hint |
| overall | – | – | pass, warn or fail (absent on the payment requirement) |
| receipt | – | – | Signed receipt (EIP-191) binding the answer to your arguments |
| url | string|null | – | – |
No examples provided.
x402_facilitator_status x402 facilitator status (free) ~171
Free: which public x402 facilitators (PayAI, x402.org, GoPlausible, x402.rs, Dexter, Daydreams, Semantic Pay and more) answer right now, and which networks and schemes each one settles. Give a network (CAIP-2 like eip155:8453, or an x402 v1 name like base, solana, xlayer) to get only the facilitators that settle it now. Read from each facilitator's GET /supported at most every 5 minutes; never verifies or settles anything. Use it to pick a facilitator for a new paid endpoint, or to see why payments on a network fail.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | A network to filter on, e.g. eip155:196 or xlayer |
| Name | Type | Req | Description |
|---|---|---|---|
| checked_at | string | yes | – |
| down | number | yes | – |
| facilitators | array | yes | Per facilitator: id, name, url, state (up, slow, down, not_checked), note, networks (CAIP-2, testnet flag, schemes), schemes, x402_versions, recent checks, last_up |
| network | – | – | With a network asked for: its CAIP-2 id, name, and facilitators_up (the ids that settle it right now) |
| up | number | yes | Facilitators that answered GET /supported with at least one payment kind |
No examples provided.
x402_fix Fix plan for an x402 endpoint ($0.05 via x402) ~308
Paid ($0.05 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand, Stellar or NEAR, or in RLUSD on the XRP Ledger): diagnoses your x402 endpoint, then returns per problem the concrete change as code for your stack (express, next, hono, node, python, generic), filled in with your own payTo, amount, network and route. A working endpoint gets improvements too (ERC-8004 identity, Base Builder Code, x402scan ownership proof, skill.md, browser paywall, Bazaar output schema), each with code. For the endpoint's owner: includes the diagnosis, so there is no need to call x402_diagnose first. Same as GET /api/v1/fix. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves later which verdict you got.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Example JSON request body, for a POST route that checks its input before the 402 (implies POST). Without it, {} is sent and the requestBody example in the endpoint's /openapi.json is tried. |
| method | string | – | HTTP method of the paid route (default: GET, then POST) |
| stack | string | – | Your server stack (default: detected) |
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | Only on an unpaid call: the x402 payment options |
| fixes | – | – | Each problem with steps and code for your stack |
| improvements | – | – | Not wrong, but makes the service easier to find, trust or pay: steps and code |
| overall | – | – | – |
| receipt | – | – | Signed receipt (EIP-191) binding the answer to your arguments |
| summary | string|null | – | – |
| unfixed | – | – | – |
| url | string|null | – | – |
No examples provided.
x402_payee_check ERC-8004 payee verification (free) ~349
Free: is every payTo of this x402 endpoint really its seller's? Per payment option, one outcome of the draft ERC "x402 Payee Verification for ERC-8004 Agents": verified-wallet (the payTo is the agent wallet registered in the ERC-8004 Identity Registry), verified-delegation (the agent wallet signed an EIP-712 payee delegation for it), mismatch, invalid-delegation, endpoint-unlisted, owner-only (payTo is the identity's owner: never counted as verified), no-agent-wallet or not-read. The identity comes from the 402's extra.erc8004 or the seller's /.well-known/agent-registration.json. When the seller's /.well-known/agent-card.json carries a Concordium badge, the result also has concordium: the agent in Concordium's Agent Registry (CIS-8004; its owner is an identity-verified account) and per payTo verified-wallet, verified-external-key (a CIS-8 bound key), owner-only, mismatch, not-bound, revoked, card-mismatch, endpoint-unlisted or not-read. Never pays. Shares the free limit of 10 calls per hour.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Example JSON request body, for a POST route that checks its input before the 402 (implies POST). Without it, {} is sent and the requestBody example in the endpoint's /openapi.json is tried. |
| method | string | – | HTTP method of the paid route (default: GET, then POST) |
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| Name | Type | Req | Description |
|---|---|---|---|
| agent | – | – | The identity checked: registry, agentId, block read, agent wallet |
| concordium | – | – | Verified by Concordium, when the seller's Agent Card carries a Concordium badge: status, summary, agent (badge, network, owner, agent wallet) and payees (outcome per payment option: verified-wallet,… |
| fix | string|null | – | – |
| payees | array | yes | Per payment option: network, payTo, asset, outcome (verified-wallet, verified-delegation, mismatch, invalid-delegation, endpoint-unlisted, owner-only, no-agent-wallet, not-read) and reason |
| status | string | yes | pass: every payTo is bound to the seller's agent; warn: some are not; info: could not confirm; none: no ERC-8004 identity found |
| summary | string | yes | – |
| url | string | – | – |
No examples provided.
x402_preflight Check an x402 endpoint before paying it ($0.001 via x402) ~483
Paid ($0.001 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand, Stellar or NEAR, or in RLUSD on the XRP Ledger): call this before your agent pays an x402 endpoint. Returns go, caution or no_go, the recommended payment option, and why: payment would fail, the seller's payout address is on the OFAC SDN sanctions list, over your budget (max_usd), price above what is advertised, not HTTPS, unknown token, its 30-day track record. Never pays the endpoint. The buyer's check for one call; for several endpoints at once use x402_preflight_batch, before a payment above about $1 x402_preflight_deep, and to debug your own endpoint x402_diagnose. Same as GET /api/v1/preflight. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves later which verdict you got.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Example JSON request body, for a POST route that checks its input before the 402 (implies POST). Without it, {} is sent and the requestBody example in the endpoint's /openapi.json is tried. |
| client | string | – | Set to gateway when your agent pays with Circle's Gateway client (@circle-fin/x402-batching) from a Gateway balance: Gateway-only endpoints are then not a caution, and Gateway options are recommended… |
| max_usd | number | – | Your budget per call in USD, e.g. 0.05 |
| method | string | – | HTTP method of the paid route (default: GET, then POST) |
| network | string | – | CAIP-2 network you want to pay on, e.g. eip155:8453 |
| pay_to | string | – | The payout address (payTo) your agent was asked to pay, from the 402 it got. x402 Doctor screens that address too (OFAC SDN) and says caution (payto_not_shown) when the seller showed x402 Doctor anot… |
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | Only on an unpaid call: the x402 payment options |
| next_step | – | – | – |
| options | – | – | Each payment option with its network, price and problems |
| reasons | – | – | – |
| receipt | – | – | Signed receipt (EIP-191) binding the answer to your arguments |
| safe_to_pay | boolean|null | – | – |
| summary | string|null | – | One line, e.g. OK to pay: $0.02 on Base. |
| url | string|null | – | – |
| verdict | – | – | – |
No examples provided.
x402_preflight_batch Check up to 10 x402 endpoints before paying ($0.005 via x402) ~282
Paid ($0.005 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand, Stellar or NEAR, or in RLUSD on the XRP Ledger): the pre-payment check for up to 10 x402 endpoints at once. Per endpoint go, caution or no_go, the recommended payment option and why, plus totals. For marketplaces and agents that weigh several services. Never pays the endpoints. Same as GET /api/v1/preflight/batch. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves later which verdict you got.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Set to gateway when your agent pays with Circle's Gateway client (@circle-fin/x402-batching) from a Gateway balance: Gateway-only endpoints are then not a caution, and Gateway options are recommended… |
| max_usd | number | – | Your budget per call in USD, e.g. 0.05 |
| method | string | – | HTTP method of the paid route (default: GET, then POST) |
| network | string | – | CAIP-2 network you want to pay on, e.g. eip155:8453 |
| urls | array | yes | The x402 endpoints to check (public http(s) URLs), at most 10 |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | Only on an unpaid call: the x402 payment options |
| count | number|null | – | – |
| counts | – | – | How many go, caution, no_go and unknown |
| receipt | – | – | Signed receipt (EIP-191) binding the answer to your arguments |
| results | – | – | One preflight per endpoint |
No examples provided.
x402_preflight_deep Deep check of an x402 endpoint before an expensive payment ($0.01 via x402) ~359
Paid ($0.01 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand, Stellar or NEAR, or in RLUSD on the XRP Ledger): for expensive calls. The pre-payment verdict (go, caution or no_go) plus the full diagnosis, the 30-day history per day, how reliable the seller's other endpoints are and whether the endpoint moved domains. Never pays the endpoint. Worth it before a payment above about $1; for an ordinary call x402_preflight is enough. Same as GET /api/v1/preflight/deep. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves later which verdict you got.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Example JSON request body, for a POST route that checks its input before the 402 (implies POST). Without it, {} is sent and the requestBody example in the endpoint's /openapi.json is tried. |
| client | string | – | Set to gateway when your agent pays with Circle's Gateway client (@circle-fin/x402-batching) from a Gateway balance: Gateway-only endpoints are then not a caution, and Gateway options are recommended… |
| max_usd | number | – | Your budget per call in USD, e.g. 0.5 |
| method | string | – | HTTP method of the paid route (default: GET, then POST) |
| network | string | – | CAIP-2 network you want to pay on, e.g. eip155:8453 |
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| Name | Type | Req | Description |
|---|---|---|---|
| accepts | – | – | Only on an unpaid call: the x402 payment options |
| next_step | – | – | – |
| options | – | – | – |
| reasons | – | – | – |
| receipt | – | – | Signed receipt (EIP-191) binding the answer to your arguments |
| safe_to_pay | boolean|null | – | – |
| summary | string|null | – | – |
| url | string|null | – | – |
| verdict | – | – | – |
No examples provided.
x402_quick_check Quick x402 endpoint check (free) ~185
Free: does this x402 endpoint work for a paying agent? Returns pass, warn or fail with the number of problems and the top three. Limited to 10 calls per hour. For every check use x402_diagnose ($0.01); for code changes x402_fix ($0.05); before paying someone else's endpoint x402_preflight ($0.001).
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Example JSON request body, for a POST route that checks its input before the 402 (implies POST). Without it, {} is sent and the requestBody example in the endpoint's /openapi.json is tried. |
| method | string | – | HTTP method of the paid route (default: GET, then POST) |
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| Name | Type | Req | Description |
|---|---|---|---|
| failures | number | yes | – |
| next | string | – | – |
| overall | string | yes | pass, warn or fail |
| top_problems | array | yes | Up to three problems, failures first |
| url | string | – | – |
| warnings | number | yes | – |
No examples provided.
x402_trust_add Add your endpoint to the x402 Trust Index (free) ~152
Free: add your own paid endpoint to the x402 Trust Index when no registry lists it yet (CDP Bazaar, Circle's Agent Marketplace, GoPlausible, XRPL AI Hub, nohumans.directory, PayAPI Market, HIVE402, MPP directory). x402 Doctor first checks that it answers 402 with a payment challenge (x402, MPP or L402); the next daily scan starts its record, which buyers' agents see before they pay. At most 25 endpoints per host. Limited to 10 calls per hour.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| Name | Type | Req | Description |
|---|---|---|---|
| check | string|null | – | The free web check for this URL |
| error | string|null | – | Why it was not added |
| message | string|null | – | – |
| ok | boolean | yes | true: added, already added, or already listed |
| status | string|null | – | added, submitted (already added) or listed (a registry lists it) |
| url | string|null | – | – |
| verdict | string|null | – | The pre-payment verdict when it was added |
No examples provided.
x402_trust_record x402 Trust Index record (free) ~139
Free: the daily track record of a paid x402 or MPP endpoint from the x402 Trust Index: on how many of the last 30 scanned days an agent could pay it, the latest verdict and reasons, price and networks. found: false when it is not in the index; add your own endpoint with x402_trust_add. Limited to 10 calls per hour. Before paying, x402_preflight ($0.001) checks the live 402 and includes this record.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| Name | Type | Req | Description |
|---|---|---|---|
| days_checked | number|null | – | – |
| days_payable | number|null | – | Days the daily scan found it payable (go or caution) |
| found | boolean | yes | false: not in the Trust Index (see how_to_list) |
| how_to_list | string|null | – | – |
| last | string|null | – | Latest day: g go, c caution, n no_go, x unreachable |
| last_scan | – | – | The latest verdict, reasons, price and networks |
| payable_ratio | number|null | – | – |
| submitted | boolean|null | – | Added by its seller, not listed in a registry |
| url | string | yes | – |
No examples provided.
How do I install the x402 Doctor MCP server?
x402 Doctor is a hosted endpoint at https://x402-doctor.fizzl.eu/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · x402-doctor.fizzl.eu
claude mcp add --transport http fizzl13-x402-doctor 'https://x402-doctor.fizzl.eu/mcp'
What is the x402 Doctor MCP server?
x402 Doctor is an MCP server listed in the public MCP registry as io.github.Fizzl13/x402-doctor. Is this x402/MPP API safe to pay? $0.001 preflight, fixes, a $0.25 test purchase. Free quick check. This page covers its hosted endpoint (https://x402-doctor.fizzl.eu/mcp).
Is the x402 Doctor MCP server safe to use?
x402 Doctor scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the x402 Doctor MCP server expose?
x402 Doctor exposes 16 tools: x402_quick_check, x402_payee_check, check_payment_proof, concordium_badge_check, x402_facilitator_status, and 11 more. Their descriptions and schemas cost roughly 3,728 tokens of context every time the server is loaded.
Does the x402 Doctor MCP server require authentication?
No. We connected to x402 Doctor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the x402 Doctor MCP server still maintained?
x402 Doctor is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the x402 Doctor MCP server?
VerifyMCP ran 13 checks on x402 Doctor, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.