Sato Hub
Data Tool

Cryo MCP Server

MCP wrapper around Cryo, the Rust/Python Ethereum data-extraction tool, for bulk block/trace/log queries plus SQL.

  • Sato Score47
  • ChainsEthereum
ActiveUnverifiedDormant · 2y ago

Cryo MCP Server is an open-source data tool on Ethereum, with last code activity on 2025-03-10 (Dormant). Sato Score 47/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-21. How the score works →

See how to install Cryo MCP Server →

Last commit Mar 10, 2025 · ★ 91

Listed from github.com/z80dev/cryo-mcp on 2026-07-19. Install: not attempted. Evidence →

Next step

Watch Cryo MCP Server

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

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

https://satohub.ai/api/mcp
Run Sato Hub Preflight on z80dev/cryo-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

Cryo MCP Server exposes Paradigm's Cryo — a widely used Ethereum data-extraction tool — through MCP, letting agents pull blocks, transactions, traces, and logs as structured datasets rather than one-off balance or price lookups. It adds SQL query support via DuckDB and integrates directly with Claude Code, aimed at bulk on-chain data analysis rather than live wallet actions.

Sato Score

47/100· Medium

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

Maintenance & liveness
20/35
Code transparency
18/20
Interface verifiability
0/10
Docs & demo
0/10
Listing transparency & provenance
6/15
Independent verification
3/10

Sato Check

v0.1.5 · as of 2026-09-29
Does it take your key?
No key read found
Does your key leave?
Not yet run
Can it move funds on its own?
Unknown
Full profile, evidence and limits →

A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".

Evidence — listed vs checked · what the words mean

Listed from github.com/z80dev/cryo-mcp on 2026-07-19. Install: not attempted.

ClaimValueEvidenceSourceChecked
Chains supportedEthereumself-reportedgithub.com/z80dev/cryo-mcpas of 2026-10-21
Verification statusUnverified — not independently reviewedself-reportedgithub.com/z80dev/cryo-mcpas of 2026-10-21
Recent activitylast commit 2025-03-10observedgithub.com/z80dev/cryo-mcp2026-10-21
Install worksdocumented by the project, not run by Sato Hubnot attempted: no falsifiable install+entry probe from deploy_specself-reportedgithub.com/z80dev/cryo-mcpas of 2026-09-14
Website answersanswered (HTTP 200)observedgithub.com/z80dev/cryo-mcp2026-10-21
Daily check record90 of 90 daily checks since 2026-07-23 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-20
Takes your keyno private-key read found in what we readtracedsatohub.ai2026-09-29
Key leaves the machinenot yet run with planted test keysthe sandbox lane has not run on this versionobservedsatohub.ainot dated
Moves funds on its ownunknown — could not read what it exposestracedsatohub.ai2026-09-29
Sato Score47/100 (Medium)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.

Install — not run by us — no falsifiable install+entry probe from deploy_spec

Runtime: Python 3.8+ (uv/uvx), requires a working cryo install + DuckDB

uv tool install cryo-mcp
claude mcp add (interactive) — command: uvx, args: cryo-mcp --rpc-url <ETH_RPC_URL> [--data-dir <DATA_DIR>]

You supply: ETH_RPC_URL (required if not passed via --rpc-url, Ethereum RPC endpoint), CRYO_DATA_DIR (optional, default download directory ~/.cryo-mcp/data/)

MCP invocation: uvx cryo-mcp --rpc-url <ETH_RPC_URL> (stdio)

Read from the project’s own docs as of 2026-09-14. What a deploy spec is →

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

100%of 91 checks since 2026-07-23 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

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. Every one of them passed, so the rate covers them too.

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
47
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
Ethereum
Agent types
MCP server
Open source
Yes
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.

#ethereum#data-extraction#mcp#sql#on-chain-data
See something inaccurate or outdated?Submit a correction →

Listing History

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

  1. Jul 24, 2026
    Sato Hub began tracking this listing
  2. Jul 20, 2026
    Edited: deploy spec
  3. Jul 19, 2026
    Listed on Sato Hub

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Cryo MCP Server

Is Cryo MCP Server open source?
Yes. Cryo MCP Server is open source under the MIT license; the repository is https://github.com/z80dev/cryo-mcp. Checked as of 2026-10-21.
Which chains does Cryo MCP Server support?
Cryo MCP Server lists support for Ethereum as of 2026-10-21.
Is Cryo MCP Server still maintained?
The most recent code activity Sato Hub observed was on 2025-03-10 (last commit 2025-03-10), which Sato Hub labels "Dormant". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Cryo MCP Server?
Python 3.8+ (uv/uvx), requires a working cryo install + DuckDB. Install: uv tool install cryo-mcp. Entry: claude mcp add (interactive) — command: uvx, args: cryo-mcp --rpc-url <ETH_RPC_URL> [--data-dir <DATA_DIR>]. This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (uvx cryo-mcp --rpc-url <ETH_RPC_URL> (stdio)).
Is Cryo MCP Server verified on Sato Hub?
No independent verification is on record for Cryo MCP Server; its verification status is "Unverified" and its Sato Score is 47 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. "Cryo MCP Server — Sato Hub." Sato Hub, updated 2026-10-21, accessed 2026-10-21. https://satohub.ai/resources/cryo-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.