Ergo Blockchain MCP Server is an MCP server that gives AI assistants direct, standardized access to Ergo blockchain data - blocks, transactions, network statistics, addresses, and tokens - through a consistent interface. It enables blockchain exploration, address analysis, token information retrieval, and advanced analytics without the assistant needing to talk to the Ergo Explorer or Node APIs directly.

Use it when an AI assistant needs to explore the Ergo blockchain: checking network status, analyzing an address's balance and transaction history, tracking a token's holder distribution over time, or clustering related addresses for entity identification. It requires at minimum the Ergo Explorer API endpoint; advanced functions additionally need a running Ergo node and its API key. It is not the right tool for blockchains other than Ergo, since its tools and data model are specific to the Ergo Explorer and Node APIs.

• Blockchain exploration: retrieve blocks, transactions, and network statistics
• Address analysis: query balances, transaction history, and perform forensic analysis
• Token analytics: view token information, holder distribution, historical ownership, and collection data
• Ecosystem integration: access EIP information, oracle pool data, and address book
• Advanced analytics: analyze blockchain patterns, token metrics, and transaction flows
• Entity identification: discover related addresses via address clustering algorithms
• Interactive visualizations: openwebui_viz_tool renders an interactive D3.js network visualization for address clustering, and openwebui_entity_tool returns a text summary of detected entities for an address
• Response standardization in JSON or Markdown, with built-in token estimation for AI context window optimization
• Historical token holder tracking with block-height tracking

From source:

git clone https://github.com/ergo-mcp/ergo-explorer-mcp.git
cd ergo-explorer-mcp
pip install -r requirements.txt
python -m ergo_explorer.server

A Docker image is also available. The server requires the environment variable ERGO_EXPLORER_API (the Ergo Explorer API URL). Advanced node-level functions additionally accept the optional ERGO_NODE_API and ERGO_NODE_API_KEY.

Developers and analysts building AI assistants that need to explore the Ergo blockchain - checking balances, tracing transaction history, tracking token holders, or clustering related addresses - through a standardized MCP interface instead of calling the Ergo Explorer and Node APIs directly.