4
402MCP/402mcp
MCP server and open registry for HTTP 402 agent payments: decode L402, x402 and MPP challenges and choose a payment rail.
no SECURITY.md
View on GitHub ↗Link checked 2026-11-12 · automated check blocked (HTTP 429), status unconfirmed
Install & config
Remote endpoint (mcpServers - Claude Desktop / Cursor / Windsurf)
{
"mcpServers": {
"402mcp-402mcp": {
"url": "https://402mcp.org/api/v1/mcp"
}
}
}Paste this into the mcpServers config of Claude Desktop or Cursor. The endpoint comes from public evidence; we do not install or host it. Official Registry record: this endpoint lists no request headers. That is not the same as key-free - the project docs decide.
VS Code (.vscode/mcp.json - the key is servers, remote needs type: http)
{
"servers": {
"402mcp-402mcp": {
"type": "http",
"url": "https://402mcp.org/api/v1/mcp"
}
}
}VS Code differs from the other three: the top-level key is <code>servers</code> and a remote endpoint also needs <code>"type": "http"</code>. Paste into .vscode/mcp.json.
Claude Code (command line)
claude mcp add --transport http 402mcp-402mcp https://402mcp.org/api/v1/mcp
Claude Code does not read a config file; add the server with this command.
Client config (built from the install command this repo gives)
{
"mcpServers": {
"402mcp-402mcp": {
"command": "npx",
"args": ["-y", "@402mcp/mcp"]
}
}
}Parsed from the README we fetched on 2026-10-26; we have not executed it.
command/args come from the install command the repository states. When it is ambiguous, the project README wins.
VS Code (.vscode/mcp.json - the key is servers)
{
"servers": {
"402mcp-402mcp": {
"command": "npx",
"args": ["-y", "@402mcp/mcp"]
}
}
}Same server, but VS Code keeps it under <code>servers</code>.
Claude Code (command line)
claude mcp add --transport stdio 402mcp-402mcp -- npx -y @402mcp/mcp
Claude Code does not read a config file; add the server with this command.
Key names differ by client: Clients & CLI
- Star count
- 0 ★ · 402MCP/402mcp · read from the GitHub search API · (checked 2026-11-13 20:00:50)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-10-23 · last seen 2026-11-14 · seen 26× · listed by 23 sources
- Score
- score 2,300 · 23 sources · mcp
- Install
npx -y @402mcp/mcp
FAQ (answers come from our records)
How do I install it?
The repository provides this install command:
npx -y @402mcp/mcp. It comes from the repository itself; we cannot guarantee it runs as-is in your client.Who is it for?
We filed it under these tags: MCP 服务. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
402MCP/402mcp;first catalogued 2026-10-23;last seen 2026-11-14。There is no official certification or quality rating here — we record sources and dates only.# 402MCP.org
以下摘录自该仓库的 README(片段) · 在 GitHub 读完整 README →
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:
bash
claude mcp add --transport http 402mcp https://402mcp.org/api/v1/mcp
Any stdio MCP client (Claude Desktop, Cursor, Windsurf and others):
json
"mcpServers": {
"402mcp": { "command": "npx", "args": ["-y", "@402mcp/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 |
| decode402challenge | Decode a 402 response (L402 macaroon and BOLT 11 invoice, x402 v1/v2, MPP) into exact next steps and the retry header |
| recommendpaymentrail | Filter by role, asset, custody, infrastructure, network, scheme, MCP support and maturity; re-weight the criteria; explain every exclusion |
| search402solutions | Search the registry with filters |
| getsolution | One entry in full, with sources and code samples |
| getschemereference | Wire format of L402, x402 or MPP |
| probe402support | One GET to a public URL to see whether it speaks 402. Never pays |
| getbestpaymentsolution | The entry with the highest composite score |
Resources: 402mcp://registry, 402mcp://methodology,
402mcp://solutions/{id}, 402mcp://schemes/{scheme}. Prompts:
choosepaymentrail, handle402response. Every tool is annotated
readOnlyHint.
Safety. Everything in a 402 response is server-controlled, so the decoder
lists those fields in untrustedfields 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 |
| POST /api/v1/mcp | MCP (JSON-RPC 2.0, streamable HTTP) |
| POST /api/v1/decode | Decode a 402 response |
| GET /api/v1/recommend | Recommend a rail from requirements |
| GET /api/v1/probe?url= | Probe a URL for 402 support (rate limited) |
| GET /api/v1/solutions | Versioned list (?q=, ?id=, ?view=full) |
| GET /api/v1/registry | Canonical feed with ETag / 304 support |
| GET /api/v1/schemes/{scheme} | Wire format of L402, x402, MPP |
| GET /api/v1/status | Daily liveness of every entry's docs and website |
| GET /api/v1/changelog · /changelog.xml · /changelog | Changes and corrections |
| /schema/v1/registry.json · /schema/v1/solution.json | JSON Schemas (draft 2020-12) |
| /openapi.json | OpenAPI 3.1 |
| /llms.txt · /llms-full.txt | Plain-text indexes |
| /.well-known/402.json · api-catalog · mcp/server-card.json · agent-skills/ | Discovery |
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:
bash
claude mcp add --transport http 402mcp https://402mcp.org/api/v1/mcp
Any stdio MCP client (Claude Desktop, Cursor, Windsurf and others):
json
"mcpServers": {
"402mcp": { "command": "npx", "args": ["-y", "@402mcp/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 |
| decode402challenge | Decode a 402 response (L402 macaroon and BOLT 11 invoice, x402 v1/v2, MPP) into exact next steps and the retry header |
| recommendpaymentrail | Filter by role, asset, custody, infrastructure, network, scheme, MCP support and maturity; re-weight the criteria; explain every exclusion |
| search402solutions | Search the registry with filters |
| getsolution | One entry in full, with sources and code samples |
| getschemereference | Wire format of L402, x402 or MPP |
| probe402support | One GET to a public URL to see whether it speaks 402. Never pays |
| getbestpaymentsolution | The entry with the highest composite score |
Resources: 402mcp://registry, 402mcp://methodology,
402mcp://solutions/{id}, 402mcp://schemes/{scheme}. Prompts:
choosepaymentrail, handle402response. Every tool is annotated
readOnlyHint.
Safety. Everything in a 402 response is server-controlled, so the decoder
lists those fields in untrustedfields 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 |
| POST /api/v1/mcp | MCP (JSON-RPC 2.0, streamable HTTP) |
| POST /api/v1/decode | Decode a 402 response |
| GET /api/v1/recommend | Recommend a rail from requirements |
| GET /api/v1/probe?url= | Probe a URL for 402 support (rate limited) |
| GET /api/v1/solutions | Versioned list (?q=, ?id=, ?view=full) |
| GET /api/v1/registry | Canonical feed with ETag / 304 support |
| GET /api/v1/schemes/{scheme} | Wire format of L402, x402, MPP |
| GET /api/v1/status | Daily liveness of every entry's docs and website |
| GET /api/v1/changelog · /changelog.xml · /changelog | Changes and corrections |
| /schema/v1/registry.json · /schema/v1/solution.json | JSON Schemas (draft 2020-12) |
| /openapi.json | OpenAPI 3.1 |
| /llms.txt · /llms-full.txt | Plain-text indexes |
| /.well-known/402.json · api-catalog · mcp/server-card.json · agent-skills/ | Discovery |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/402mcp-402mcp/)
- Source
- awesome · https://github.com/402MCP/402mcp
- Browse by field
- MCP servers
- Listed by
- 23 independent sources
- added
- today
- Security policy
- no
SECURITY.mdat the repository root (which does not mean it is unsafe)
More like this
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.