Skip to content

MCP servers › io.github.nuthatch-org › nuthatch

MCP server · registry snapshot 2026-11-18 · last checked 2026-11-18

nuthatch MCP server

Registry name io.github.nuthatch-org/nuthatch

by nuthatch-org · GitHub account (the registry's namespace rule)repository: same ownerSource ↗Website ↗

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

5 of 5 record checks metversion 5.22.0Ruststandard input/output

Summary

io.github.nuthatch-org/nuthatch is a local MCP server listed in the official MCP registry at version 5.22.0, under the namespace of the GitHub account nuthatch-org. Its linked repository, github.com/nuthatch-org/nuthatch, belongs to the same GitHub account.

Record checks

5 of 5 record checks met · 4 do not apply

  • met: Registry entry is active and says how to run it
  • met: Source repository link opens
  • met: Repository is not archived
  • met: Code pushed to the repository in the 90 days before our check
  • met: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 7 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it

Key facts

Runs
local package
Transport
standard input/output
Your own values
none declared (not a guarantee)
Package
Docker (OCI)
Repository
public
Last tested
not tested

Tool list

Not read: Its package type is not run in our sandbox yet. This is our limit, not the server's. So there is no tool-list size and no result from the three APIs.

Add to your client

How fresh this is

Live-tested
no
Last tested
not tested
Latest version
5.22.0, published 2026-11-17 (registry, as of the 2026-11-18 snapshot)
First listed version
2026-11-17 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-11-17; 2 in the 90 days before the 2026-11-18 snapshot.
Most recent 2 versions
  • 5.22.0 · 2026-11-17
  • 5.21.0 · 2026-11-17
(versions still listed in the registry only)
Registry data
snapshot 2026-11-18
Package and repository
checked 2026-11-18

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry; repository link does not open; repository archived; no push in over 365 days. Does not apply: listed version cannot be installed or is withdrawn. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

Version 5.21.0 (published 2026-11-17) → 5.22.0 (published 2026-11-17), between the registry lists of 2026-11-17 and 2026-11-18.

The publisher’s GitHub release note for v5.22.0, published 2026-11-17.

Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
Nuthatch 5.22.0 is for a firm that has to show its own onchain figures to someone else: an answer
as of a block or a time, recipes for an issuer's own token, and an evidence bundle that another
machine re-executes to the same rows. There is no storage migration. No sealed segment and no
registry hash moves. A nest that holds a label set gets a new NID and data identity once, because
label sets are no longer part of what a nest is, and one factory configuration that silently lost
events is now refused at load.

## Upgrade guidance

Replace the binary and restart. A 5.21 store is used as it is.

- **A nest with a label set imported**: its NID and data identity move once, since `labels/` and
  `labels.manifest.json` no longer count toward either (#2946). A single-nest directory starts as
  before. A runtime whose mount record was written with labels present logs `identity drift` for it
  and keeps serving the `data/<nid>` the record names. A nest that publishes writes a full copy under
  the new data identity on its next `publish sync`; the old prefix can be deleted once it lands.
  The operators guide's
  [data lifecycle](https://github.com/nuthatch-org/nuthatch/blob/main/docs/operators.md#data-lifecycle)
  section has the detail.
- **A nest whose `[[factories]]` give one announcing event's `child_param` two templates**: it is
  refused at load, naming both (#2958). It loaded before, but a child takes one template, so the
  second template's tables stayed empty. Declare one template whose ABI holds both contracts' events.
- **A `/sql` client that rejects unknown provenance keys**: an answer may now carry `labels_sha256`
  when it read `labels`, and `segments_sha256` when it was asked at a block.
- Every other nest: nothing to do.

## As of a block or a time

- **`/at?time=T`** places a unix time against the nest's own stamped blocks: the last block at or
  before it, the next one after, and whether that is final, which it is once the next block is
  sealed (#2941). On EURC, 1,000 random times
  from deployment to the tip were all placed with no indexed event between `block` and
  `next_block`, so the nest's state at the time is its state at `block`.
- **`/sql` takes `at_block` or `at_time`** and answers from the rows at or below that block, sealed
  and hot (#2942). Label sets bind as imported now (#2962).

## For an issuer's own token

- **`nuthatch recipe add frozen`, `outstanding` and `mint_burn_daily`** for a FiatToken-style
  contract (#2943). `outstanding` is total supply less frozen balances and the balances of addresses
  labelled `treasury`. Asked at 2022-12-31 23:59 PT on EURC, it gives 24,905,662.05 against the
  24,905,662 of Circle's December 2022 report.
- **`nuthatch recipe add fiat_threshold`** lists transfers above a fiat amount at their UTC day's
  rate, from an offchain table, to recipients in none of the given label sets (#2945). A day with no
  rate lists its transfers as unpriced rather than leaving them out.
- **`examples/mica-art22`** computes the four MiCA Art 22(1) figures over EURC, each deduction of the
  EBA's RTS as its own view (#2947). It is a worked example, not regulatory advice.

## Evidence bundles

- **`nuthatch evidence make "<SELECT>" --at-block N | --at-time T`** asks a running nest for one
  answer as of a sealed block and writes a bundle: the chain, NID, registry hash, statement, rows, a
  hash of the rows in canonical order, the label set's hash when the rows read `labels`, and a hash of
  the final segments they were read from (#2944, #2961). `--key` signs it with a pack key. It refuses
  an unsealed block, and one whose segments include a provisional tail.
- **`nuthatch evidence verify b.json --url <nest>`** asks a nest of the same NID the same statement
  at the same block and says `match`, or names the field that differs. `--dir` re-hashes the
  verifier's own segment files first, which `serve` does not, and names any that changed.
- **Label sets are not part of a nest** (#2946). Th

The release on GitHub

Source: the official MCP Registry list on 2026-11-17 and on 2026-11-18; release notes from the GitHub Releases API, checked 2026-11-18.

What it is

How do I add it to my client?

Config from the registry entry
  • No config: the Docker image declares runtime arguments (options for the runner itself), and the registry documentation gives no rule for where they go.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

What do the published files and outside lists say?

Read as text · nothing run · no tool called

Package files

  • MCP SDK in the package files. Not read yet: added with the next daily run.
  • Build workflow. Not read yet: added with the next daily run.

Image

  • Image platforms. The image is published for linux/amd64 only. Source: read 2026-11-18.
  • Image user. The image config sets user nuthatch. Read from the image config; the image was not pulled or run. Source: oci:ghcr.io/nuthatch-org/nuthatch:5.22.0 · read 2026-11-18.
  • Image tag history. First reading of the tag ghcr.io/nuthatch-org/nuthatch:5.22.0 on 2026-11-18 (sha256:947012b86102…); later readings are compared with it. Source: oci:ghcr.io/nuthatch-org/nuthatch:5.22.0 · read 2026-11-18.

Outside lists

  • CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-18. This product uses the NVD API but is not endorsed or certified by the NVD.
  • GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-18. GitHub Advisory Database, CC BY 4.0
  • Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-18. Source: read 2026-11-18.
  • Cline marketplace. Not in the Cline marketplace on 2026-11-18. Source: read 2026-11-18.

Own host

Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Repository github.com/nuthatch-org/nuthatchOpens publiclymatchesapi.github.com · 2026-11-18

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace
io.github.nuthatch-org
GitHub owner
an organization (nuthatch-org)
Repository
github.com/nuthatch-org/nuthatch
Stars
7
Repository age
91–180 days
Last push
0–30 days ago
Archived
no
Security policy
SECURITY.md

Source: the registry entry and api.github.com · 2026-11-18; security policy read from GitHub · 2026-11-17.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

5 of 5 record checks met · 4 do not apply

  • Not ranked by downloads: not an npm or PyPI package
  • Not ranked by stars: 7 stars (ranked from 10)
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • MetSource repository link opensThe linked GitHub repository is public.
  • MetRepository is not archivedNot archived.
  • MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
  • MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
  • Does not applyPackage names its licence with a standard (SPDX) identifierNot an npm or PyPI package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnNot an npm or PyPI package.
  • Does not applynpm package carries build provenance (attestation)PyPI packages have no npm-style attestation.
  • Does not applyNo known critical or high advisory in the package or its dependenciesNot an npm or PyPI package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-18 (security policy 2026-11-17). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about io.github.nuthatch-org/nuthatch

Answered from the data above

Who publishes io.github.nuthatch-org/nuthatch?

The registry ties the namespace io.github.nuthatch-org to the GitHub account nuthatch-org; only its owner can publish under it. Its linked repository, github.com/nuthatch-org/nuthatch, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.

Is io.github.nuthatch-org/nuthatch safe to install?

We do not rate servers as safe or unsafe. 5 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Has io.github.nuthatch-org/nuthatch been security tested?

No. Its package type is not run in our sandbox yet. This is our limit, not the server's.

Does io.github.nuthatch-org/nuthatch publish a security policy?

Yes: its repository has a public security policy (github.com/nuthatch-org/nuthatch/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.

Where is the source code of io.github.nuthatch-org/nuthatch?

In github.com/nuthatch-org/nuthatch, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

Has it been tested?

Feature #1

Its package type is not run in our sandbox yet. This is our limit, not the server's. — our limit

Package type: oci.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added at the next monthly refresh
listed 2026-11-18; not classified yet
Pricing modelAI-classified
pending: added at the next monthly refresh
the website is not read yet
Programming language
api.github.com · 2026-11-18
Hosting type
registry · 2026-11-18
MCP capability
not checked
not read (no session)
Transport
standard input/output
registry · 2026-11-18
Required credentials
none declared
registry · 2026-11-18 · no declaration is not a guarantee
Package registry
registry · 2026-11-18
Freshness
0–30 days
registry updatedAt · 2026-11-18
Lifecycle status
registry · 2026-11-18
License class
does not apply
package ecosystem not queried by this layer (oci); only npm and PyPI are supported here
Integrity hash
does not apply
package ecosystem not queried by this layer (oci); only npm and PyPI are supported here
Signature / provenance
does not apply
package ecosystem not queried by this layer (oci); only npm and PyPI are supported here
Dependency advisories
not checked
only npm and PyPI packages are audited
Popularity
does not apply
package ecosystem not queried by this layer (oci); only npm and PyPI are supported here
Publisher signals
owner: an organization · repository age: 91–180 days · stars: 0–9
api.github.com · 2026-11-18
Maintenance
api.github.com · 2026-11-18
Environment
your machine
where it runs, from the hosting type · 2026-11-18

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.github.nuthatch-org/nuthatch: MCP server record.” Data checked 2026-11-18. https://protocolprobe.com/mcp/servers/io.github.nuthatch-org/nuthatch

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 5 of 5 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.github.nuthatch-org/nuthatch)](https://protocolprobe.com/mcp/servers/io.github.nuthatch-org/nuthatch)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).

Write to hello@protocolprobe.com · corrections log · methodology