Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

x402 Doctor

by Fizzl13version 1.0.3i★ 1 (Stars for the whole repo)iRuns in the cloudOfficial site ↗
Registry nameio.github.Fizzl13/x402-doctor

How to install

What it does

Is this x402/MPP API safe to pay? $0.001 preflight, fixes, a $0.25 test purchase. Free quick check.

  • Connects Runs in the cloud
  • Account or key No key needed
  • Category Clinics & health

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity0/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering8/8The cloud endpoint answered at the last check
Usage score20/100

Quality: Passed 5/5 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install x402 Doctor. Follow https://mcp.popnx.com/i/fizzl13-x402-doctor.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 5/5 checks · What you ask goes through the maker’s server (x402-doctor.fizzl.eu) · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude · about 2 min

No key, nothing to install · Set it up once on claude.ai or the desktop app, then use it in chat · free accounts can add 1 · on Team/Enterprise an Owner adds it

  1. Open Claude’s Connectors page

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. Click “Add” → “Custom” → “Web” and fill in these 2 fields

    Copy each value into the field with the same name in Claude, then click Continue

    Name · Namex402 Doctor
    Remote MCP server URL · Addresshttps://x402-doctor.fizzl.eu/mcp

    Click Continue past the sign-in settings Claude detected · under Authentication choose what the maker says (Sign in now, Sign in when needed or No sign in), then click Add

  3. Turn it on in a chat

    +Connectorsx402 Doctor

  4. Try it

    Use x402 Doctor and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using x402 Doctor or shows a x402 Doctor tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with ChatGPT, depending on your plan

Full MCP: ChatGPT Business, Enterprise or Edu on the web · Pro: connects with read/fetch permissions, so tools that change data may not work · Plus: not confirmed in OpenAI’s docs; if you see an add-custom-MCP option on the Plugins page you can try these steps · web only

  1. Open ChatGPT’s add-MCP page on the web

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. Fill in the name and address

    Enter a name, paste the address under Connection, tick the risk warning and click Create as a plugin

    Name · Namex402 Doctor
    Connection · Addresshttps://x402-doctor.fizzl.eu/mcp
  3. Pick x402 Doctor in a chat

    Start a new chat and pick x402 Doctor from your plugins before typing

  4. Try it

    Use x402 Doctor and tell me what you can do for me, then show me one thing

    ✓ If ChatGPT says it is using x402 Doctor or shows a x402 Doctor tool in the answer, you are connected

Menu names checked against OpenAI’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Claude Code · about 2 min

No key, nothing to install

  1. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  2. Paste this command and press Enter

    claude mcp add --transport http --scope user x402-doctor https://x402-doctor.fizzl.eu/mcp
  3. Type /mcp in Claude Code

    You should see x402 Doctor listed as connected

  4. Try it

    Use x402 Doctor and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using x402 Doctor or shows a x402 Doctor tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor · about 2 min

No key, nothing to install

  1. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  2. Open the AI chat in Cursor in Agent mode

  3. Try it

    Use x402 Doctor and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using x402 Doctor or shows a x402 Doctor tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code · about 2 min

No key, nothing to install

  1. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  2. Open the AI chat in VS Code in Agent mode

  3. Try it

    Use x402 Doctor and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using x402 Doctor or shows a x402 Doctor tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

Address for apps that connect over the web

Addresshttps://x402-doctor.fizzl.eu/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use x402 Doctor💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

Claude Code

claude mcp add --transport http --scope user x402-doctor https://x402-doctor.fizzl.eu/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "x402-doctor": {
      "url": "https://x402-doctor.fizzl.eu/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "x402-doctor": {
      "type": "http",
      "url": "https://x402-doctor.fizzl.eu/mcp"
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

GitHub starsi
1 (Stars for the whole repo)
This repo holds several MCP listings; its stars count once in rankings
Downloads per weeki
Not on npm/PyPI
Licencei
AGPL-3.0
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
1.0.3
Published to registryi
Oct 13, 2026
Code last changedi
Nov 18, 2026
Last checked
Nov 18, 2026
Maker
Fizzl13
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Connect over the internet in

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

All apps, with pros and cons →

Related guides

What it can do

