nuthatch
OCI · GHCR.IO/NUTHATCH-ORG/NUTHATCH
Query an EVM contract's indexed history with SQL, via a local nuthatch nest and nuthatch dev.
Available components
Last scanned (13 hours ago)
Scores higher than 63% of OCI servers
Category Crypto and Web3
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. How we score → Why this is hard to score →
Supply Chain Security0
- 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.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to nuthatch-org/nuthatch). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1211 tokens (~75/item across 16 items; 13 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 62% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
Checks we ran (12)
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (4)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain Security (scores 0 for this)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 in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
- Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +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.
- 19 Nov 26 +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.
- 17 Nov 26 47
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed oci/ghcr.io/nuthatch-org/nuthatch@5.22.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | oci |
| Reason | Verified |
| Discovered via | GitHub artifact attestations |
| Source repo | nuthatch-org/nuthatch |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/nuthatch-org/nuthatch/.github/workflows/release.yml@refs/tags/v5.22.0 |
| Rekor log index | 3949001924 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha256:947012b8610265d90343e22eaf304d28baaa397197f9f0ef065a4e2a33801f50 |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
at ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| time | integer | yes | Unix seconds, UTC. |
No output schema declared.
No examples provided.
balance ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
diff ~228
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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`. |
No output schema declared.
No examples provided.
entity ~46
Look up one decoded row, of any table, by its id, formatted `{block:012}-{logindex:06}`; the answer names the table.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
explain ~64
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | A SELECT or WITH query to validate. |
No output schema declared.
No examples provided.
exposure ~44
Direct counterparty-exposure of an address to the labeled set (RFC-0008 C1): inbound/outbound count + summed amount per label.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | – |
No output schema declared.
No examples provided.
flags ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
schema ~34
The data model - how tables/views are named and queried. Read this first, then `tables` for the exact tables and columns.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
sql ~216
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | A SELECT or WITH query. |
No output schema declared.
No examples provided.
status ~43
Index status: contract, chain, decoded rows across all tables (`entities`, not transfers alone), holders, last & sealed block, and the first indexed block (`start_block`).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
table ~36
Recent rows of one table, merged across the hot tip and sealed segments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| name | string | yes | – |
No output schema declared.
No examples provided.
tables ~31
List every decoded table (`{alias}__{event}`) with its columns, Solidity types, and topic0.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
top_balances ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
No output schema declared.
No examples provided.
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.
oci · ghcr.io/nuthatch-org/nuthatch
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.
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.