Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Nothing to run from here
x402 Doctor is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
10
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Check x402 endpoints like a paying agent: diagnose, fix plans, pre-payment checks. Free quick check.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http fizzl13-x402-doctor-mcp https://x402-doctor.fizzl.eu/mcp
# 2 — ask your agent for something these tools do
# x402_quick_check, check_payment_proof, x402_diagnose and 7 more
x402 Doctor costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
FIAll 5 servers
Fizzl135 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http fizzl13-x402-doctor-mcp https://x402-doctor.fizzl.eu/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| method | string | no | HTTP method of the paid route (default: GET, then POST) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| header | string | yes | The PAYMENT-RESPONSE header value (base64 JSON) |
Paid ($0.01 USDC via x402 on Base or Solana): 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. Same as GET /api/v1/diagnose. The answer carries a si
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| method | string | no | HTTP method of the paid route (default: GET, then POST) |
Paid ($0.001 USDC via x402 on Base or Solana): 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. Same as GET
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| method | string | no | HTTP method of the paid route (default: GET, then POST) |
| max_usd | number | no | Your budget per call in USD, e.g. 0.05 |
| network | string | no | CAIP-2 network you want to pay on, e.g. eip155:8453 |
Paid ($0.05 USDC via x402 on Base or Solana): 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. 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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| method | string | no | HTTP method of the paid route (default: GET, then POST) |
| stack | string | no | Your server stack (default: detected) |
Paid ($0.005 USDC via x402 on Base or Solana): 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 lat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | yes | The x402 endpoints to check (public http(s) URLs), at most 10 |
| method | string | no | HTTP method of the paid route (default: GET, then POST) |
| max_usd | number | no | Your budget per call in USD, e.g. 0.05 |
| network | string | no | CAIP-2 network you want to pay on, e.g. eip155:8453 |
Paid ($0.01 USDC via x402 on Base or Solana): 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. Same as GET /api/v1/preflight/deep. The answer carries a signed receipt (EIP-191, bound to your arguments) that proves lat
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The x402 endpoint (public http(s) URL), e.g. https://api.example.com/paid |
| method | string | no | HTTP method of the paid route (default: GET, then POST) |
| max_usd | number | no | Your budget per call in USD, e.g. 0.5 |
| network | string | no | CAIP-2 network you want to pay on, e.g. eip155:8453 |
Paid ($0.25 USDC via x402 on Base or Solana): 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 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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | The x402 endpoint to buy once (https, someone else's, payable in USDC on Base) |
| method | string | no | HTTP method of the paid route (default: GET, then POST) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | The job id x402_delivery_check answered with |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| type | string | no | bug, feature (something missing) or other |
| message | string | yes | What happened or what you need |
| endpoint | string | no | Optional: the route or tool it is about, e.g. /v1/token |
| contact | string | no | Optional: how to reach you about it |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install x402 Doctor or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.3.
1.0.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish x402 Doctor can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.