nuthatch MCP server

nuthatch

Turn an EVM contract's history into a local SQL database. One Rust binary, no Postgres, no

subgraph to write, and an MCP server built in.

· Website: www.nuthatch-indexer.com

curl -fsSL https://nuthatch-indexer.com/install.sh | sh                  # macOS Apple Silicon, Linux x86_64
nuthatch init 0xA0b86991c6218b36c1D19D4a2e9Eb0cE3606eB48 --alias usdc   # USDC; the chain is detected
nuthatch dev --backfill 300                                             # the last 300 blocks, then keeps up
nuthatch sql "SELECT count(*) FROM usdc__transfer"                      # in a second terminal

The Linux binary needs glibc 2.34 or newer to run (it is built on 2.35). No Intel Mac binary is published: there, and on other platforms, build from source with Rust 1.95.0 (docs/install.md). init creates a nest: a directory holding the contract's ABI, its config and, once dev runs, its indexed data. --backfill 300 starts 300 blocks behind the tip, about an hour of mainnet, so there are rows to query within seconds on the bundled public endpoints. Without it, dev backfills from the contract's deployment block: for USDC that is 20 million blocks, a long backfill on free public endpoints and a job for your own RPC (--rpc).

Like Ponder, nuthatch reads the chain over JSON-RPC, so it needs an endpoint, and a provider may charge for one. The public endpoints it bundles are for trying it out, not for keeping it running. It complements The Graph rather than replacing it: a subgraph serves an application from a network of indexers, while a nest puts a contract's history in a database on your own machine.

Why. Getting at a contract's history usually means writing a subgraph or handler code, running a database, or renting someone else's copy. nuthatch generates the tables from the ABI, runs as one process with nothing else to install, and keeps the data on your machine: at most 2 GB of RAM per chain, no telemetry, no account. The built-in MCP server lets Claude or any MCP client query it.

What you get

decoders, and scaffolds the project. You write nothing.

• No authoring. init 0xAddr resolves the ABI (Sourcify, then Etherscan), generates the schema and

the live tip and sealed history, one surface.

• No infra. A single static Rust binary. Embedded mode needs no Postgres, no Docker, no IPFS.
• It's just SQL. Your contract's events become per-event tables you query with real analytical SQL -

phone-home, no mandatory API token, ever.

• It's yours, and it's small. ≤2 GB RAM for single-chain tip-following, CI-enforced. No telemetry, no

Who runs it

Arbitrum One, serves live panels from self-hosted nests instead of The Graph gateway.

• Lodestar, an analytics dashboard for The Graph Protocol on

An earlier example, now finished: Arcaidia, a speed layer over Circle's CCTP built at ETHOnline 2026, read its indexed state from two nests on Ethereum Sepolia and Arc Testnet. Its solver discovered intents there, its settlement agent tracked CCTP there, and its web console rendered from them. The nests were serving within two hours of the builder asking The Graph for a higher Studio rate limit. They were stopped on 2026-09-29.

Shortened. The full README is on GitHub.