| name | blockscout |
| description | Blockscout MCP tool reference for on-chain data queries. Covers all 16 tools: address info, transactions, token transfers, NFTs, contract ABI/source, read-only calls, ENS resolution, and block data across 8+ chains. TRIGGER when: user asks about on-chain data, contract state, token balances, transaction history, ENS lookup, NFT holdings, or uses blockscout MCP tools. DO NOT TRIGGER when: user asks about crypto market prices or trading volume (use coingecko skill), or writing Solidity code (use solidity-auditor skill).
|
| metadata | {"author":"DROOdotFOO","version":"1.1.0","tags":"blockscout, blockchain, onchain, mcp, ethereum, web3"} |
Blockscout MCP
On-chain data queries via Blockscout MCP server (already configured).
16 tools across address intelligence, transactions, contracts, and blocks.
Chain support
EVM-only. Blockscout covers 90+ EVM chains. Not available for native Solana
or Tron -- use CoinGecko contract endpoints for token data on those chains.
Solana via Neon EVM: Chain 245022934 covers the Neon EVM layer on Solana
(EVM-compatible contracts deployed on Solana).
Common chain IDs
| Chain | ID | Chain | ID |
|---|
| Ethereum | 1 | Arbitrum One | 42161 |
| Polygon | 137 | OP Mainnet | 10 |
| Base | 8453 | zkSync Era | 324 |
| Gnosis | 100 | Scroll | 534352 |
| Celo | 42220 | Mode | 34443 |
| Neon EVM (Solana) | 245022934 | Filecoin | 314 |
| Robinhood Chain | 4663 | | |
Robinhood Chain (4663) is an Arbitrum Orbit L3 (native currency ETH), reachable by
chain_id like any other -- no instance URL needed.
Default: Ethereum (1). Use get_chains_list to discover all 90+ supported chains.
Discover a chain ID
For any chain not in the table -- Orbit L3s, new rollups, or chains with their own
Blockscout instance (e.g. robinhoodchain.blockscout.com) -- pass a name substring to
get_chains_list instead of assuming it is unsupported:
get_chains_list(query="robinhood")
-> { name: "Robinhood Chain", chain_id: "4663", ecosystem: "Arbitrum Orbit" }
If a chain has a Blockscout explorer, it is almost certainly reachable through the MCP
by chain_id -- you do not need the instance URL.
Reference
What You Get
- Reference documentation for all 16 Blockscout MCP tools covering address intelligence, transactions, contracts, and block data.
- Chain ID lookup tables and common usage patterns for querying on-chain state across 90+ EVM chains.
- Pagination handling, error recovery, and time-based query guidance for efficient data retrieval.
See also
coingecko -- market prices, volumes, DEX pools, trending tokenssentinel -- automated contract monitoring with alert rulesethskills -- framework selection, RPC providers, EIP/ERC standardssolidity-auditor -- smart contract security patterns and audit methodology
