Get Nimiq alerts on Telegram. Try @nimiq_notifier_bot for notifications you can follow on the go.

Open in Telegram

Default

Nimiq MCP server

A Model Context Protocol (MCP) server that exposes the Nimiq JSON-RPC API as tools for AI assistants (Cursor, Claude, and other MCP clients). This site hosts a public instance so you can query chain data from compatible clients without running the server yourself.

What it connects to

The MCP service forwards tool calls to the public mainnet JSON-RPC endpoint https://rpc-mainnet.nimiqscan.com. Wallet- and validator-specific tools stay disabled on this deployment unless we enable them server-side.

Streamable HTTP endpoint

Remote MCP clients should use this URL (path /mcp) with the Streamable HTTP transport:

https://mcp.nimiqscan.com/mcp

Cursor

Add the server under Settings → Features → Model Context Protocol, or merge this into your user or project mcp.json (adjust if your Cursor version uses a different shape—use the endpoint URL above as the remote endpoint):

{
  "mcpServers": {
      "nimiq": {
      "url": "https://mcp.nimiqscan.com/mcp"
    }
  }
}

After saving, reload MCP or restart Cursor. You should see Nimiq tools (for example getBlockNumber) in the client’s tool list.

Other clients

Any MCP client that supports remote MCP over Streamable HTTP can use the same endpoint. Clients that only support stdio need a local or container run of the server; see the upstream docs.

Source & options

Implementation and environment variables (RPC URL, optional wallet/validator tools) are documented in the nimiq-mcp repository.