How do I install X402?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does X402 need an API key?

The publisher lists these environment variables: BASE_PRIVATE_KEY.

When was X402 last checked?

Last checked 2026-11-09. Pay-per-call x402 tools on Base: web extract/render, burn-once secret vault, chart, GeoTIFF

X402 MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Credentials from the publisher

BASE_PRIVATE_KEY — 0x-prefixed EVM private key, wallet funded with Base USDC -- signs EIP-3009 payments locally.

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1BASE_PRIVATE_KEY=<secret> claude mcp add io.github.jannis-e-x402-mcp-server -- npx -y x402-mcp-server_by_milza@1.0.5

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.jannis-e-x402-mcp-server": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ],9      "env": {10        "BASE_PRIVATE_KEY": "<secret>"11      }12    }13  }14}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.0.5
API key

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

x402-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_KEY must 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_KEY in your MCP client config, as shown above.

Security

BASE_PRIVATE_KEY never leaves your machine. It is read once from the local environment and used only to sign EIP-712 typed-data (EIP-3009 TransferWithAuthorization) payment authorizations locally with viem.
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 402 challenge 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 402 challenge 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

X402

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install X402?

Does X402 need an API key?

What transport does X402 use?

When was X402 last checked?

Documentation

x402-mcp-server

Tools

Quickstart

How payment works

Security

Requirements

License

Links