# nuthatch (oci · ghcr.io/nuthatch-org/nuthatch)

Query an EVM contract's indexed history with SQL, via a local nuthatch nest and nuthatch dev.

- Trust score: 49/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- oci · `ghcr.io/nuthatch-org/nuthatch`: 49/100 (this document), [markdown](https://verifymcp.io/servers/nuthatch-org-nuthatch/ghcr-io-nuthatch-org-nuthatch.md), [page](https://verifymcp.io/servers/nuthatch-org-nuthatch/ghcr-io-nuthatch-org-nuthatch)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/nuthatch-org/nuthatch`
- Version: `5.22.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 87/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to nuthatch-org/nuthatch).
  - License check failed: no license is declared.
  - Actively maintained (last published 3 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 79/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1211 tokens (~75/item across 16 items; 13 tools + 3 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 62% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the nuthatch MCP server?

nuthatch runs locally as a container image, launched with docker run --rm -i ghcr.io/nuthatch-org/nuthatch:5.22.0 mcp --url http://host.docker.internal:8288. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add nuthatch-org-nuthatch -- docker run --rm -i ghcr.io/nuthatch-org/nuthatch:5.22.0 mcp --url http://host.docker.internal:8288
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

### Cursor

```json
{
  "mcpServers": {
    "nuthatch-org-nuthatch": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/nuthatch-org/nuthatch:5.22.0",
        "mcp",
        "--url",
        "http://host.docker.internal:8288"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

### VS Code

```json
{
  "servers": {
    "nuthatch-org-nuthatch": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/nuthatch-org/nuthatch:5.22.0",
        "mcp",
        "--url",
        "http://host.docker.internal:8288"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

### Codex

```bash
codex mcp add nuthatch-org-nuthatch -- docker run --rm -i ghcr.io/nuthatch-org/nuthatch:5.22.0 mcp --url http://host.docker.internal:8288
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nuthatch-org-nuthatch": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/nuthatch-org/nuthatch:5.22.0",
        "mcp",
        "--url",
        "http://host.docker.internal:8288"
      ],
      "enabled": true
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

### Hermes

```yaml
mcp_servers:
  nuthatch-org-nuthatch:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/nuthatch-org/nuthatch:5.22.0", "mcp", "--url", "http://host.docker.internal:8288"]
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

### Netclaw

```json
{
  "McpServers": {
    "nuthatch-org-nuthatch": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/nuthatch-org/nuthatch:5.22.0",
        "mcp",
        "--url",
        "http://host.docker.internal:8288"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

### Other

```json
{
  "mcpServers": {
    "nuthatch-org-nuthatch": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/nuthatch-org/nuthatch:5.22.0",
        "mcp",
        "--url",
        "http://host.docker.internal:8288"
      ]
    }
  }
}
```

The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 47)

First indexed and scored.

## MCP tools (13)

### `status` (~43 tokens)

Index status: contract, chain, decoded rows across all tables (`entities`, not transfers alone), holders, last & sealed block, and the first indexed block (`start_block`).

### `schema` (~34 tokens)

The data model - how tables/views are named and queried. Read this first, then `tables` for the exact tables and columns.

### `tables` (~31 tokens)

List every decoded table (`{alias}__{event}`) with its columns, Solidity types, and topic0.

### `table` (~36 tokens)

Recent rows of one table, merged across the hot tip and sealed segments.

Input parameters:

- `limit` (integer)
- `name` (string, required)

### `sql` (~216 tokens)

Run a read-only SQL query over the live tip ∪ sealed history. Each event is a view named `{alias}__{event}` (e.g. "usdc__transfer") with block_number, log_index, tx_hash, address + the event's params. Call `schema` first. SELECT/WITH only. Returns a compact table (data rows are the lines beginning `|`; chain data cannot start a line) + a provenance stamp; capped at `limit` rows (default 200), and the node caps `limit` itself (50,000 unless its operator changed it).

Input parameters:

- `at_block` (integer): Answer over the facts as they stood at this block. Authored entities are not available then.
- `at_time` (integer): Answer as of this time, unix seconds UTC, placed as `at` places it.
- `limit` (integer): Max rows to return (default 200; the node may cap it lower than you ask).
- `query` (string, required): A SELECT or WITH query.

### `at` (~105 tokens)

Where the nest stood at a time (unix seconds UTC): `block`, the newest block at or before it the nest holds a timestamp for, and `next_block`, the oldest after it. The nest's state at the time is its state at `block`. `exact` is true when the two are adjacent, `final` when `next_block` is sealed. Refused for a time the nest has not indexed past.

Input parameters:

- `time` (integer, required): Unix seconds, UTC.

### `explain` (~64 tokens)

Validate a SQL query WITHOUT executing it - binds tables/columns/types and returns {valid:true} or an error with a fix hint. Cheaper than `sql`; use it to check a query before running it.

Input parameters:

- `query` (string, required): A SELECT or WITH query to validate.

### `entity` (~46 tokens)

Look up one decoded row, of any table, by its id, formatted `{block:012}-{logindex:06}`; the answer names the table.

Input parameters:

- `id` (string, required)

### `diff` (~228 tokens)

What happened in a block range, a block or one transaction, as a JSON document of fixed sentences with exact amounts: every control-plane event (ownership, pause, upgrade, roles), the largest movements and net flows per token, new holders, approvals with unlimited ones named, labels, and every other table counted or told. `flow: true` gives the token flow instead. Give `from` and `to`, or `block`, or `tx` with its `block`. Nothing in it is inferred; `not_seen` says what the nest cannot see.

Input parameters:

- `block` (integer): One block, or the block holding `tx`.
- `final_only` (boolean): Refuse a range above the sealed boundary.
- `flow` (boolean): The token flow instead of the story.
- `from` (integer): First block of an inclusive range.
- `to` (integer): Last block of an inclusive range.
- `top` (integer): Items per list (story default 10, at most 1000).
- `tx` (string): One transaction hash; needs `block`.

### `balance` (~143 tokens)

Derived token balance for an address (IVM view; i128 base units, returned as a decimal string). The result carries `complete_history`. When true the nest was indexed from its configured `start_block` with no `--backfill` (the contract's deployment if `start_block` is the deployment block, which `init` sets) and the figure is under `balance`. When false or null it is only the net of transfers since `indexed_from` and is returned as `net_flow_since_indexed_from` with a note: a negative figure is then not an error, and it must not be reported as a balance.

Input parameters:

- `address` (string, required)

### `top_balances` (~93 tokens)

Top holder balances, descending (IVM view; i128 base units as decimal strings). The result carries `complete_history`. When true these are holders (`holders`, `balance`). When false or null they are only net flows since `indexed_from` (`net_receivers`, `net_flow_since_indexed_from`, with a note) and must not be reported as holders or balances.

Input parameters:

- `limit` (integer)

### `flags` (~70 tokens)

Compliance flags (RFC-0008 C3): `kind=threshold` (single transfers over the configured amount) or `kind=velocity` (addresses over the windowed-volume threshold). Amounts are i128 base units as decimal strings.

Input parameters:

- `kind` (string)
- `limit` (integer)

### `exposure` (~44 tokens)

Direct counterparty-exposure of an address to the labeled set (RFC-0008 C1): inbound/outbound count + summed amount per label.

Input parameters:

- `address` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/nuthatch-org-nuthatch/ghcr-io-nuthatch-org-nuthatch#diagnostics

## Score history

- 2026-11-21: 49
- 2026-11-20: 48
- 2026-11-19: 48
- 2026-11-18: 47
- 2026-11-17: 47

## Common questions

### What is the nuthatch MCP server?

nuthatch is an MCP server listed in the public MCP registry as io.github.nuthatch-org/nuthatch. Query an EVM contract's indexed history with SQL, via a local nuthatch nest and nuthatch dev. This page covers its container image (ghcr.io/nuthatch-org/nuthatch).

### Is the nuthatch MCP server safe to use?

nuthatch scores 49 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the nuthatch MCP server expose?

nuthatch exposes 13 tools: status, schema, tables, table, sql, and 8 more. Their descriptions and schemas cost roughly 1,153 tokens of context every time the server is loaded.

### Is the nuthatch MCP server still maintained?

nuthatch is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the nuthatch MCP server?

VerifyMCP ran 12 checks on nuthatch, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about nuthatch: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/nuthatch-org/nuthatch
- Repository: https://github.com/nuthatch-org/nuthatch
- Website: https://www.nuthatch-indexer.com/
- Changelog RSS feed: https://verifymcp.io/servers/nuthatch-org-nuthatch/ghcr-io-nuthatch-org-nuthatch.xml
- Changelog JSON feed: https://verifymcp.io/servers/nuthatch-org-nuthatch/ghcr-io-nuthatch-org-nuthatch/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/nuthatch-org-nuthatch/ghcr-io-nuthatch-org-nuthatch.json
- HTML version of this page: https://verifymcp.io/servers/nuthatch-org-nuthatch/ghcr-io-nuthatch-org-nuthatch
