catena-x402-mcp-demo
An MCP server whose tool invocations are metered and charged over x402, plus a paying-proxy reference client that lets any standard MCP client use the paid tool without knowing x402 exists.
README
catena-x402-mcp-demo
An MCP server whose tool invocations are metered and charged over x402, plus a paying-proxy reference client that lets any standard MCP client use the paid tool without knowing x402 exists. Settlement is real testnet USDC on Base Sepolia, landing in a Catena sandbox account.
flowchart LR
CL["Standard MCP client<br/>Claude Code, Inspector"] -->|stdio JSON-RPC| PX["Paying proxy<br/>holds the wallet, spend cap"]
PX -->|Streamable HTTP + x402| SV["Paid MCP server<br/>gate in front of the handler"]
SV -->|verify then settle| F[Facilitator]
F -->|USDC| CA[(Catena sandbox account)]
classDef pay stroke-width:2px
class PX,SV pay
sequenceDiagram
autonumber
participant C as Standard client
participant P as Paying proxy
participant S as Paid MCP server
participant F as Facilitator
C->>P: tools/list
P->>S: tools/list
S-->>P: tools (free)
P-->>C: tools
C->>P: tools/call premium_market_signal
P->>S: POST (no payment yet)
S-->>P: 402 challenge
P->>P: within the spend cap? reserve it
P->>S: retry with signed payment
S->>F: verify
F-->>S: valid
S->>S: tool runs, response buffered
alt handler succeeded
S->>F: settle
F-->>S: settled
S-->>P: 200 result released
else handler returned 4xx
S->>S: settlement cancelled
S-->>P: error, nothing charged
end
P-->>C: ordinary tool result
How it works
The x402 challenge lives at the HTTP layer of the MCP Streamable HTTP transport, underneath the JSON-RPC framing, so the MCP protocol itself is untouched and standard clients stay compatible.
initialize,tools/list, and the freepricingtool cost nothing.tools/callonpremium_market_signaldraws a 402 with an x402 v2 challenge (exact scheme). The proxy pays it, the facilitator settles into the configuredpayTo, and only then does a successful tool result return. Middleware order is the invariant: unpaid calls never reach the tool handler; MCP HTTP 4xx cancels settlement.- The proxy refuses a paid call BEFORE paying when its running total would
pass
PROXY_SPEND_CAP_USD. The cap is configuration, never derived from tool arguments, so a prompt-injected tool call cannot raise it.
More detail: docs/architecture.md.
Setup (sandbox, ~10 minutes)
Requires Node >= 22.13 and pnpm.
pnpm install
cp .env.example .env
# SELLER_PAY_TO_ADDRESS: your Catena sandbox account's base-sepolia USDC
# deposit address, from app.catena.com
# BUYER_EVM_PRIVATE_KEY: a testnet wallet the proxy pays from. Fund it with
# Base Sepolia USDC at https://faucet.circle.com (select Base Sepolia).
# USDC only; no ETH is needed, transfers are gasless EIP-3009.
Demo: the whole loop in one command
pnpm demo
Boots the paid server against the public x402 facilitator, drives a standard MCP client through the paying proxy, and prints: free discovery, then the paid tool call settling ~$0.001 of testnet USDC into the Catena deposit address.
Use it from Claude Code (standard client)
Run the paid server in one terminal (pnpm server), then register the proxy
as an ordinary stdio MCP server in .mcp.json:
{
"mcpServers": {
"paid-market-signal": {
"command": "pnpm",
"args": ["--dir", "/path/to/catena-x402-mcp-demo", "proxy"]
}
}
}
The proxy reads BUYER_EVM_PRIVATE_KEY and UPSTREAM_MCP_URL from this
repo's own .env, so no secret goes into .mcp.json. (.mcp.json is
gitignored here anyway; keep it that way if you copy this setup.)
Claude Code lists both tools and calls them normally; the proxy pays the 402
behind the scenes. MCP Inspector works the same way:
npx @modelcontextprotocol/inspector pnpm proxy.
Tests
pnpm test runs the server and proxy suites against an in-process server
with a recording fake facilitator; no network, no money. They prove:
discovery is free, an unpaid paid-tool call is refused with a 402 before the
tool runs, a paid call settles exactly once, MCP 4xx does not settle, and
the proxy refuses an over-cap call before any payment.
Scope
Consumes public surfaces only: the MCP TypeScript SDK (v1, protocol 2025-11-25; the v2 SDK targeting the 2026-07-28 spec is beta, and migration is import-path-level), the public x402 packages and facilitator, and a Catena sandbox account as the receiving side.
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。