CryoCAUTION
A Python package for accessing Cryo datasets via Claude Code
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A Model Completion Protocol (MCP) server for the Cryo blockchain data extraction tool.
Cryo MCP allows you to access Cryo's powerful blockchain data extraction capabilities via an API server that implements the MCP protocol, making it easy to query blockchain data from any MCP-compatible client.
For LLM Users: SQL Query Workflow Guide
When using this MCP server to run SQL queries on blockchain data, follow this workflow:
- Download data with
query_dataset:
result = query_dataset(
dataset="blocks", # or "transactions", "logs", etc.
blocks="15000000:15001000", # or use blocks_from_latest=100
output_format="parquet" # important: use parquet for SQL
)
files = result.get("files", []) # Get the returned file paths- Explore schema with
get_sql_table_schema:
# Check what columns are available in the file schema = get_sql_table_schema(files[0]) # Now you can see all columns, data types, and sample data
- Run SQL with
query_sql:
# Option 1: Simple table reference (DuckDB will match the table name to file)
sql_result = query_sql(
query="SELECT block_number, timestamp, gas_used FROM blocks",
files=files # Pass the files from step 1
)
# Option 2: Using read_parquet() with explicit file path
sql_result = query_sql(
query=f"SELECT block_number, timestamp, gas_used FROM read_parquet('{files[0]}')",
files=files # Pass the files from step 1
)Alternatively, use the combined approach with query_blockchain_sql:
# Option 1: Simple table reference
result = query_blockchain_sql(
sql_query="SELECT * FROM blocks",
dataset="blocks",
blocks_from_latest=100
)
# Option 2: Using read_parquet()
result = query_blockchain_sql(
sql_query="SELECT * FROM read_parquet('/path/to/file.parquet')", # Path doesn't matter
dataset="blocks"6a57de6c5984OBSERVED · 2026-10-07Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add cryo-mcp -- uvx cryo-mcp
{
"mcpServers": {
"cryo-mcp": {
"command": "uvx",
"args": [
"cryo-mcp"
]
}
}
}Exposed tools (10)
10 read · 0 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
get_latest_ethereum_block | read | |
get_sql_examples | read | |
get_sql_table_schema | read | |
get_transaction_by_hash | read | |
list_available_sql_tables | read | |
list_datasets | read | Return a list of all available cryo datasets |
lookup_dataset | read | |
query_blockchain_sql | read | |
query_dataset | read | |
query_sql | read |
Trust audit
CAUTIONgrade B · trust 84/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | PASS |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (3 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (11)
"input": "0x3593564c000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000
"input": "0x3593564c000000000000000000000000000000000000000000000000000000000000006000000000000000000000000000000000000000000000000000000000000000a00000000000000000000000000000000000000000000000000000
"input": "0x1640ff3e000000000000000000000000000000000000000000000000000000000000003c0000000000000000000000001111111254eeb25477b68fb85ed929f73a9605820000000000000000000000000000000000000000000000000000
"input": "0xe3ead59e000000000000000000000000000010036c0190e009a000d0fc3541100a07380a0000000000000000000000005c5b196abe0d54485975d1ec29617d42d91983260000000000000000000000007c1156e515aa1a2e851674120074
"input": "0xab2b2906f79ece28da6d38d49bbb8cbb8113ecc83e93483b6afd2d9a00dd2f6e3df021240100841b5b000000000000000000000000000082202caec5e6d85014eadc68d4912f3c90093e7c2e7e3df021240001840000000000072ac83545
ethereum__blocks__00001000_to_00001004.parquet
os.environ["ETH_RPC_URL"] = "http://10.0.0.48:8545"
cmd = ["cryo", "blocks", "-b", block_range, "-r", "http://10.0.0.48:8545", "--json"]
cmd = ["cryo", "blocks", "-b", block_range, "-r", "http://10.0.0.48:8545", "--json", "-o", str(temp_dir)]
os.environ["ETH_RPC_URL"] = "http://10.0.0.48:8545"
os.environ["ETH_RPC_URL"] = "http://10.0.0.48:8545"
Gates applied: no_behavioural_pass.
6a57de6c5984full audit observations/trust-audit/mcp-server/z80dev__cryo.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-07 | 6a57de6c5984 | CAUTION | B | 84 | first audit |
Questions
What is the Cryo MCP server?
A Python package for accessing Cryo datasets via Claude Code
What tools does Cryo expose?
10 in total: 10 read-only, 0 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Cryo safe to connect to an agent?
With care. The audit graded it B (84/100) and found 11 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does Cryo need?
No credential environment variables were found in its source, so it appears to need none.
How current is this page?
The grade is for one exact copy of the source (6a57de6c5984), read on 2026-10-07. The repository is watched and re-audited when it changes.