MCP.so
登录

X402 List MCP Server已验证已精选

@mcccsm

基本信息

关于 X402 List MCP Server

x402-list.com 的 MCP 服务器:发现 x402 支付服务,并查看经链上验证的 facilitator 结算量。以 x402-list-mcp 发布在 npm 上。

#x402#agentic payments#402

X402 List MCP Server 配置

使用下面的配置,将此服务器添加到你的 MCP 客户端。

{
  "mcpServers": {
    "x402-list-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "x402-list-mcp"
      ]
    }
  }
}

X402 List MCP Server 工具

7

Your first call when you do not know which x402 service exists for a job: it narrows the directory of listed services to candidates. Filter by free-text query, category, network, live status, and whether the last observed 402 envelope is signable by a standard x402 client; sort by newest, uptime, cheapest, or endpoints. Returns up to 100 compact summaries a page: price in decimal USD, uptime, status, verification. Then x402_get_service for the full record.

Call this once you hold a slug and are deciding whether to commit to that service: the full record behind a directory row. Live status, uptime over 24h/7d/30d/90d, average response time, networks and settlement asset, every priced endpoint, and the assessment block. include_series=true adds 90 daily points of on-chain volume and distinct buyers. Read the units map in the response: the per-endpoint price field is atomic token units, not dollars.

Call this when you have a need in words and want one service to call rather than a list to read: it is the free ranking step between searching and paying. Pass the need as q, plus any category, network, price cap or verification requirement, and get up to 20 ranked recommendations with the basis each one placed on. Ranking is mostly per-service reliability (live status, verification, uptime, response time), x402 compliance, and price in USD, with a small (about 10%) weight on measured on-chain settlement traction that can never dominate those three. The response carries ranking_version (currently 3), need_blind_ranking (true when no q was given, so the order is global quality rather than your need), and a units map holding every scoring caveat in full: the compliance cap, the pro-quota rule for shared payout addresses, renormalization, the $10 volume floor, and the single-buyer discount. Read units before comparing scores across generations.

Call this before you send a payment, or right after a call unexpectedly failed: is this service up right now. With no slug, the directory snapshot: five status counts across the directory (include_services=true attaches every row). With a slug: that service's status, its 24h/7d/30d/90d uptime windows, response time, consecutive failures, daily snapshots. No money fields.

Call this when the question is about the rail rather than the service: which x402 facilitator actually settles money, and how much. Returns on-chain-verified settlement volume and transaction counts per facilitator for today (UTC), 7d, 30d and all-time, plus a verification flag ('on-chain' once volume has been observed on-chain, else 'listed'), across more than 30 facilitators. Optional daily timeseries (up to 90 days) and per-chain breakdown. Volume is decimal USD. Caveats: PER-FACILITATOR, never per-service; the *_24h fields cover today (UTC) so far, not a trailing 24 hours, and reset at 00:00 UTC, so prefer 7d.

Call this when the free signals have run out: you hold 2 to 8 finalists from x402_search_services or x402_find_best_service, their stored fields do not separate them for YOUR stated need, and choosing wrong costs more than a quarter. It buys one fresh AI assessment reasoned against your question, not a cached grade; reading an already-computed assessment stays free via x402_get_service. Price: a one-time $0.25 USDC on Base, over two calls. Call once WITHOUT payment_signature_b64 to receive the x402 payment challenge verbatim (accepts[], amount, payTo, and a base64 PAYMENT-REQUIRED header); sign accepts[0] client-side with your own wallet; call again with the SAME question and services plus payment_signature_b64 to receive the report and a base64 PAYMENT-RESPONSE settlement receipt. This server holds no keys, never signs and never settles: it only relays the challenge. Optionally add probe { slug, endpoint_path? } to have one listed service paid and called for real and its answer analyzed: the challenge is then priced at $0.25 plus that endpoint price X, and the report gains a probe_report block with a verdict and truncated extracts, never the verbatim third-party body. When live probing is not armed the probe is ignored. Caveats: read the amount to sign from accepts[0].amount, never from a fixed figure, since a probe changes it; probe fees are non-refundable whatever the verdict; if the fresh run cannot be produced the server answers before settling, so you are never charged for nothing; there is no refund. Prices are US dollars.

Call this before you trust anything you cached about a service, and right after a payment failed for no obvious reason: the monitor's log of what moved under you. Returns payTo, price and 402-schema changes observed on listed services, most recent first, in exactly three event types (payto_changed, price_changed, schema_changed). Filter with service (the slug), type, and days (1 to 365, default 90). Caveats: prices here are atomic token amounts, never dollars, and every payTo is masked by design, so the feed reports THAT the payout address changed, never the address. Free and read-only.

概览

什么是 x402-list MCP Server?

x402-list MCP Server 是 x402-list.com 的 MCP 服务器。x402-list.com 是一个收录接受 x402(HTTP 402 稳定币)支付服务的目录。它让 AI 智能体发现 x402 服务、查看可用性和价格,并检查各 facilitator 经链上验证的结算量。

该包以 x402-list-mcp 发布在 npm 上,是对公开 x402-list HTTP JSON API 的轻量封装。它不持有任何密钥、不访问数据库,也不向目录写入任何内容。七个工具中有六个免费且只读。第七个 x402_assess_services 是付费工具,作为透传:它转发一个由你在客户端自行签名的 x402 支付质询,该包从不持有密钥、从不签名、也从不结算。源代码以 MIT 许可发布在 github.com/mcccsm/x402-list-mcp。

如何使用 x402-list MCP Server?

