X402 Receipt Verifier MCP Server

by nexus-mcp-infra Your server? Claim it

answering

X402 Receipt Verifier is answering right now. Last checked 3 min ago. It exposes 2 tools. Last commit 4 Sep 2026.

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

Uptime history 54 days of history · worst day 97%

54 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

292 ms

Response time

average over 24h

Stars

last commit 4 Sep 2026

Nothing serious here today

Today is the operative word: we check X402 Receipt Verifier every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 3 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

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

~/Library/Application Support/Claude/claude_desktop_config.json

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

~/.codex/config.toml

[mcp_servers.x402-receipt-verifier]
url = "https://x402-receipt-verifier-325572559480.us-central1.run.app/mcp"

.cursor/mcp.json

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

.vscode/mcp.json

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

This endpoint answered with an authorization challenge. The server is running, but it did not say what kind of credentials it expects.

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

payer

payer_spend_health

Aggregate delivery-confirmation rate for one payer address on one NEXUS asset over lookback_days. verdict is SUMMARY (with delivery_rate) or NO_PAYMENTS_FOUND.

verify

verify_payment_receipt

Audits one x402 payment against NEXUS's own delivery logs (its own assets only) and returns a signed receipt. verdict is one of VERIFIED_DELIVERY, PAYMENT_NO_DELIVERY, PAYMENT_NOT_FOUND. claimed_at must be an ISO-8601 timestamp.

Endpoints

URL	Transport	State	Latency	Checked
https://x402-receipt-verifier-325572559480.us-central1.run.app/mcp	streamable-http	needs auth	237 ms	3 min ago

Alternatives to X402 Receipt Verifier

same job, measured the same way

Job Card Template

by theluckystrike

Open a job card, log hours and materials against it, print the card for client sign-off.

local only

NessFlow

by nessflow

Run and read SEO site audits: issues, health score, fixes, rankings and logs.

answering

Shipbook

by shipbook

Debug production issues using Shipbook logs and Loglytics error insights.

answering

Orquesta

by getorquesta

Read a project's prompts, logs and agents, and send new work to the agent on your own machines.

answering

three.ws Provenance

by nirholas

Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

61 installs/wk local only

Evidence Log

by riskrouter

Tamper-evident evidence log: signed heads, proofs, and recording salted digests of your records.

8 tools answering

Agent Health

by autonet

Free owned-agent uptime monitoring, DNS domain proof, signed alerts and opt-in endpoint checks.

46 tools answering

Maileroo

by maileroo

Send email, search delivery logs, and manage domains and your Maileroo account.

answering

X402 Receipt Verifier — questions

Answers built from our own checks of this server.

What can X402 Receipt Verifier do?

It exposes 2 tools, read directly from the server on our last check. Among them: payer_spend_health, verify_payment_receipt. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is X402 Receipt Verifier working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 292 ms. The bar chart above shows every period we have measured.

How do I connect X402 Receipt Verifier?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own credentials: it refuses anonymous clients.

Does X402 Receipt Verifier need an API key?

Yes. Every time we knock, X402 Receipt Verifier answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.

How fast is X402 Receipt Verifier?

It answers our handshake in 292 ms on average, which is faster than 45% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is X402 Receipt Verifier open source?

We cannot say either way: written in Python and 0 stars on GitHub, but we could not determine the licence, and without one the code is not open source by default.