io.github.MinaProtocol/mina-mcp-server
NPM · @O1-LABS/MINA-MCP-SERVER · SCANNED SEP 21
Query Mina Protocol: accounts, blocks, transactions, zkApp events/actions, archive SQL, Rosetta.
Available components
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 44 of 143 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to MinaProtocol/mina-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 112 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1780 tokens (~89/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.MinaProtocol/mina-mcp-server server?
io.github.MinaProtocol/mina-mcp-server runs locally as an npm package, launched with npx -y @o1-labs/mina-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @o1-labs/mina-mcp-server
claude mcp add minaprotocol-mina-mcp-server -- npx -y @o1-labs/mina-mcp-server
{
"mcpServers": {
"minaprotocol-mina-mcp-server": {
"command": "npx",
"args": [
"-y",
"@o1-labs/mina-mcp-server"
]
}
}
} {
"servers": {
"minaprotocol-mina-mcp-server": {
"command": "npx",
"args": [
"-y",
"@o1-labs/mina-mcp-server"
]
}
}
} codex mcp add minaprotocol-mina-mcp-server -- npx -y @o1-labs/mina-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"minaprotocol-mina-mcp-server": {
"type": "local",
"command": [
"npx",
"-y",
"@o1-labs/mina-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add minaprotocol-mina-mcp-server --command npx --arg -y --arg @o1-labs/mina-mcp-server
mcp_servers:
minaprotocol-mina-mcp-server:
command: "npx"
args: ["-y", "@o1-labs/mina-mcp-server"] {
"McpServers": {
"minaprotocol-mina-mcp-server": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@o1-labs/mina-mcp-server"
]
}
}
} assistant mcp add minaprotocol-mina-mcp-server -t stdio -c npx -a -y @o1-labs/mina-mcp-server
{
"mcpServers": {
"minaprotocol-mina-mcp-server": {
"command": "npx",
"args": [
"-y",
"@o1-labs/mina-mcp-server"
]
}
}
} 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 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −1
- CVE-2026-82562 no longer affects this package ▲ security
- CVE-2026-82417 no longer affects this package ▲ security
- Known CVEs: fail → pass ▲ security
- Stability: pass → 0.77 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −2
- Stability: pass → 0.80 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
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 Sept 2026 · Analysed npm/@o1-labs/mina-mcp-server@0.7.3
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | MinaProtocol/mina-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/MinaProtocol/mina-mcp-server/.github/workflows/release.yml@refs/tags/v0.7.3 |
| Rekor log index | 1685497165 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:29acf26c646f16d001366c913faa6b84f34d53291dead0e155da1a9ade8ae4334de5c94b9eaba819af58dad962cc484afb326a023e051a214c877480f |
Background: How many MCP packages publish verified provenance →
Dependencies 143 packages
| Packages resolved | 143 |
|---|---|
| Stale | 44 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
describe_state ~40
[infra] Snapshot of the live public network: sync, latest block, mempool size, plus suggested next-tool hints. Call this first to orient yourself.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_account ~54
Get account information by public key from the live daemon (tutorial + live modes).
| Name | Type | Req | Description |
|---|---|---|---|
| publicKey | string | yes | Mina public key (B62...) |
| token | string | – | Token ID (optional, defaults to MINA) |
No output schema declared.
No examples provided.
get_actions ~147
[tutorial+live] Get dispatched actions from a zkApp address via the Archive-Node-API. Actions are reducer inputs that modify zkApp state. Snapshot mode does not run an Archive-Node-API and rejects this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | zkApp public key (B62...) |
| endActionState | string | – | Filter to this action state hash (inclusive) |
| from | number | – | Start block height (inclusive) |
| fromActionState | string | – | Filter from this action state hash (inclusive) |
| status | string | – | Block status filter |
| to | number | – | End block height (exclusive) |
| tokenId | string | – | Token ID |
No output schema declared.
No examples provided.
get_archive_blocks ~119
[tutorial+live] Get finalized blocks from the Archive-Node-API (height, creator, timestamp, coinbase). Prefer this for live mode (the archive node holds canonical history) over `get_best_chain` (daemon's in-memory view including not-yet-canonical tip). Returns full block rows — use a small `limit` on busy chains.
| Name | Type | Req | Description |
|---|---|---|---|
| canonical | boolean | – | Only return canonical (finalized) blocks |
| limit | number | – | Number of blocks to return |
| sortBy | string | – | Sort order |
No output schema declared.
No examples provided.
get_best_chain ~130
Get the current best chain from the live daemon. Returns per-block headers + transaction counts (always within budget) — use get_block for a specific block's transactions. detail:"full" returns complete blocks and may overflow on busy networks.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Output size. "lite" (default): block header + transaction counts only — always within budget. "transactions": header + a page of userCommands (see transactionLimit/Offset). "full": the complete daemo… |
| maxLength | number | – | Maximum number of blocks to return |
No output schema declared.
No examples provided.
get_block ~199
Get a block by state hash or height. Defaults to a "lite" summary (header + transaction counts) that stays within the tool budget; use detail to pull paged transactions or the full block. In tutorial mode, queries the live daemon first and falls back to the archive DB. In live mode, a stateHash is required (use get_archive_blocks to discover one).
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | Output size. "lite" (default): block header + transaction counts only — always within budget. "transactions": header + a page of userCommands (see transactionLimit/Offset). "full": the complete daemo… |
| height | number | – | Block height |
| stateHash | string | – | Block state hash |
| transactionLimit | number | – | Max userCommands to return when detail="transactions". |
| transactionOffset | number | – | Offset into the userCommands list when detail="transactions". |
No output schema declared.
No examples provided.
get_events ~121
[tutorial+live] Get emitted events from a zkApp address via the Archive-Node-API. Events are state-change notifications emitted by zkApp account updates. Snapshot mode does not run an Archive-Node-API and rejects this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | zkApp public key (B62...) |
| from | number | – | Start block height (inclusive) |
| status | string | – | Block status filter |
| to | number | – | End block height (exclusive) |
| tokenId | string | – | Token ID (defaults to MINA token) |
No output schema declared.
No examples provided.
get_example ~55
[infra] Get the full step list for a single named example workflow. Use list_examples first to discover names.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Example name from list_examples (e.g. 'send_payment', 'verify_in_archive'). |
No output schema declared.
No examples provided.
get_genesis_constants ~59
Get the network's genesis constants: coinbase reward, account-creation fee, slot/epoch timing, k (confirmations), and ledger depth. Use these to reason about fees, finality, and timing rather than hard-coding values.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_mempool ~109
List transactions currently pending in the daemon's mempool (not yet in a block), optionally filtered by `publicKey`. Each entry has top-level `from`/`to` (B62q… pubkeys) plus `amount`/`fee`/`nonce`/`hash`/`kind`/`memo`/`failureReason`. Empty once everything has been included — does not show mined txs.
| Name | Type | Req | Description |
|---|---|---|---|
| publicKey | string | – | Filter by public key |
No output schema declared.
No examples provided.
get_network_id ~50
Get the daemon's network identifier (e.g. 'mina:mainnet', 'mina:devnet'). Use this to confirm which network the server is actually talking to before interpreting balances or submitting transactions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_network_state ~55
[tutorial+live] Get network state from the Archive-Node-API: max canonical and pending block heights. (Different from `get_sync_status` which queries the daemon, and from `describe_state` which aggregates both.)
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_sync_status ~90
[infra] Get the sync status and daemon info. Returns the flat daemon status object directly — fields like `syncStatus`, `blockchainLength`, `stateHash`, `numAccounts`, `chainId`, `addrsAndPorts` are at the top level (not nested under `daemonStatus`). In snapshot mode returns archive DB stats instead. In tutorial and live modes returns the live daemon status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_transaction_status ~102
Check the daemon's status for a submitted transaction (PENDING / INCLUDED / UNKNOWN). Pass the id returned by send_payment as `payment` (or a zkApp tx id as `zkappTransaction`) — exactly one. Use this to poll after a send; for an already-mined tx, prefer get_transaction / search_transactions against the archive.
| Name | Type | Req | Description |
|---|---|---|---|
| payment | string | – | Payment transaction ID |
| zkappTransaction | string | – | zkApp transaction ID |
No output schema declared.
No examples provided.
list_examples ~71
[infra] List curated example workflows (each is a sequence of tool calls). Filter by the current server mode by default; pass `all` to see every workflow regardless of mode.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | 'current' filters to workflows runnable in this server's mode; 'all' shows every workflow. |
No output schema declared.
No examples provided.
rosetta_account ~98
Mina-Rosetta /account/balance — balance(s) for a B62q… account, optionally at a specific block.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Mina public key (B62q…) |
| blockHash | string | – | Block state hash (optional). Pass at most one of blockIndex or blockHash. |
| blockIndex | number | – | Block height (optional). Pass at most one of blockIndex or blockHash. |
No output schema declared.
No examples provided.
rosetta_block ~162
Mina-Rosetta /block — a block (with operations) by index or state hash. Provide exactly one. Defaults to a "lite" summary (block identifiers + transaction/operation counts); Rosetta expands each Mina tx into several operations, so the full shape is large on busy networks — use detail:"transactions" with paging, or detail:"full" deliberately.
| Name | Type | Req | Description |
|---|---|---|---|
| detail | string | – | "lite" (default): counts only. "transactions": paged transactions. "full": entire response. |
| hash | string | – | Block state hash |
| index | number | – | Block height |
| transactionLimit | number | – | Max transactions when detail="transactions". |
| transactionOffset | number | – | Offset into the transactions list when detail="transactions". |
No output schema declared.
No examples provided.
rosetta_mempool ~28
Mina-Rosetta /mempool — pending transaction identifiers on this network.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
rosetta_mempool_transaction ~52
Mina-Rosetta /mempool/transaction — a single pending transaction with operations, by hash.
| Name | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | Transaction hash (returned by rosetta_mempool) |
No output schema declared.
No examples provided.
rosetta_status ~39
Mina-Rosetta /network/status — current/genesis/oldest block identifiers and sync state for this network, in standardized Rosetta format.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.MinaProtocol/mina-mcp-server server?
io.github.MinaProtocol/mina-mcp-server is listed in the public MCP registry as io.github.MinaProtocol/mina-mcp-server. Query Mina Protocol: accounts, blocks, transactions, zkApp events/actions, archive SQL, Rosetta. This page covers its npm package (@o1-labs/mina-mcp-server).
Is the io.github.MinaProtocol/mina-mcp-server server safe to use?
io.github.MinaProtocol/mina-mcp-server scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. 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 io.github.MinaProtocol/mina-mcp-server server expose?
io.github.MinaProtocol/mina-mcp-server exposes 20 tools: get_account, get_block, get_best_chain, get_transaction_status, get_mempool, and 15 more. Their descriptions and schemas cost roughly 1,780 tokens of context every time the server is loaded.
Is the io.github.MinaProtocol/mina-mcp-server server still maintained?
io.github.MinaProtocol/mina-mcp-server is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.MinaProtocol/mina-mcp-server server under?
io.github.MinaProtocol/mina-mcp-server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.