Nodit MCP Server
Official Nodit MCP server giving agents normalized multi-chain blockchain data across EVM and non-EVM networks.
- Sato Score57
- ChainsMultichain
Nodit MCP Server is an open-source MCP server by Nodit (Lambda256), with last code activity on 2026-06-23 (Quiet). Latest release on 2026-06-23. Sato Score 57/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install Nodit MCP Server →Last commit Jun 23, 2026 · Last release Jun 23, 2026 · ★ 24
Listed from developer.nodit.io on 2026-07-12. Install: reproduced by Sato Hub on 2026-07-21. Evidence →
Next step
Watch Nodit MCP Server
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on noditlabs/nodit-mcp-server before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
Nodit MCP Server connects AI agents to Nodit's blockchain infrastructure, exposing normalized, multi-chain data formatted for AI reasoning. It covers EVM chains (Ethereum, Base, Arbitrum, Optimism, Polygon, Avalanche, BNB Chain) plus non-EVM networks (Bitcoin, Solana, Aptos, Sui, TRON, XRPL, Dogecoin). Builders plug it in as a data layer so agents can query and reason over onchain state without running their own node infrastructure.
Sato Score
57/100· MediumHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 13/35
- Code transparency
- 18/20
- Interface verifiability
- 8/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 0/10
Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety).
Sato Check
v1.2.1 · as of 2026-09-27- Does it take your key?
- No key read found
- Does your key leave?
- Not yet run
- Can it move funds on its own?
- Unknown
A profile describes what we read and ran, with dates. It is not a safety rating, an audit or an endorsement, and "not found" is not "not there".
Evidence — listed vs checked · what the words mean
Listed from developer.nodit.io on 2026-07-12. Install: reproduced by Sato Hub on 2026-07-21.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | Multichain | self-reported | developer.nodit.io | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | developer.nodit.io | as of 2026-10-15 |
| Recent activity | last release 2026-06-23 · last commit 2026-06-23 | observed | github.com/noditlabs/nodit-mcp-server | 2026-10-15 |
| Install works | reproduced — install and entry both completedshows the install path works as written; not a statement about runtime behaviour | ✓ reproduced | github.com/noditlabs/nodit-mcp-server | 2026-07-21 |
| MCP endpoint answers | answered, but declined an anonymous probe | observed | mcp.nodit.io | 2026-10-15 |
| Daily check record | 0 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Takes your key | no private-key read found in what we read | traced | satohub.ai | 2026-09-27 |
| Key leaves the machine | not yet run with planted test keysthe sandbox lane has not run on this version | observed | satohub.ai | not dated |
| Moves funds on its own | unknown — could not read what it exposes | traced | satohub.ai | 2026-09-27 |
| Deploys as | npx (local stdio), Remote MCP (hosted SSE endpoint)confidence 0.85 | self-reported | github.com/noditlabs/nodit-mcp-server | as of 2026-07-14 |
| Works with | Claude Desktop, Claude Code, Cursor, Claude (Web)confidence 0.85 | self-reported | github.com/noditlabs/nodit-mcp-server | as of 2026-07-14 |
| Sato Score | 57/100 (Medium)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — reproduced in a container Jul 21, 2026
Runtime: node
npx @noditlabs/nodit-mcp-server@latest npx @noditlabs/nodit-mcp-server@latest (stdio, JSON-RPC)
You supply: NODIT_API_KEY (free at nodit.lambda256.io)
claude mcp add satohub-nodit-mcp -- npx @noditlabs/nodit-mcp-server@latest
A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.
Read from the project’s own docs as of 2026-07-21. What a deploy spec is →
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 2
- Failed
- 89
- Their error
- 26
- Unattributed
- 63
State changed on 2026-07-19 (responding → unclear), 2026-09-01 (unclear → failing), 2026-09-27 (failing → unreachable from our probe).
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Multichain
- Agent types
- MCP Server, Data Provider
- Open source
- Yes
- Deploys as
- npx (local stdio), Remote MCP (hosted SSE endpoint)
- Works with
- Claude Desktop, Claude Code, Cursor, Claude (Web)
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Nodit MCP Server fits
Related concepts: What Are MCPs? The Standard Way to Give Agents Tools, What Are Onchain Agents?
Listing History
Recorded changes to Nodit MCP Server's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Jul 23, 2026Sato Score tier: High → MediumScore 79 → 69.
- Jul 21, 2026Verified: deploy spec
- Jul 20, 2026Edited: mcp endpoint url
- Jul 19, 2026Edited: mcp endpoint url
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Auto-enriched: deployment options, supported integrations
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Privy
ActiveEmbedded and server wallet infrastructure used to give agents secure key management.
Phantom MCP
ActivePhantom's MCP server that lets AI agents view addresses, sign transactions, swap, and transfer tokens across Solana, Ethereum, Bitcoin, and Sui.
Clanker
ActiveAgent that deploys tokens on Base when tagged on Farcaster.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Nodit MCP Server
- Is Nodit MCP Server open source?
- Yes. Nodit MCP Server is open source under the Apache-2.0 license; the repository is https://github.com/noditlabs/nodit-mcp-server. Checked as of 2026-10-15.
- Which chains does Nodit MCP Server support?
- Nodit MCP Server lists support for Multichain as of 2026-10-15.
- Is Nodit MCP Server still maintained?
- The most recent code activity Sato Hub observed was on 2026-06-23 (last commit 2026-06-23, last release 2026-06-23), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Nodit MCP Server?
- node. Install: npx @noditlabs/nodit-mcp-server@latest. Entry: npx @noditlabs/nodit-mcp-server@latest (stdio, JSON-RPC). Sato Hub reproduced this install in a container on 2026-07-21. It runs as an MCP server (npx @noditlabs/nodit-mcp-server@latest).
- Is Nodit MCP Server verified on Sato Hub?
- Sato Hub holds one earned check for Nodit MCP Server: Deploy path reproduced — install verified in an isolated container (proves installability, not runtime safety). Its Sato Score is 57 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Nodit MCP Server — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/nodit-mcpData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.