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 Receipt Verifier

by nexus-mcp-infraversion 1.0.0i★ 0iRuns in the cloudRepository ↗
Registry nameio.github.nexus-mcp-infra/x402-receipt-verifier

How to install

What it does

Audits NEXUS's own x402 payment logs against its own delivery logs and issues a signed proof-of-deli

  • Connects Runs in the cloud
  • Account or key May need a key; not confirmed (our check was refused)
  • Category Online shops & payments

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
Freshness7/12Full marks for a release or code change within 30 days
Still answering8/8The cloud endpoint answered at the last check
Usage score15/100

Quality: Passed 2/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 Receipt Verifier. Follow https://mcp.popnx.com/i/nexus-mcp-infra-x402-receipt-verifier.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 2/5 checks · What you ask goes through the maker’s server (x402-receipt-verifier-325572559480.us-central1.run.app) · ✓ 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 Receipt Verifier
    Remote MCP server URL · Addresshttps://x402-receipt-verifier-325572559480.us-central1.run.app/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 Receipt Verifier

  4. Try it

    Use X402 Receipt Verifier and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using X402 Receipt Verifier or shows a X402 Receipt Verifier 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 Receipt Verifier
    Connection · Addresshttps://x402-receipt-verifier-325572559480.us-central1.run.app/mcp
  3. Pick X402 Receipt Verifier in a chat

    Start a new chat and pick X402 Receipt Verifier from your plugins before typing

  4. Try it

    Use X402 Receipt Verifier and tell me what you can do for me, then show me one thing

    ✓ If ChatGPT says it is using X402 Receipt Verifier or shows a X402 Receipt Verifier 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-receipt-verifier https://x402-receipt-verifier-325572559480.us-central1.run.app/mcp
  3. Type /mcp in Claude Code

    You should see X402 Receipt Verifier listed as connected

  4. Try it

    Use X402 Receipt Verifier and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using X402 Receipt Verifier or shows a X402 Receipt Verifier 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 Receipt Verifier and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using X402 Receipt Verifier or shows a X402 Receipt Verifier 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 Receipt Verifier and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using X402 Receipt Verifier or shows a X402 Receipt Verifier 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-receipt-verifier-325572559480.us-central1.run.app/mcp

JSON settings are under “For developers” below

Stuck? Ask people who use X402 Receipt Verifier💬 Discussion →
For developers: Terminal commands and JSON settings

Over the web

Claude Code

claude mcp add --transport http --scope user x402-receipt-verifier https://x402-receipt-verifier-325572559480.us-central1.run.app/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "x402-receipt-verifier": {
      "url": "https://x402-receipt-verifier-325572559480.us-central1.run.app/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "x402-receipt-verifier": {
      "type": "http",
      "url": "https://x402-receipt-verifier-325572559480.us-central1.run.app/mcp"
    }
  }
}

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

At a glance

Downloads per weeki
Not on npm/PyPI
Licencei
No licence stated
Connection
Runs in the cloud
Transport
streamable-http
Latest versioni
1.0.0
Published to registryi
Aug 23, 2026
Code last changedi
Sep 4, 2026
Last checked
Nov 15, 2026
Maker
nexus-mcp-infra
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

