402MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@402MCPdecode this 402 response and tell me exactly how to pay and retry"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
402MCP.org
The MCP server and open registry for HTTP 402 agent payments.
When an AI agent receives 402 Payment Required, 402MCP tells it which scheme
the server speaks (L402, x402 or MPP), what is being asked for, and exactly how
to pay and retry. When a developer is choosing how an agent should pay, or how an
API should charge agents, it recommends a rail from stated requirements. Behind
both sits an open registry of sourced, scored payment solutions.
Site: https://402mcp.org
Remote MCP endpoint:
https://402mcp.org/api/v1/mcp(streamable HTTP)npm:
@402mcp/mcp(stdio)Install guides: https://402mcp.org/docs#install
Install
Claude Code:
claude mcp add --transport http 402mcp https://402mcp.org/api/v1/mcpAny stdio MCP client (Claude Desktop, Cursor, Windsurf and others):
{
"mcpServers": {
"402mcp": { "command": "npx", "args": ["-y", "@402mcp/mcp"] }
}
}Related MCP server: x402 Micropayments MCP
MCP server
One transport-agnostic core (lib/mcp/) serves both the hosted endpoint and the
stdio package, so the two expose the same tools, resources and prompts.
Tool | Purpose |
| Decode a 402 response (L402 macaroon and BOLT 11 invoice, x402 v1/v2, MPP) into exact next steps and the retry header |
| Filter by role, asset, custody, infrastructure, network, scheme, MCP support and maturity; re-weight the criteria; explain every exclusion |
| Search the registry with filters |
| One entry in full, with sources and code samples |
| Wire format of L402, x402 or MPP |
| One GET to a public URL to see whether it speaks 402. Never pays |
| The entry with the highest composite score |
Resources: 402mcp://registry, 402mcp://methodology,
402mcp://solutions/{id}, 402mcp://schemes/{scheme}. Prompts:
choose_payment_rail, handle_402_response. Every tool is annotated
readOnlyHint.
Safety. Everything in a 402 response is server-controlled, so the decoder
lists those fields in untrusted_fields and never repeats their text as
instructions. It flags expired challenges and macaroons that commit to a
different payment hash than their invoice. The probe refuses private, loopback,
link-local and metadata addresses (including hostnames that resolve to them) and
non-web ports, and the hosted endpoint rate-limits it per client. No tool can
spend money.
Machine interfaces
Endpoint | Purpose |
| MCP (JSON-RPC 2.0, streamable HTTP) |
| Decode a 402 response |
| Recommend a rail from requirements |
| Probe a URL for 402 support (rate limited) |
| Versioned list ( |
| Canonical feed with ETag / 304 support |
| Wire format of L402, x402, MPP |
| Daily liveness of every entry's docs and website |
| Changes and corrections |
| JSON Schemas (draft 2020-12) |
| OpenAPI 3.1 |
| Plain-text indexes |
| Discovery |
Any page returns Markdown when requested with Accept: text/markdown.
Methodology
Every entry is scored 1–10 on six equally weighted criteria: custody and sovereignty, operational friction, agent-native support, payment rails and assets, settlement speed and fees, and developer experience. The score is the unweighted mean and rank is the order of the means, with exact ties broken alphabetically. Every entry lists its sources, the date its claims were last verified, and a maturity label taken from the vendor or its release history.
The current ranking is at https://402mcp.org and in /api/v1/registry. The full
methodology is at https://402mcp.org/docs#methodology.
402MCP.org is not affiliated with, sponsored by, or compensated by any vendor it indexes, and listing position cannot be purchased. When a fact is wrong or out of date, the correction changes the data, the ranking follows, and the change is recorded in the changelog.
Development
Requires Node 18.18 or later.
npm install
npm run dev # http://localhost:3000Command | What it does |
| Decoder tests against vectors from the BOLT 11 spec, the MPP draft, reference-minted macaroons and x402 shapes |
| Every machine endpoint: formats, contracts, JSON-RPC behaviour, schema validation, dataset invariants |
| Crawler directives, metadata, structured data, icons, discovery documents, feeds, headers |
| Builds the stdio package and the |
| The built stdio package, end to end |
| ESLint and TypeScript |
The verify suites default to http://localhost:3000; pass a URL to run them
against a deployment.
Deploying to Cloudflare
The site runs as a Cloudflare Worker through the OpenNext adapter. Copy
wrangler.example.jsonc to wrangler.jsonc, create the KV namespace it names,
and fill in your own values. Then:
npm run cf:build
npm run cf:deployProject layout
data/solutions.ts The registry dataset; scores and ranks are computed here
data/changelog.ts Additions and corrections, with reasons
lib/decode/ bech32, BOLT 11, macaroons, RFC 9110 challenges, x402, MPP
lib/mcp/ Transport-agnostic MCP server: tools, resources, prompts
lib/recommend.ts Requirement-driven recommendation
lib/probe.ts URL probe with SSRF guards
lib/schemes.ts Wire-format reference for each scheme
lib/liveness.ts Daily docs and website checks
app/ Next.js App Router pages and route handlers
worker.ts Worker entry: OpenNext handler plus the scheduled liveness job
packages/402mcp/ The @402mcp/mcp stdio package
server.json Official MCP Registry entry
tests/ · scripts/ Unit tests, verification suites and the package buildLicense
Code: MIT (see LICENSE). Registry data: CC BY 4.0.
This server cannot be deployed
Maintenance
Related MCP Connectors
Pay for APIs with USDC. Read-only x402 payment discovery, verification, evidence, and status.
Discover machine-payable APIs, probe x402 payment terms, and run seller operations. Non-custodial.
26 pay-per-call AI agent tools for marketing, sales, content, research, verification, and integration testing. Agents pay per call via x402 micropayments (USDC on Base), raw JSON in and out. Includes delivery-acceptance receipts (ACCEPT/REJECT/REVIEW), a webhook capture/replay/conformance lab, and n8n workflow validation with bounded JSON-Patch repair.
Payment decisions, durable evidence, x402 resource discovery and live gateway status for AI agents.
Related MCP Servers
- AlicenseAqualityFmaintenanceA neutral, non-custodial payment router for AI agents: it discovers which payment rails a paid endpoint accepts (x402 on Base/EVM, Solana, MPP), then pays across them using the caller's own wallet key. Three tools — discover_payment_rails, pay_for_resource, payment_history.4MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to discover, pay for, and sell HTTP APIs using the x402 micropayment protocol, with USDC settlement on Base mainnet. Includes tools for payment requirements, paying and fetching resources, building seller configurations, and monitoring revenue.140 npm1MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search and verify machine-payable HTTP 402/x402 APIs using live probe data, providing ranked results by liveness, uptime, price, and trustworthiness.-
- AlicenseNot gradedqualityCmaintenanceExposes a live catalogue of specialist tools as MCP endpoints and returns x402 payment challenges for each call, letting agents pay per use in USDC from their own wallet without subscriptions or API keys.MIT