你可以在本地通过 stdio 运行 npm 包,也可以连接托管服务器 https://mcp.x402-list.com/mcp(Streamable HTTP)。本地使用需要 Node.js 20 或更高版本以及 npm。两种方式都不需要 API 密钥。

Claude Code

本地包:

claude mcp add --transport stdio x402-list -- npx -y x402-list-mcp

或托管服务器:

claude mcp add --transport http x402-list https://mcp.x402-list.com/mcp

二选一即可。

Claude Desktop

将以下条目添加到 claude_desktop_config.json 并重启客户端:

{
  "mcpServers": {
    "x402-list": {
      "command": "npx",
      "args": ["-y", "x402-list-mcp"]
    }
  }
}

Cursor

将托管服务器添加到 .cursor/mcp.json(项目)或 ~/.cursor/mcp.json(全局),或使用 README 中的安装链接:

{
  "mcpServers": {
    "x402-list": {
      "url": "https://mcp.x402-list.com/mcp"
    }
  }
}

VS Code

将以下内容添加到 .vscode/mcp.json,然后启动服务器并在 Copilot 智能体模式中使用:

{
  "servers": {
    "x402-list": {
      "type": "http",
      "url": "https://mcp.x402-list.com/mcp"
    }
  }
}

Codex

codex mcp add x402-list --url https://mcp.x402-list.com/mcp

自托管 HTTP

MCP_HTTP_PORT=3000 npx -y x402-list-mcp --http

客户端随后连接 http://localhost:3000/mcp,http://localhost:3000/healthz 会返回 {"status":"ok"}。可选环境变量包括 X402_LIST_BASE_URL、X402_LIST_TIMEOUT_MS(默认 15000)、MCP_ALLOWED_ORIGINS 和 MCP_ALLOWED_HOSTS。

x402-list MCP Server 的主要功能

  • 按关键词、类别、网络、在线状态以及服务的 402 响应是否可被标准 x402 客户端签名,搜索和筛选 x402-list 目录。
  • 完整的服务记录:端点、每个端点的美元价格、24 小时 / 7 天 / 30 天 / 90 天可用率、网络和结算资产。
  • 服务端排名,综合考量可靠性、x402 合规性和价格,并给链上实际使用量一个较小权重。
  • 各 facilitator 经链上验证的结算量和交易笔数。
  • 已收录服务的 payTo、价格和 402 schema 变更记录。
  • 不持有密钥、不签名、不写入;API 返回的收款地址均已脱敏。

x402-list MCP Server 工具

  • 发现: x402_search_services 把目录缩小到候选服务,x402_get_service 返回某个 slug 的完整记录,x402_find_best_service 根据文字描述的需求返回最多 20 个排序推荐,并标注 ranking_version,分数只应在同一评分版本内比较。
  • 监控: x402_check_health 报告整个目录或单个服务的实时状态,x402_change_events 列出观察到的 payto_changed、price_changed 和 schema_changed 事件,可按 service、type 和 days 筛选。
  • 市场数据: x402_facilitator_volumes 返回各 facilitator 今日(UTC)、7 天、30 天和累计的结算量,并附链上验证标记。
  • 付费评估: x402_assess_services 以 Base 上 0.25 USDC 的价格,对 2 到 8 个候选服务进行一次全新的 AI 比较。先不带 payment_signature_b64 调用以获取质询,在客户端签名后重试。

x402-list MCP Server 的使用场景

  • 为任务寻找付费 API:“找一个在 Base 上、当前在线且可签名的图像生成 x402 服务。”
  • 付款前检查服务:“这个服务现在在线吗?30 天可用率是多少?”
  • 排查支付失败:“这个服务的 payTo 或价格最近变过吗?”
  • 研究生态:“本月哪些 x402 facilitator 有真实的链上结算量?”
  • 在相近选项之间取舍:“针对我的用例评估这三个候选服务。”

x402-list MCP Server 常见问题排查

  • 本地服务器无法启动: 本地使用需要 Node.js 20 或更高版本以及 npm。使用托管 URL 则完全不需要本地 Node.js。
  • x402_change_events 忽略了筛选条件: 参数名是 service(目录中的 slug),而不是 slug。
  • 价格看起来非常大: pricing[].price 是链上代币的原始最小单位数量;只有 price_usd 是美元金额。
  • 分数对不上: 只在相同的 ranking_version 内比较 x402_find_best_service 的分数。
  • 请求超时: 调大 X402_LIST_TIMEOUT_MS(默认 15000 毫秒)。

常见问题

1

x402-list MCP Server 免费吗?

七个工具中有六个免费且只读。只有 `x402_assess_services` 收费,价格为 Base 上 0.25 USDC;如果加上实时探测目标,还需加上该端点的价格。

2

x402-list MCP Server 需要 API 密钥或钱包吗?

不需要 API 密钥。付费评估工具需要你在自己这一端签署 x402 支付质询;该包从不持有密钥,也不签名。

3

应该用托管服务器还是 npm 包?

都可以。托管服务器 `https://mcp.x402-list.com/mcp` 无需本地安装,`npx -y x402-list-mcp` 则在本地通过 stdio 运行。每个客户端选择一种传输方式即可。

4

它会代我付款吗?

不会。它从不持有密钥、从不签名、从不结算,只为付费工具转发 x402 质询。

5

facilitator 结算量衡量的是什么?

它是按 facilitator 汇总、经链上验证的结算量。README 提醒不要把它与单个服务的使用量混淆,后者是刻意保守的低估值。

6

x402-list MCP Server 支持哪些客户端?

README 介绍了 Claude Code、Claude Desktop、Cursor、VS Code 和 Codex,以及任何 stdio 或 Streamable HTTP 客户端。

评论

金融与商务 分类下的更多 MCP 服务器