What it does
The server exposes 18 web data services to an agent through MCP. The publisher describes them as agent-payable: the agent pays for each call over x402 rather than holding a subscription or account with each service. The publisher also states that none of the services require an API key.
The entry fits agents that need web data from several sources and want a single MCP connection with per-call payment instead of separate accounts for each provider. It is tagged under development, data and web browsing.
Limitations and requirements
Each service call is paid by the agent through x402. The source does not list other requirements, permissions or platform limits.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.mercuryx402/mercury-x402-mcp
Agent-payable web data over x402: 18 keyless services an agent pays per call.
v1.0.1As shown on registry.modelcontextprotocol.io when we last read it