About x402-mcp-server
x402-mcp-server exposes paid web, charting, secret-vault, and GeoTIFF tools to AI agents. It handles x402 payment challenges per call using a locally held Base wallet, with prices charged in USDC.
Key features
- 01Extract public pages as Markdown
- 02Render JavaScript-heavy pages to Markdown
- 03Share a secret through a single-use claim link
- 04Generate deterministic SVG bar charts
- 05Convert GeoTIFF data to PNG or WebP
Use cases
- 01Retrieve clean text from a public URL
- 02Render a JavaScript-based page for analysis
- 03Deliver a secret once through a claim link
- 04Create a chart from labeled values
- 05Convert geospatial imagery with map metadata
MCP support
The MCP server exposes five x402-paywalled tools. It signs EIP-3009 payment authorizations locally and submits them to pay per call on Base Mainnet in USDC.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
npx -y x402-mcp-server_by_milzaBASE_PRIVATE_KEYSecret0x-prefixed EVM private key, wallet funded with Base USDC -- signs EIP-3009 payments locally.Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.
Tools
5Saved tool list · updated 2w ago
This tool takes no parameters.
Details
From the project READMEx402-mcp-server
A small, growing catalog of x402-paywalled HTTP tools on Base Mainnet via x402 micro-payments — no API keys, no signup, pay per call in USDC.
This MCP server exposes that catalog as native MCP tools. Every tool call pays for itself automatically: the server POSTs the request, catches the real x402 v2 402 PAYMENT-REQUIRED challenge, signs an EIP-3009 TransferWithAuthorization with viem using a local wallet, and resubmits with the PAYMENT-SIGNATURE header. No human signature prompt at call time — the agent just calls the tool.
Tools
| Tool | Cost (USDC) | Description | Key input parameters |
|---|---|---|---|
markdown-extractor | 0.01 | Fetches a public URL and returns clean, token-efficient markdown, paywalled with the x402 v2 protocol on Base Mainnet. Designed for autonomous AI agents to call directly: no API key, no signup — pay per call in USDC. | url (string, required) |
spa-dom-to-md | 0.03 | Renders JavaScript-heavy SPA pages in real headless Chromium via Cloudflare Browser Rendering, waits for network-idle / selector-ready, strips nav/footer/script chrome, and serializes the fully-rendered DOM into clean, LLM-ready Markdown. | url (string, required) |
burn-once-secret-vault | 0.01 | Store a secret (API key, webhook payload, signed URL) encrypted with WebCrypto AES-256-GCM and share a claim URL that yields the secret exactly once. A Durable Object serializes reads so single-use delivery is race-free, and every burn returns an Ed25519-signed attestation. Creating a vault requires x402 payment; the recipient's claim read (GET /v/:vault_id) is free. | secret (string, required) |
svg-bar-chart-renderer | 0.015 | Deterministic, paid-per-render SVG bar chart generator for LLM agents. Accepts labeled scalar data and layout options, performs exact geometry math (min/max normalization, nice-interval y-axis ticks, label spacing, bar-width distribution), and returns schema-valid, escape-correct SVG with identical input always yielding byte-identical output. | data (array, required) |
wasm-geotiff-transcoder | 0.03 | Decodes a GeoTIFF/COG (https URL or inline base64), reads the selected RGB bands via windowed overview reads, applies a tone-map stretch, and returns a PNG/WebP plus georeference metadata (CRS, bounds, pixel scale) and source stats. Limits: 20 MB source, 2048 px output width. Billed per attempt: payment settles after structural validation, before decode, so decode-time failures (e.g. a bands_rgb band the source lacks) are still charged. | exactly one of source or or_base64_body (required) |
All tools run on Base Mainnet (eip155:8453). Settlement happens server-side through an ordered facilitator chain — Coinbase CDP, then PayAI, then Primer as fallbacks — which changes nothing on your side: you sign the same EIP-3009 authorization either way, and every tool is also listed in the CDP and PayAI x402 Bazaar discovery catalogs. Exact request-body fields for each tool are also discoverable at runtime via <tool-url>/openapi.json.
Quickstart
Add this to your claude_desktop_config.json:
{
"mcpServers": {
"x402-mcp-server": {
"command": "npx",
"args": ["-y", "x402-mcp-server_by_milza"],
"env": {
"BASE_PRIVATE_KEY": "0xyour_base_mainnet_private_key"
}
}
}
}
⚠️ Funding warning:
BASE_PRIVATE_KEYmust be a Base Mainnet wallet private key funded with a small amount of real USDC (e.g. $0.50 is enough for dozens of calls at these prices). Every tool call spends real money from this wallet. Do not use a key that holds funds you're not prepared to spend through this server, and never commit this key to source control.
Once configured, restart Claude Desktop and the tools listed above become available to the assistant automatically — no further setup, no dashboard, no API key registration.
How payment works
BASE_PRIVATE_KEY is your own wallet — whoever installs this server sets their own key and pays for their own calls. Each call settles straight to the tool provider's wallet; your key never touches anyone else's funds and no one else's key ever touches yours. To set it up:
- Use (or create) a Base Mainnet EVM wallet you're OK spending small amounts from.
- Fund it with a bit of USDC on Base (e.g. $0.50).
- Export its private key and set it as
BASE_PRIVATE_KEYin your MCP client config, as shown above.
Security
BASE_PRIVATE_KEYnever leaves your machine. It is read once from the local environment and used only to sign EIP-712 typed-data (EIP-3009TransferWithAuthorization) payment authorizations locally withviem.- No raw private key, seed phrase, or signature is ever sent over the network — only the resulting signed authorization, exactly as the x402 protocol requires to settle payment for the specific request being made.
- Payment terms (recipient, amount, network, asset contract, expiry) are read fresh from each live
402challenge returned by the resource server, never trusted from a local cache, so a stale or tampered local catalog can't redirect funds. - Spending ceiling: the live
402challenge is trusted for signing mechanics (domain, nonce window, asset) but never for the amount. Every call checks the challenge's requested amount against this catalog's known price for that tool and refuses to sign anything higher — a hijacked, compromised, or buggy endpoint can't get a blank-check signature just by asking for more. - This package does not phone home, collect telemetry, or store your key anywhere on disk.
Requirements
- Node.js 18+
- A Base Mainnet EVM wallet, funded with a small amount of USDC, whose private key you control
License
MIT
Links
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.