About Mercury X402 Mcp
Mercury X402 Mcp is a pay-per-call web-data MCP server for AI agents, with tools for fetching, parsing, and inspecting websites. It uses x402 payments in USDC on Base and attaches an offline-verifiable provenance receipt to results.
Key features
- 01Fetch pages and convert to Markdown
- 02Extract structured content, tables, and links
- 03Inspect sitemaps, feeds, and DNS
- 04Free catalog and receipt verification tools
- 05Pay per call with signed provenance receipts
Use cases
- 01Gather web content for RAG workflows
- 02Check page changes and availability
- 03Verify the provenance of fetched data
MCP support
It exposes web-data tools to MCP clients. The catalog and receipt verification tools are free; other calls use wallet-funded x402 pay-per-call payments.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://network.mercury-hq.com/mcpclaude mcp add --transport http mercury-x402 https://network.mercury-hq.com/mcp{"mcpServers":{"mercury-x402":{"type":"http","url":"https://network.mercury-hq.com/mcp"}}}Open in Cursor{"servers":{"mercury-x402":{"type":"http","url":"https://network.mercury-hq.com/mcp"}}}Open in VS Code{"mcpServers":{"mercury-x402":{"type":"http","url":"https://network.mercury-hq.com/mcp"}}}{"mcpServers":{"mercury-x402":{"serverUrl":"https://network.mercury-hq.com/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
18| Parameter | Type | Required | Description |
|---|---|---|---|
| url | string | Yes | the page to fetch (http/https) |
| links | enum | No | 1 = also return the outbound-link graph (crawl frontier)0 | 1 |
| format | enum | No | text (default) or structure-preserving markdowntext | markdown |
| extract | string | No | 1 = page description + wordCount; OR a comma-list of field names (e.g. title,price,author,publishedAt) to get a structured JSON record under `extract` |
Details
From the project READMEmercury-x402-mcp
17 keyless, signed-provenance web-data tools your AI agent can pay for itself — over x402 on Base mainnet (USDC). No Mercury API key, no account, no signup. Your agent calls a tool, it pays the SKU with your wallet, and gets back the result plus an EIP-191 provenance receipt it can verify offline, forever.
Tools include: clean fetch, LLM-ready markdown, structured extract, link graph, robots, diff, notarize, headers, table extract, feed, availability, validate, batch, sitemap, DNS, readability, redirect — built live from Mercury's catalog, so the list is always current.
Install
npx mercury-x402-mcp
Add to your MCP host (Claude Desktop / Cursor / Cline / any MCP client):
{
"mcpServers": {
"mercury": {
"command": "npx",
"args": ["-y", "mercury-x402-mcp"],
"env": {
"MERCURY_PRIVATE_KEY": "0xYOUR_BASE_MAINNET_WALLET_KEY"
}
}
}
}
MERCURY_PRIVATE_KEY is your Base-mainnet wallet (funded with a little USDC). Mercury is keyless —
the only thing you bring is a wallet to pay per call. Tools cost ~$0.003–$0.02 each.
The mercury_catalog and mercury_verify tools work without a wallet (free).
Why
Firecrawl / Jina / Tavily all gate behind a human-created API key + a credit-card plan — an agent can't onboard itself. Mercury can: an agent discovers the tools, pays over x402, and every result is cryptographically signed so the bytes are provably genuine and untampered — what RAG, trading, and agent-to-agent commerce actually need.
Discovery: https://mercury-x402-jed.fly.dev/.well-known/x402 · https://mercury-x402-jed.fly.dev/llms.txt
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.