Transactions cannot be sent, which removes the whole category of accident that makes people nervous about giving a model chain access. The pairing of live chain calls with documentation search and the OpenRPC method list is what makes it usable to someone who does not already know Nimiq's RPC: the model can look up what a call does and then make it. The remote option routes requests through the maintainer's Worker and supports SSE only; the local one talks to RPC directly.
An MCP server for the Nimiq blockchain, available two ways: a hosted endpoint that needs no installation, or `npx nimiq-mcp` locally with a direct RPC connection. Sending transactions is deliberately not supported.
- Chain data: the current head block, a block by number or by hash, and the current epoch — `getHead`, `getBlockByNumber`, `getBlockByHash`, `getEpochNumber`
- Accounts and transactions: account detail and balance by address, a transaction by hash, and transaction history for an address — `getAccount`, `getBalance`, `getTransaction`, `getTransactionsByAddress`
- Validator and network state: all active validators, one validator in detail, slot assignments, and network status including peer count and consensus state — `getValidators`, `getValidator`, `getSlots`, `getNetworkInfo`
- Supply and staking maths: circulating supply, supply at a given time, a staking rewards calculation, an interactive calculator that asks for the missing inputs, and the NIM price against other currencies — `getSupply`, `calculateSupplyAt`, `calculateStakingRewards`, `interactiveStakingCalculator`, `getPrice`
- Documentation access: every RPC method from the latest OpenRPC document, and full-text search over the Nimiq docs — `getRpcMethods`, `searchDocs`
- Three documentation resources served as plain text for the model to read — `nimiq://docs/web-client`, `nimiq://docs/protocol`, `nimiq://docs/validators`
Nothing for the remote path: add the URL https://nimiq-mcp.je-cf9.workers.dev/sse with SSE transport. Locally, Node.js and `npx nimiq-mcp`; the default RPC endpoint is https://rpc.nimiqwatch.com and `--rpc-url`, `--rpc-username` and `--rpc-password` point it elsewhere. The same arguments work as URL parameters on the remote endpoint. The package is `nimiq-mcp` (0.0.10 in package.json).
One command — npx nimiq-mcp
