nuthatch-org/nuthatch
Index an EVM contract's events into a local SQL database with nuthatch, and query it over MCP. The MCP server needs the nuthatch binary on PATH and a running nuthatch dev.
Index an EVM smart contract's events or onchain history into a local SQL database. Use when asked to index a contract's events or logs, page through eth_getLogs or work round its block range limits ("query returned more than 10000 results", "block range too large"), build a dashboard, API or backend over onchain history (token transfers, swaps, holders, balances), backfill a contract's past events, or replace a subgraph for local development. Works on Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain and other EVM chains.
Build, configure, run, or debug a nuthatch indexer (a "nest", one or many in a runtime). Use when the user wants to index a smart contract's events into a local SQL database with nuthatch - scaffolding from an address, editing nuthatch.toml/semantic.toml, adding contracts, factories, compliance labels and flags, packaging/mounting nests, running several nests in one runtime, or troubleshooting a running indexer.
Port a Graph Protocol subgraph to a nuthatch nest. Use when the user has a subgraph (schema.graphql, mappings, subgraph.yaml, or a deployment CID) and wants a nest, a port report, or to know which entity fields will not match. Classify every field and emit the report BEFORE scaffolding. Then overlay [[calls]], Exact views, checks and a README onto nuthatch init --from-subgraph. Do not run AssemblyScript. Do not invent contract reads the mapping did not make.