Data · Remote MCP server
Mercury X402 MCP
Agent-payable web data over x402: 18 keyless services an agent pays per call.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.mercuryx402/mercury-x402-mcp- Version
- 1.0.1
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-06-07
- Updated
- 2026-06-07
- Publisher
- mercuryx402 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/mercuryx402) · how
- Repository
- github.com/mercuryx402/mercury-x402-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://network.mercury-hq.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- mercury-x402 1.0.0 · protocol 2025-06-18
- Tools discovered
18 - show names
fetch,extract,markdown,metadata,links,robots,diff,notarize,headers,table,feed,availability,validate,batch,sitemap,dns,readability,redirect- Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | mercury-x402-mcp | 1.0.1 | stdio |
How to connect Mercury X402 MCP
Mercury X402 MCP is a remote MCP server: there is nothing to install. Its endpoint is https://network.mercury-hq.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: mercury-x402-mcp version 1.0.1. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y mercury-x402-mcp@1.0.1.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"mercury-x402-mcp": {
"command": "npx",
"args": [
"-y",
"mercury-x402-mcp@1.0.1"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| MenhthienConnect astrology chart data from menhthien.com to Claude Desktop and MCP-compatible AI assistants. | Local · stdio |
| Meok Bs7121 MCPBS 7121 lift-plan compliance for UK crane + hiab operators. Parts 1/3/4/5 clause lookup, Appointed. | Local · stdio |
| Meok Omnibus Tracker MCPEU Digital Omnibus AI Act tracker - Track delay status by article. First-mover advantage for SEO + b. | Local · stdio |
| MerchantwordsAmazon keyword volume, reverse-ASIN, and SERP data across 11 marketplaces. | Remote · HTTPLive check: ✓ handshake |
| Merx - European Business DataEuropean business data - French company check, EU VAT validation, legal search. | Remote · HTTPLive check: sign-in required |
| MeSquared VisibilityPublic-site SEO/AEO readiness scans with evidence scores, issues, and clear measurement scope. | Remote · HTTPLive check: ✓ handshake |
| Met NoMET Norway (api.met.no) MCP - global weather, Nordics specials. | Remote · HTTPLive check: ✓ handshake |
| Meta Ad Intel ServerMeta ads plus advertiser contacts via Apify enrichment. | Remote · HTTPLive check: sign-in required |