Sato Hub
MCP

Mercury x402 MCP

Pay-per-call MCP server (x402, USDC on Base) offering keyless web-read, structured extraction, and markdown tools with signed provenance receipts.

  • Sato Score37
  • ChainsBase, Polygon +2
EarlyUnverified

Mercury x402 MCP is a MCP server on Base, Polygon, Avalanche and other chains, with no code activity tracked. Sato Score 37/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

Check what an install would ask of your keys, before you run it →

No code activity tracked

Listed from network.mercury-hq.com on 2026-07-19. Install: not attempted — no install path on record. Evidence →

Next step

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Ask Sato Hub what is on record about Mercury x402 MCP before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Mercury is an MCP server that lets agents fetch, extract, and convert web content to markdown without an API key, paying per call over HTTP 402 in USDC on Base mainnet. Each result ships a cryptographically signed (EIP-191) provenance receipt an agent can verify offline, aimed at RAG and agent-to-agent commerce use cases that need proof of what was fetched and when; the server showed 98.3% 30-day uptime on Smithery at time of review.

Sato Score

37/100· Low

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
0/20
Interface verifiability
8/10
Docs & demo
0/10
Listing transparency & provenance
5/15
Independent verification
4/10

Evidence — listed vs checked · what the words mean

Listed from network.mercury-hq.com on 2026-07-19. Install: not attempted — no install path on record.

ClaimValueEvidenceSourceChecked
Chains supportedBase, Polygon, Avalanche, Seiself-reportednetwork.mercury-hq.comas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportednetwork.mercury-hq.comas of 2026-10-21
Website answersanswered (HTTP 200)observednetwork.mercury-hq.com2026-10-21
Daily check record49 of 50 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Sato Score37/100 (Low)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-21

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Observed record — 91 daily checks since 2026-07-23

98%of 51 checks since 2026-09-01 succeeded
Currently responding for 41 days
Succeeded
87
Failed
4
Their error
0
Unattributed
4

State changed on 2026-08-30 (responding → unclear), 2026-08-31 (unclear → responding), 2026-09-10 (responding → unreachable from our probe), 2026-09-11 (unreachable from our probe → responding).

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 40 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.

Last 30 days — to 2026-10-21, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
37
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Base, Polygon, Avalanche, Sei
Agent types
MCP server (x402 payments)
Open source
Unknown
Pricing
Pay-per-call via x402 (USDC on Base), $0.003-$0.008/call
Last checked
2026-10-21

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#mcp#x402#web-scraping#provenance#usdc

Where Mercury x402 MCP fits

Related concepts: How Agents Use Wallets, What Are Onchain Agents?

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Mercury x402 MCP's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 19, 2026
    Auto-enriched: has pricing
  2. Jul 24, 2026
    Sato Hub began tracking this listing
  3. Jul 19, 2026
    Status: Active → Early
  4. Jul 19, 2026
    Edited: category
  5. Jul 19, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Mercury x402 MCP

Is Mercury x402 MCP open source?
Unknown. Sato Hub has not found a public repository or a license statement for Mercury x402 MCP as of 2026-10-21.
Which chains does Mercury x402 MCP support?
Mercury x402 MCP lists support for Base, Polygon, Avalanche, Sei as of 2026-10-21.
Is Mercury x402 MCP still maintained?
Sato Hub tracks no commit or release for Mercury x402 MCP; it cannot say whether it is maintained.
How do I install or run Mercury x402 MCP?
Sato Hub has no deploy spec for Mercury x402 MCP; follow the project's own documentation.
Is Mercury x402 MCP verified on Sato Hub?
No independent verification is on record for Mercury x402 MCP; its verification status is "Unverified" and its Sato Score is 37 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Mercury x402 MCP — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/mercury-x402-mcp

Data last refreshed 2026-10-21; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.