Blockscout Mcp
Connect your agent to Blockscout on-chain data, metrics, and analytics through 56 MCP tools while building or operating web3 products.
Overview
io.github.junct-bot/blockscout-mcp is a MCP server for the Build phase that delivers 56 tools for Blockscout on-chain data, metrics, and analytics.
What is this MCP server?
- 56 MCP tools for Blockscout data, metrics, and on-chain analytics
- Remote streamable-http server at blockscout.mcp.junct.dev (v1.1.0)
- Supports agent-driven contract, transaction, and network insight during development
- Open GitHub repo junct-bot/blockscout-mcp for review and contributions
- Useful across build-time integration and operate-time incident triage
- 56 Blockscout MCP tools
- Server version 1.1.0
- Streamable-http remote endpoint
What problem does it solve?
Web3 solo builders lose time context-switching to explorers when their agent needs consistent chain metrics and analytics in code or support threads.
Who is it for?
Builders shipping on-chain features, dashboards, or support agents who want Blockscout-grade data without custom indexer infrastructure.
Skip if: Teams with no web3 surface area who only need CEX prices or centralized app analytics.
What do I get? / Deliverables
After adding the Blockscout MCP remote, your agent can query on-chain analytics tools directly while you build integrations or triage live issues.
- Integrated Blockscout analytics accessible from agent tool calls
- Faster contract and transaction investigation during build and ops
- Structured chain metrics for dashboards and support playbooks
Recommended MCP Servers
Journey fit
Canonical placement is Build because the main payoff is integrating explorer-grade on-chain data into apps and agent workflows you are actively shipping. Integrations subphase matches Blockscout as an external data plane for contracts, txs, and chain metrics—not a standalone research essay.
How it compares
On-chain explorer analytics MCP, not a Binance market-data server or a smart-contract deploy skill.
Common Questions / FAQ
Who is io.github.junct-bot/blockscout-mcp for?
Solo and small-team developers building web3 products or ops workflows who want fifty-six Blockscout analytics tools inside their MCP agent.
When should I use io.github.junct-bot/blockscout-mcp?
Use it while integrating explorer data into your app or when monitoring and investigating on-chain behavior during operations.
How do I add io.github.junct-bot/blockscout-mcp to my agent?
Add https://blockscout.mcp.junct.dev/mcp as a streamable-http MCP server in your Claude Code, Cursor, Codex, or compatible client configuration.