The server asks you to sign in before it lists its tools.

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 nexus-mcp-infra, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 3 months ago

  • ✕ Fail

    Has a licence

    No licence file found in the repo

  • ! Caution

    Endpoint responds

    Refused access (HTTP 403) without offering OAuth sign-in. It may need a key, or it may be blocking bots; not confirmed.

  • ! Caution

    Sign-in with OAuth

    Needs a key or token that you copy and paste yourself

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

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/nexus-mcp-infra-x402-receipt-verifier.svg)](https://mcp.popnx.com/en/servers/nexus-mcp-infra-x402-receipt-verifier)

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 Online shops & paymentsi

  • More stars than 0% of the other 2960 servers in this category
  • Published to the registry more recently than 23% of the other 2960 servers in this category
  • Basic checks equal to or better than 11% of the other 2960 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 Receipt Verifier safe?

It passed 2 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 3 months ago, and the latest version (1.0.0) reached the registry 3 months 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: Stripe MCP, flightclaw, Trade It, Marketplace Ad Pros: Amazon Ads & Seller Central, idealo MCP Server

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

Stripe MCP

Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.

by stripeWidely used★ 2.1KUpdated 13 months ago

Runs in the cloud✓ service owner · stripe.com

flightclaw

Search ~300 airlines and book flights with a checkout link. OAuth sign-in by email code.

by flightclawGrowing★ 87Updated 2 months ago

Runs in the cloud✓ service owner · flightclaw.com

Trade It

Connect brokerage accounts to AI assistants: holdings, orders, asset lookup, and approved trading.

by trade-it-incEarly★ 62Updated 34 days ago

Runs in the cloud✓ service owner · tradeit.app

idealo MCP Server

Search products, compare prices and discover deals across 6 European markets with your AI assistant.

by idealoEarly★ 28Updated 6 months ago

Runs in the cloud✓ service owner · mcp.idealo.com
Compared with similar ones
This one
X402 Receipt Verifier
Stripe MCPflightclawTrade ItMarketplace Ad Pros: Amazon Ads & Seller Centralidealo MCP Server
Runs whereRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoYesNoNoNoNo
Basic checks2/54/44/45/54/44/4
License–MITMITCC0-1.0MITMIT
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 Receipt Verifier

Audits NEXUS's own x402 payment logs against its own delivery logs and issues a signed receipt proving a specific payment correlates with a real, successful service call. NEXUS candidate #13 -- manual build, not FORGE-generated.

  • POST /verify-payment-receipt {"asset_name": "...", "payer_address": "0x...", "claimed_amount_usd": 0.01, "claimed_at": "2026-08-22T21:31:34Z"} -- charged $0.02 via x402 (Base mainnet, real USDC).
  • POST /payer-spend-health {"asset_name": "...", "payer_address": "0x..."} -- charged $0.02 via x402.
  • POST /verify-receipt-signature {"receipt": {...}, "signature": "..."} -- free, confirms a previously-issued receipt is authentic and unmodified.
  • MCP tools verify_payment_receipt / payer_spend_health at /mcp -- currently free, see "Known limitations".
  • GET /health, GET /.well-known/agent-card.json, GET /openapi.json (has x-payment-info).

Mainnet cutover (2026-09-03)

Originally built and measured on Base Sepolia testnet. Cut over to Base mainnet: x402 settlement moved to the CDP facilitator (create_facilitator_config(), same swap already applied to ws/live-entity-verification/erc8004-agent-liveness/onchain-activity-index), and the payto wallet moved to NEXUS_X402_PAYTO_ADDRESS (fail-fast env var, no placeholder default, renamed from X402_WALLET_ADDRESS). CDP_API_KEY_ID/CDP_API_KEY_SECRET and NEXUS_X402_PAYTO_ADDRESS must be set in Cloud Run before this deploys.

What it actually does (and why it's not just a log dump)

revenue_events (x402 payments settled) and traffic_events (HTTP requests served) are two separate, uncorrelated tables -- neither insert stores a shared ID linking a specific payment to the specific request it paid for. This asset does the correlation NEXUS itself doesn't otherwise do anywhere: given a claimed (asset_name, payer_address, claimed_amount_usd, claimed_at), it finds the real matching revenue_events row (if any) within window_seconds, then checks whether a successful (2xx) traffic_events row for that same asset landed shortly after that real payment timestamp. The verdict (VERIFIED_DELIVERY / PAYMENT_NO_DELIVERY / PAYMENT_NOT_FOUND) plus a signed receipt is the product -- not raw access to either table. Both tables are read through two Postgres SECURITY DEFINER RPC functions (nexus_verify_payment_receipt, nexus_payer_spend_health) that return only the computed verdict object, never a row dump -- consistent with this codebase's existing INSERT-only RLS policy on both tables (see CLAUDE.md SS5). Migration: add_x402_payment_receipt_verification_rpcs (Supabase project ieduhdgfjdeffvzxvihf).

Scope, on purpose: only covers NEXUS's own already-deployed x402 assets (whatever is actually in our own revenue_events/traffic_events). Auditing a third party's payment claims against a third party's logs was the original, broader idea (opportunity list item #3, "recibo/prueba de ejecucion verificable para pagos entre agentes") and was explicitly flagged there as carrying legal/dispute-liability risk from acting as an arbiter between two other parties. Narrowing scope to our own already-public asset catalog sidesteps that entirely -- there is no third party whose claim we're adjudicating, only our own already-settled data.

Known asset_name spellings (found while building this, real data)

revenue_events.asset_name is not consistently kebab-case across the existing catalog -- e.g. the similarity-search asset's real stored value is "Similarity Search API" (display-cased), not similarity-search-api. Callers must pass the exact string as stored, or the RPC correctly (not a bug) returns PAYMENT_NOT_FOUND. As of this writing, real values seen in revenue_events: document-conversion-api, live-entity-verification, agent-verification-api, url-metadata-api, Similarity Search API, ws.

The signed receipt

signature is an HMAC-SHA256 (hex) over the canonical JSON encoding of receipt, keyed by NEXUS_RECEIPT_SIGNING_KEY. This is not an offline-verifiable signature (that would need asymmetric crypto + a published public key -- deliberately left out, see "Known limitations"): a holder proves a receipt is authentic by calling this asset's own free POST /verify-receipt-signature, which re-checks the HMAC server-side. Rotating NEXUS_RECEIPT_SIGNING_KEY invalidates every receipt issued under the old key.

Deploy target: Cloud Run

Same pipeline as candidates #4/#3/#6 -- see skills/infra-deploy-ops.

# 1. First deploy -- PUBLIC_DOMAIN not known yet, every real request 421s until step 2.

./scripts/deploy_cloud_run.sh x402-receipt-verifier manual_assets/x402-receipt-verifier

2. Grab the printed *.run.app URL, then (only if it differs from env-vars.deploy.yaml's guess):

gcloud run services update x402-receipt-verifier --region us-central1 --project nexus-505016 \ --update-env-vars PUBLIC_DOMAIN=

Known limitations (left unfixed on purpose -- CLAUDE.md SS3, no gate without evidence it's needed)

  • MCP tool calls are not charged. Same in-process-call pattern as every other manual asset in this codebase (url-metadata-api, agent-verification-api, document-conversion-api).
  • Receipt signature requires an online check, not offline asymmetric verification -- see above.
  • Correlation is a time-window heuristic, not a hard link. Neither revenue_events nor traffic_events stores a shared correlation ID at insert time, so VERIFIED_DELIVERY means "a successful request to this asset landed within the window after this payment", not "this exact request was paid for by this exact transaction". On a low-traffic asset this is effectively exact; on a hypothetical high-traffic asset with many concurrent callers it would be ambiguous -- candidate_successful_calls (surfaced directly on the receipt, see PaymentReceipt in main.py) would show >1 in that case. None of the 6 assets covered had concurrent traffic dense enough for this to matter as of 2026-08-23.
  • ~~Payment settles before the Supabase RPC runs...~~ Corrected 2026-08-31: false positive, see below. The 2026-08-23 quality gate claimed a Supabase failure would settle payment anyway; nobody had actually read x402's (2.15.0, the pinned version) PaymentMiddlewareASGI source before writing that. It already implements verify→execute→settle-only-on-2xx: verify_payment (no funds move) runs before the handler via call_next(request); when the handler returns ≥400 or raises (exactly what happens here -- _verify_payment_receipt_core re-raises _NexusRpcError as HTTPException(502/503/504) on a Supabase failure), the middleware calls dispatcher.cancel() and never calls `process_settlement()` -- no charge. Confirmed empirically (real app + real PaymentMiddlewareASGI + mocked facilitator, forcing an HTTPException(504)): 0 settle()/on_after_settle calls on failure, 1 on a 200. No code change needed -- the architecture was already correct.
  • Anon-key RPC bypass. The two Postgres RPC functions are granted to anon (required for PostgREST to expose them at all) -- a leaked SUPABASE_ANON_KEY lets someone call them directly at /rest/v1/rpc/nexus_verify_payment_receipt, bypassing this asset's x402 charge. Accepted: the RPCs only return correlation verdicts about NEXUS's own already-public asset catalog, nothing sensitive is exposed by the bypass itself, only the paywall is bypassed. Same risk category as every other Supabase anon-key use in this codebase.
  • No per-caller rate limiting. Fine for a 7-day disposable measurement window.

Quality gate (2026-08-22 deploy, gate completed 2026-08-23 after a spend-limit interruption)

Same 2-agent process as candidates #3/#4/#6 (security lens; functional+quality+buyer-experience lens), run post-deploy this time -- the review was still in progress when the account's monthly spend limit cut the session overnight, resumed and finished the next session. Real findings, applied:

  • Security (1 finding, low): POST /verify-receipt-signature had no x402 gate and no size/depth bound, so it hashed an arbitrary caller-supplied receipt dict for free -- a cheap cost/availability nuisance, not a serious vuln. Fixed: rejects >4096-byte or >10-level-deep bodies with 400/413 before any hashing (_validate_receipt_shape, _MAX_RECEIPT_BYTES/_MAX_RECEIPT_DEPTH in main.py).
  • Functional/buyer-experience (1 finding, medium) -- retracted 2026-08-31: originally reported as "payment settles before the RPC runs, so a Supabase failure leaves the buyer charged with no recourse." This was a misreading of PaymentMiddlewareASGI, not a real bug -- see "Known limitations" above for the empirical proof. No code change was needed.
  • Everything else checked (SSRF class from candidate #3, zip-bomb/thread-leak class from candidate #6, anon-key RPC over-return, HMAC correctness, self-payment payTo class from candidate #4, IP truncation, injection surface) came back clean -- confirmed, not just claimed, by re-reading the relevant code paths.
  • Two very-low cosmetic items were left as-is on purpose: an unused ctx: Context = None MCP-tool param (matches the same unused-param convention already present in agent-verification-api/main.py, not a deviation worth fixing here) and silent clamping of window_seconds/lookback_days on the MCP path only (REST already rejects out-of-range via Pydantic; the MCP path echoes the substituted value back in the receipt, so it's discoverable, just not an explicit error -- no evidence yet that this needs a gate).

Measurement (candidate #13, 7-day window)

7-day window from first real deploy (2026-08-23 -> decision point 2026-08-30). Source of truth: traffic_events/revenue_events/mcp_call_events (asset_name = 'x402-receipt-verifier'), not Cloud Run logs. Day 7: if zero real traffic (filtering crawlers), pause/delete the Cloud Run service (gcloud run services delete x402-receipt-verifier --region us-central1 --project nexus-505016).