mcp-registry/io.github.mercuryx402/mercury-x402-mcp · v1.0.0
Also listed as glama/mercuryx402/mercury-x402-mcp
As of 2026-10-20 13:36 UTC, the Mercuryx402 Mercury X402 MCP server is up with a Glimind reliability score of 66/100 (grade C). Over the last 30 days it answered 98.4% of Glimind's liveness checks. It had 965 outages in 90 days, with a median recovery of 3 minutes.
Agent-payable web data over x402: 18 keyless services an agent pays per call.
Claude Code
claude mcp add --transport http mercuryx402-mercury-x402-mcp-server https://network.mercury-hq.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"mercuryx402-mercury-x402-mcp-server": {
"type": "http",
"url": "https://network.mercury-hq.com/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
18 of 18 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
Reachable 98.4% of the time over the last 30 days; median recovery 3 min.
Agents fail over to an alternative the first time a call fails. Add health checks and restart-on-failure, and avoid cold starts on serverless hosts.
Handshake + tools/list takes ~2,345 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.mercuryx402%2Fmercury-x402-mcp/fixes
{
"name": "fetch",
"description": "VERIFIABLE keyless web-read for autonomous agents. Every result ships a cryptographically SIGNED provenance receipt (EIP-191 over sha256(text)+url+status+time) — the wedge a free scraper structurally CANNOT match: Jina r.jina.ai is free+keyless too, but its bytes are HEARSAY (no proof of what/where/when). MERCURY's `attestation` is ecrecoverable OFFLINE, forever, by you OR any downstream agent you forward the bytes to — proving the content is genuine + untampered (key pinned at /.well-known/merc",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"maxLength": 2048,
"description": "the page to fetch (http/https)"
},
"links": {
"enum": [
"0",
"1"
],
"type": "string",
"description": "1 = also return the outbound-link graph (crawl frontier)"
},
"format": {
"enum": [
"text",
"markdown"
],
"type": "string",
"description": "text (default) or structure-preserving markdown"
},
"extract": {
"type": "string",
"maxLength": 256,
"description": "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`"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "readability",
"description": "URL → a clean ARTICLE record { title, byline, publishedAt, article text } with boilerplate (nav/header/footer/sidebar/ads/share-bars/comment-forms) stripped via deterministic DOM density heuristics, plus a signed provenance receipt pinning the cleaned article to its source — the clean-citation primitive distinct from raw markdown. Deterministic (no LLM): same URL + same source bytes ⇒ byte-identical output. — $0.005/call",
"inputSchema": {
"type": "object",
"required": [
"url"
],
"properties": {
"url": {
"type": "string",
"maxLength": 2048,
"description": "the article page to extract (http/https)"
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "validate",
"description": "URL (a JSON/API endpoint) + a JSON Schema in → a deterministic pass/fail with per-field errors (missing/wrong-type/enum/range/pattern), plus a signed provenance receipt binding the verdict to the exact response bytes AND the exact schema. Deterministic, keyless, no LLM — x402, USDC on Base mainnet. — $0.005/call",
"inputSchema": {
"type": "object",
"required": [
"url",
"schema"
],
"properties": {
"url": {
"type": "string",
"maxLength": 2048,
"description": "the JSON/API endpoint to fetch + validate (http/https)"
},
"schema": {
"type": "string",
"maxLength": 16384,
"description": "the JSON Schema to validate against. THREE accepted forms: (1) COMPACT URL-native comma list of field[:type] (type in string|number|integer|boolean|array|object|null; default string), e.g. id:integer,name,price:number,inStock:boolean — every field becomes a REQUIRED typed property; (2) a JSON-Schema string (Draft-07 core subset: type/required/properties/items/enum/const/min*/max*/pattern/format/additionalProperties/nullable/anyOf/oneOf/allOf/not); (3) a shorthand-map string {\"id\":\"integer\",\"name\":\"string\"}."
},
"pointer": {
"type": "string",
"maxLength": 256,
"description": "optional JSON-Pointer (e.g. /data or /result/0) to validate a SUB-DOCUMENT of the response instead of the whole body (for APIs that wrap the payload)."
}
},
"additionalProperties": false
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.mercuryx402/mercury-x402-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.mercuryx402/mercury-x402-mcp"}) over MCP.
validate ~378 tokensextract ~339 tokenssitemap ~327 tokensfetch ~323 tokensdiff ~301 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.mercuryx402%2Fmercury-x402-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.mercuryx402%2Fmercury-x402-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mercuryx402%2Fmercury-x402-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.mercuryx402%2Fmercury-x402-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.mercuryx402%2Fmercury-x402-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:e6f8d1bd6efb381f…, first seen 2026-10-17, included at leaf 2794 of 33,178. Version history · verify what your client received.
Compare: most reliable web servers · most reliable data servers · most reliable security servers · most reliable knowledge servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-20 13:36 UTC, the Mercuryx402 Mercury X402 MCP server is up with a Glimind reliability score of 66/100 (grade C). Over the last 30 days it answered 98.4% of Glimind's liveness checks. It had 965 outages in 90 days, with a median recovery of 3 minutes.
Mercuryx402 Mercury X402 MCP server advertises 22 tools, including availability, batch, diff, dns, extract.
Point your MCP client at this streamable-http endpoint: https://network.mercury-hq.com/mcp
Glimind scanned all 18 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.