get-network-state
Get the current state of the Mina network
LABSCO SUMMARY
Keeping actions and events as separate tools matches how Mina zkApps actually work, and merging them would have destroyed the distinction.
On Mina an action is an input a zkApp reduces over and an event is an output it emits, and a developer debugging a zkApp is almost always asking about one specifically. A generic 'query the chain' tool would force the caller to filter for the distinction that mattered most. Narrow surface aimed at people building on one chain, and it does not pretend otherwise — three tools, read-only, no wallet involved.
What it is
A three-tool client over a Mina Archive Node: filtered queries for actions and for events, plus the current network state.
What you get
- query-actions and query-events are separate because on Mina they are separate things — actions are the sequenced inputs a zkApp consumes, events are what it emits.
- Both accept filters, so a query narrows to a contract or a range rather than returning everything the archive holds.
- get-network-state returns the chain's current position, which is what makes an archive result interpretable.
Requirements
Nothing to supply — it reads a public archive node.
Setup effort
One command — npx mcp-mina-archive-node
USE CASES
01
Debugging what a zkApp consumed
Query the actions with filters narrowing to the contract and range in question, rather than reading the whole archive.
02
Checking what a contract emitted
Query events separately from actions, since on Mina those are different things and the answer is usually about one of them.
3 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
query-actions
Query actions from the Mina blockchain with optional filters
query-events
Query events from the Mina blockchain with optional filters
BEFORE YOU INSTALL
What to know first
Tools you get
3 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 3 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-mina-archive-node": {
"command": "npx",
"args": [
"mcp-mina-archive-node"
]
}
}
}npx
TERMINAL
npx mcp-mina-archive-node
