4
402MCP/402mcp
MCP server and open registry for HTTP 402 agent payments: decode L402, x402 and MPP challenges and choose a payment rail.
无 SECURITY.md
在 GitHub 查看 ↗链接已于 2026-11-12 核查 · 自动访问被拒(HTTP 429),状态未能确认
安装与配置
远端端点(Claude Desktop / Cursor / Windsurf 共用 mcpServers)
{
"mcpServers": {
"402mcp-402mcp": {
"url": "https://402mcp.org/api/v1/mcp"
}
}
}把这段粘进 Claude Desktop / Cursor 的 mcpServers 配置即可。端点来自公开证据,我们没有替你安装或托管它。 官方 Registry 记录:这个端点没有列出任何请求头。这不等于免密 —— 以项目文档为准。
VS Code(.vscode/mcp.json —— 键名是 servers,远程要 type: http)
{
"servers": {
"402mcp-402mcp": {
"type": "http",
"url": "https://402mcp.org/api/v1/mcp"
}
}
}VS Code 的配置文件和另外三家不同:顶层键是 <code>servers</code>,远程端点还要写 <code>"type": "http"</code>。复制到 .vscode/mcp.json。
Claude Code(命令行)
claude mcp add --transport http 402mcp-402mcp https://402mcp.org/api/v1/mcp
Claude Code 不收 JSON 文件,用这条命令直接加。
客户端配置(取自该仓库的安装命令)
{
"mcpServers": {
"402mcp-402mcp": {
"command": "npx",
"args": ["-y", "@402mcp/mcp"]
}
}
}解析自我们于 2026-10-26 抓取的该仓库 README;我们未执行过。
command/args 来自仓库写明的安装命令;不确定时请以该项目 README 为准。
VS Code(.vscode/mcp.json —— 键名是 servers)
{
"servers": {
"402mcp-402mcp": {
"command": "npx",
"args": ["-y", "@402mcp/mcp"]
}
}
}VS Code 顶层键是 <code>servers</code>,其余与上面那份相同。
Claude Code(命令行)
claude mcp add --transport stdio 402mcp-402mcp -- npx -y @402mcp/mcp
Claude Code 不收 JSON 文件,用这条命令直接加。
配置项的键名以你的客户端为准:客户端与 CLI
- ★ 数取值
- 0 ★ · 402MCP/402mcp · 取自 GitHub 搜索 API · (2026-11-13 20:00:50 核对)
- 来源明细
- 收录自 punkpeye/awesome-mcp-servers 榜单(我们从中收集的条目之一) · 条目类型:MCP 服务
- 收录与活跃
- 收录于 2026-10-23 · 最近见到 2026-11-14 · 共见到 26 次 · 被 23 个来源列出
- 评分构成
- 综合分 2,300 · 23 个来源 · mcp
- 安装
npx -y @402mcp/mcp
常见问题(答案都来自我们的记录)
怎么安装?
该仓库给出的安装命令是
npx -y @402mcp/mcp。我们的记录里它是仓库自己提供的;不保证在你的客户端上直接可用。它适合谁 / 用来做什么?
我们把它归在这些标签下: MCP 服务。标签来自条目自身,不是我们强加的分类。
谁维护它、还在更新吗?
仓库
402MCP/402mcp;我们收录于 2026-10-23;最近见到 2026-11-14。这里没有"官方认证"或"质量评级"——我们只记录来源与时间。# 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 |
收录徽章(可选)
想把收录标记放进 README 就复制这行,可选,不影响收录。
[](https://anclum.com/zh/s/402mcp-402mcp/)
- 来源
- awesome · https://github.com/402MCP/402mcp
- 按领域浏览
- MCP 服务
- 收录来源
- 23 个独立来源
- 收录于
- 今天
- 安全策略
- 我们没在该仓库根目录找到
SECURITY.md(这不代表不安全)
同类推荐
所属领域与标签
每个标签都能点进去看同类的全部条目。数字是当前库里的真实条数。