Tool names and descriptions exactly as the server reported them on Nov 18, 2026. The maker wrote them, not us; we show them as plain text.

  • x402_quick_check

    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_

  • x402_payee_check

    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 a

  • check_payment_proof

    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

  • concordium_badge_check

    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_h

  • x402_facilitator_status

    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

  • x402_trust_record

    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_trus

  • x402_trust_add

    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 challe

  • verify_receipt

    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

  • x402_diagnose

    Paid ($0.01 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, 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, S

  • x402_preflight

    Paid ($0.001 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, 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, t

  • x402_fix

    Paid ($0.05 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, 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),

  • x402_preflight_batch

    Paid ($0.005 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, 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 tota

  • x402_preflight_deep

    Paid ($0.01 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, 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

  • x402_delivery_check

    Paid ($0.25 via x402 in USDC on Base, Solana, Monad, Polygon, Arbitrum, Avalanche, Algorand or Stellar, 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 li

  • x402_delivery_status

    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.

  • feedback

    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.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account Fizzl13, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed yesterday

  • ✓ Pass

    Has a licence

    Uses AGPL-3.0

  • ✓ Pass

    Endpoint responds

    Responded in 150 ms (HTTP 200)

  • – Not applicable

    Sign-in with OAuth

    No sign-in needed

  • ✓ Pass

    No hidden instructions in tool descriptions

    Read 16 tool descriptions and found no hidden instructions to the AI

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/fizzl13-x402-doctor.svg)](https://mcp.popnx.com/en/servers/fizzl13-x402-doctor)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Clinics & healthi

  • More stars than 0% of the other 1182 servers in this category
  • Published to the registry more recently than 43% of the other 1182 servers in this category
  • Basic checks equal to or better than 99% of the other 1182 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is x402 Doctor safe?

It passed 5 of 5 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed yesterday, and the latest version (1.0.3) reached the registry 37 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT on the web (full MCP on Business and above; Pro read-only).

What can I use instead?

In the same category: Medplum MCP, Mirobody, Codescene MCP Server, WHOOP — MissingMCP, Marrow

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Medplum MCP

Securely access and manage FHIR healthcare data stored in Medplum.

by medplumWidely used★ 2.8KUpdated 4 months ago

Runs in the cloud✓ service owner · medplum.com

Mirobody

Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.

by thetahealthGrowing↓ 725/wk★ 1.6KUpdated 9 days ago

Runs on your computer✓ thetahealth.ai

Codescene MCP Server

An MCP server that provides CodeScene Code Health analysis tools.

by codescene-ossGrowing↓ 3.8K/wk★ 85Updated 8 months ago

Runs on your computer✓ service owner · codescene.com

Marrow

Marrow Health: your Apple Health data over MCP, from the free iOS app. Reads, and writes on demand.

by skeletonarmytechEarly↓ 62/wk★ 4Updated 28 days ago

Runs on your computer✓ skeletonarmy.tech
Compared with similar ones
This one
x402 Doctor
Medplum MCPMirobodyCodescene MCP ServerWHOOP — MissingMCPMarrow
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installInstalls on your computerInstalls on your computerRuns in the cloud, nothing to installInstalls on your computer
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks5/54/43/32/32/43/3
LicenseAGPL-3.0Apache-2.0Apache-2.0NOASSERTIONMITMIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

x402 Doctor

· Live status ·

Diagnoses why an x402-payable endpoint's payment flow is broken, without needing a funded wallet.

Paste a URL (web app) or run x402-doctor (CLI, CI) and get back exactly which check failed, why, and how to fix it. Every check traces back to a real bug hit while shipping Ichimoku Signal and presign-guard.

▶ [Watch the 70-second explainer](https://x402-doctor.fizzl.eu/media/explainer.mp4) (with voice and captions): diagnosing a broken endpoint, the pre-payment check for agents, and the daily Trust Index.

▶ New: [the paid fix in 70 seconds](https://x402-doctor.fizzl.eu/media/fix.mp4): for $0.05 the Doctor hands you the medicine, the exact code that fixes each problem for your stack, in the browser or as JSON for agents.

What it checks

GroupCheckCatches
402 challengereturns-402No 402 for GET or POST (tries both, or --method). Behind Cloudflare or Amazon CloudFront the hint names the usual Monetization Gateway or AWS WAF Monetize rule misses. An endpoint that asks for x401 proof first is info, not a failure. A POST that answers 400 or 422 to an empty body checks its input before payment: Doctor sends the requestBody example from the seller's /openapi.json (or one built from its schema), or your own example body, and without one the check is a warning (needs input), not a failure
x401An x401 proof request (PROOF-REQUEST, x401.id) instead of a 402: the endpoint asks who is behind the agent before it asks for payment. Pass when the base64url payload names scheme x401, a version and credential requests (with their protocols, the token endpoint and the payment hint); a warning when agents can't read it; info for the older header name PROOF-REQUIRED
protocol-version, challenge-headerv1 vs v2, missing x402Version, challenge in the wrong header, undecodable header
envelope-body-mirrorHeader-only challenge (@x402/express sends {}), header and body disagreeing
MCP (payment per tool call)mcp-serverWhen the URL answers no 402 but speaks MCP (Streamable HTTP, JSON or SSE, with or without a session): initialize and tools/list without payment
mcp-paid-toolsNo tool description says it is paid (x402, USDC, a price), so agents can't tell
mcp-payment-requiredOne unpaid tools/call per paid-looking tool (at most 2; explicitly paid tools first — "Paid …" or a price / "via x402" in the title; never tools that call themselves free, destructive tools, or write tools unless explicitly paid). A free answer warns only for an explicitly paid tool, otherwise it is info: the x402 payment requirement in the tool result with isError: true (as @x402/mcp), or an HTTP 402 with PAYMENT-REQUIRED instead (payable over HTTP, not by @x402/mcp clients), a JSON-RPC error, a tool that answers for free, or example arguments refused before the payment step (publish one valid call as _meta.examples to avoid that). The requirement then gets the payment-option, settlement and wallet checks below
mcp-tool-poisoningHidden orders for the agent in tool descriptions (tool poisoning): hidden Unicode characters, blocks, reading ~/.ssh or .env, "do not tell the user", sending the maximum USDC (code rules), then TypeSafe Jev per tool (with TYPESAFE_API_KEY). A sure finding is warn, an unsure one info. Calibrated on 755 tools of 96 servers from the official MCP registry: no false alarm, and five made-up poisoned tools all caught
mcp-payment-text, mcp-payment-structuredThe requirement only in structuredContent (the x402 MCP transport requires JSON text in content[0]), or only as text (structuredContent preferred)
Payment optionsaccepts[i]-scheme, -networkMissing scheme; legacy names like base / solana:mainnet instead of CAIP-2
accepts[i]-payto, -assetInvalid EVM, Solana, XRPL or Algorand addresses (XRPL and Algorand with their checksums); a payTo that is a placeholder nobody holds a key for (the zero address, which USDC refuses, 0x…dEaD, or Solana's System Program or incinerator), also as an MPP recipient; asset that is not USDC, or USDC of another network (e.g. Base Sepolia USDC on Base); on Algorand an asset that is not an ASA id (USDC is ASA 31566704); on XRPL an XRP amount that isn't in drops, or "RLUSD" from another issuer than Ripple's
accepts[i]-amountDecimal dollar amounts ("0.02") instead of atomic units, zero or non-integer amounts
Stellar optionsx402 exact on Stellar (stellar:pubnet, @x402/stellar): payTo a G…, C… or M… address with a valid StrKey checksum, asset a Soroban token contract (USDC is CCW67TSZV3SSS2HXMBQ5JFGCKJNXKZM7UQUWUZPUTHXSTZLEO7SJMI75; "USDC" or a testnet contract fails), a positive integer amount (USDC has 7 decimals: 100000 is $0.01) and extra.areFeesSponsored: true, without which the client refuses
testnet-onlyEvery option is on a test network (Base Sepolia, Solana Devnet, …): the challenge can be valid, but agents paying with real USDC have no option
aws-test-modeA 402 served through Amazon CloudFront that offers only testnets (info): AWS WAF Monetize left in Test currency mode
accepts[i]-extraSolana without extra.feePayer (clients throw "feePayer is required"), EVM without the EIP-712 name/version
accepts[i]-batch, -batch-delay, -batch-deposit, batch-escrowThe batch-settlement scheme (one deposit into the x402 escrow, then a signed voucher per call, claimed in batches): extra.receiverAuthorizer missing (clients refuse), withdrawDelay missing or outside 900 s to 30 days, no EIP-712 domain for the EIP-3009 deposit, minDeposit not in atomic units, the escrow not deployed on the network; the deposit and withdraw delay buyers commit to
accepts[i]-auth-capture, -auth-escrow, -auth-deadlines, -auth-fees, -auth-domain, -auth-flow, auth-capture-escrowThe auth-capture scheme on EVM (the buyer signs once; the amount is held in the commerce-payments escrow until the seller captures it, with refunds until a deadline): no operator (extra.captureAuthorizer), an escrow that is neither commerce-payments v1.1 nor v1.0, a capture deadline that has passed or a refund deadline before it, fee bounds outside 0 <= min <= max <= 10000 bps or no fee recipient, no EIP-712 domain for the EIP-3009 authorization, a charge (paymentFlow authorization) without receiverAuthorizer, the escrow not deployed on the network; when the money is captured and until when it can be refunded
accepts[i]-cloudflare, -payto, -amount, cloudflare-registrationCloudflare pay per crawl (batch-settlement on network cloudflare:402): payTo must be merchant (Cloudflare settles, as merchant of record), the price is a currency code (USD) and an amount in cents, and the 402 carries the http-message-signatures extension with the URL where agents register their signing key. Paid by crawlers and agents registered with Cloudflare (Web Bot Auth), not by wallets: the preflight says caution (cloudflare_crawler_only), not no-go
accepts[i]-extra, circle-gateway, accepts-orderCircle Gateway options ("exact" signed for the Gateway Wallet, domain GatewayWalletBatched): extra.version other than "1" or no verifyingContract (Circle's client skips or can't sign it), a contract that isn't Circle's Gateway Wallet; who can pay them (a Gateway balance and Circle's client, not standard x402 clients or browser wallets; their 7-day timeout is right); a Gateway option listed before the standard one on the same network, which x402 clients would pick and fail
accepts[i]-schemeA scheme standard x402 clients don't pay (anything but exact, upto, batch-settlement and auth-capture; eip3009 gets the hint to use exact): what it requires is unknown, so a missing or unusual payTo, asset or amount is a warning, not a fail (a burn address stays a fail). The preflight never recommends such an option over a standard one; with only such options it says caution (custom_scheme_only)
accepts[i]-scheme, -network, -planNevermined plans (nvm:erc4337 on eip155: , nvm:card-delegation on stripe, braintree or visa): no payTo or amount is asked, since the price is in the plan; the network must be the settlement rail (not sandbox or live), planId a plan id and extra.agentId set. The preflight says caution (nevermined_plan): payable only with a Nevermined account and its SDK, not by standard x402 clients
Resourceresource-urlhttp:// resource URL on an https:// endpoint (Express behind a TLS proxy without trust proxy); a path instead of a full URL (judged against the endpoint, a warning)
resource-metadataMissing description / mimeType
Settlementsolana-payout-accountSolana payout wallet without a token account for the asset: every settlement fails on-chain
xrpl-payout-account, xrpl-payout-trustlineXRPL payout account that was never activated, has Deposit Authorization on, or requires a destination tag the option doesn't give; for a token like RLUSD, no (or a frozen) trust line to its issuer: every payment fails
accepts[i]-lightning, lightning-invoice, lightning-request-hashBitcoin Lightning (x402 exact on lnbtc, Sept 2026): payTo must be the node key, amount in millisatoshis, paymentFlow: "upfront" and a request binding (http:1/mcp:1); the BOLT11 invoice in extra.invoice is decoded and must match the option exactly (amount, bc/tb, expiry = maxTimeoutSeconds, signed by payTo, not expired) and commit to extra.requestHash, which for http:1 is recomputed for the doctor's own request
algorand-payout-optinAlgorand payout address that has not opted in to the asset (an account can only receive an ASA after opting in): every payment fails
stellar-payout-trustlineStellar payout account (G…) that was never funded, or has no (or an unauthorised) trustline to Circle's USDC: every payment fails. Read from Horizon; a contract (C…) needs none
solana-walletsSolana settled by PayAI, which rejects Phantom (Lighthouse instructions before the transfer)
Who can paywalletsPer wallet (MetaMask, Coinbase Wallet, Rabby, Phantom, Solflare, Backpack, Pera, Defly, Xaman, Crossmark, GemWallet, x402 agents, which also pay Stellar): the networks where payment works and where it fails, and why. Also in the JSON report as wallets
metamask-site-scanOnly with METAMASK_SCAN=on (off by default: the endpoint has no published API or licence). MetaMask's site scanner (Blockaid) blocks the domain (e.g. "wallet drainer"): MetaMask users can't open the site or pay in the browser. With how to report a false positive. Agents are not affected

| | evm-payto-eoa | EVM payout wallet is

Only the beginning is shown; read the rest in the repo