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
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.