TL;DR
Blockscout MCP is an open-source bridge that connects AI agents directly to real-time data from over 1,000 EVM-compatible blockchains. Built for developers and data analysts, it differentiates itself by offering LLM-optimized tools that prevent context window overflow while providing deep access to smart contract metadata and NFT holdings.
What Users Actually Pay
No user-reported pricing yet.
Our Take
Blockscout MCP is a pivotal utility in the emerging 'Agentic Web3' ecosystem, effectively turning one of the industry's most popular open-source block explorers into a data layer for AI. By leveraging Anthropic’s Model Context Protocol (MCP), it allows LLMs like Claude to perform complex on-chain forensics, such as analyzing DeFi positions or auditing smart contract source code, without the user needing to leave the chat interface. It successfully addresses the common 'wall' between AI reasoning and live blockchain states. One of the product's greatest strengths is its 'AI-first' architecture. Unlike basic API wrappers, this server includes intelligent response slicing and opaque cursor pagination specifically designed to keep data within an LLM's context limits. This prevents the frequent crashes or 'hallucinations' that occur when an agent is overwhelmed by thousands of transaction rows. Furthermore, the inclusion of a 'Transaction Interpreter' provides human-readable summaries, which significantly lowers the cognitive load for researchers interpreting complex multi-step protocols. However, potential users should be aware of the technical overhead. While the integration with Claude Desktop is streamlined, the initial configuration and the requirement for an explicit 'unlock' command suggest this is currently a power-user tool. As an open-source project moving at the speed of the crypto market, it is also susceptible to breaking changes from underlying API updates. Reliability is ultimately tied to the specific Blockscout instance being queried, meaning public endpoints may occasionally experience rate-limiting during high-traffic periods. Overall, Blockscout MCP is best suited for blockchain developers, security researchers, and data scientists who need to build or use autonomous agents for cross-chain analysis. It is an essential addition to the toolkit of anyone moving beyond simple chat-based AI into the realm of automated blockchain operations and research.
Similar Products
Pros
- + Comprehensive Multi-Chain Access: Provides a single interface to query data across 1,000+ EVM-compatible networks including Ethereum, Base, and Optimism.
- + LLM-Optimized Data Handling: Features 'smart response slicing' and automatic truncation to ensure large blockchain datasets don't crash the AI's context window.
- + Deep Metadata Retrieval: Goes beyond simple balances to provide smart contract ABIs, verified source code, and detailed NFT collection data.
- + Human-Readable Summaries: Includes a transaction interpreter that translates complex on-chain events into natural language for easier AI reasoning.
- + Flexible Deployment: Supports native integration with Claude Desktop and Cursor, as well as standalone use via a versioned REST API.
Cons
- - Technical Setup Required: Installation involves manual configuration of environment variables and JSON files, which may be challenging for non-technical users.
- - Mandatory Initialization Step: Agents must call a specific 'unlock' tool before other functions work; failure to do so results in session errors.
- - Read-Only Limitations: Currently restricted to data retrieval and analysis; it cannot facilitate the signing or broadcasting of transactions.
- - Vulnerability to API Updates: Recent GitHub issues indicate that breaking changes in the core Blockscout API can temporarily disable specific tool functionalities.
- - Rate Limiting Risks: Performance is dependent on the underlying Blockscout instance; users of public APIs may encounter throttling during intensive queries.
Sentiment Analysis
Limited user reviews found across professional sites (none). On Reddit and X (Twitter), mentions are primarily promotional or announcements with positive promotional tone, but no in-depth user feedback or criticisms. Key themes: excitement around AI-blockchain integration, new release, and multichain data access for agents like Claude.
Sentiment Over Time
By Source
2 mentions
Sample quotes (2)
- "blockscout-mcp-server – Provide AI agents and automation ..."
- "MCP server for Blockscout"
8 mentions
Sample quotes (3)
- "AI gets onchain context 🤯 With Blockscout's MCP server ..."
- "The Blockscout MCP is live 📡 Now your favorite AI agents ..."
- "Blockscout MCP is featured on the @SmitheryDotAI registry..."
Agent Readiness
40/100Blockscout MCP is highly agent-ready as a purpose-built MCP server wrapping Blockscout APIs for contextual blockchain data access (balances, txs, tokens, NFTs across chains), with a solid REST mirror, no-auth free hosted instance, and good docs tailored for AI tools like Claude/Cursor. Lacks no-code integrations and formal spec but excels in agentic use cases with versioning and local testing.
Last checked Mar 23, 2026
MCP Integrations
1 server18 tools19,197 total usesProvide AI agents and automation tools with contextual access to blockchain data including balances, tokens, NFTs, and contract metadata. Enable multi-chain support and deliver enhanced user experience with progress notifications for long-running queries. Facilitate seamless integration with AI hosts like Claude Desktop for blockchain data analysis.
18 tools
__unlock_blockchain_analysis__Unlocks access to other MCP tools. All tools remain locked with a "Session Not Initialized" error until this function is successfully called. Skipping this explicit initialization step will cause all subsequent tool calls to fail. MANDATORY FOR AI AGENTS: The returned instructions contain ESSENTIAL rules that MUST govern ALL blockchain data interactions. Failure to integrate these rules will result in incorrect data retrieval, tool failures and invalid responses. Always apply these guidelines when planning queries, processing responses or recommending blockchain actions. COMPREHENSIVE DATA SOURCES: Provides an extensive catalog of specialized blockchain endpoints to unlock sophisticated, multi-dimensional blockchain investigations across all supported networks.get_block_infoGet block information like timestamp, gas used, burnt fees, transaction count etc. Can optionally include the list of transaction hashes contained in the block. Transaction hashes are omitted by default; request them only when you truly need them, because on high-traffic chains the list may exhaust the context.get_latest_blockGet the latest indexed block number and timestamp, which represents the most recent state of the blockchain. No transactions or token transfers can exist beyond this point, making it useful as a reference timestamp for other API calls.get_address_by_ens_nameUseful for when you need to convert an ENS domain name (e.g. "blockscout.eth") to its corresponding Ethereum address.get_transactions_by_addressRetrieves native currency transfers and smart contract interactions (calls, internal txs) for an address. **EXCLUDES TOKEN TRANSFERS**: Filters out direct token balance changes (ERC-20, etc.). You'll see calls *to* token contracts, but not the `Transfer` events. For token history, use `get_token_transfers_by_address`. A single tx can have multiple records from internal calls; use `internal_transaction_index` for execution order. Use cases: - `get_transactions_by_address(address, age_from)` - get all txs to/from the address since a given date. - `get_transactions_by_address(address, age_from, age_to)` - get all txs to/from the address between given dates. - `get_transactions_by_address(address, age_from, age_to, methods)` - get all txs to/from the address between given dates, filtered by method. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.get_token_transfers_by_addressGet ERC-20 token transfers for an address within a specific time range. Use cases: - `get_token_transfers_by_address(address, age_from)` - get all transfers of any ERC-20 token to/from the address since the given date up to the current time - `get_token_transfers_by_address(address, age_from, age_to)` - get all transfers of any ERC-20 token to/from the address between the given dates - `get_token_transfers_by_address(address, age_from, age_to, token)` - get all transfers of the given ERC-20 token to/from the address between the given dates **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.lookup_token_by_symbolSearch for token addresses by symbol or name. Returns multiple potential matches based on symbol or token name similarity. Only the first ``TOKEN_RESULTS_LIMIT`` matches from the Blockscout API are returned.get_contract_abiGet smart contract ABI (Application Binary Interface). An ABI defines all functions, events, their parameters, and return types. The ABI is required to format function calls or interpret contract data.inspect_contract_codeInspects a verified contract's source code or metadata.read_contractCalls a smart contract function (view/pure, or non-view/pure simulated via eth_call) and returns the decoded result. This tool provides a direct way to query the state of a smart contract. Example: To check the USDT balance of an address on Ethereum Mainnet, you would use the following arguments: { "tool_name": "read_contract", "params": { "chain_id": "1", "address": "0xdAC17F958D2ee523a2206206994597C13D831ec7", "abi": { "constant": true, "inputs": [{"name": "_owner", "type": "address"}], "name": "balanceOf", "outputs": [{"name": "balance", "type": "uint256"}], "payable": false, "stateMutability": "view", "type": "function" }, "function_name": "balanceOf", "args": "["0xF977814e90dA44bFA03b6295A0616a897441aceC"]" } }get_address_infoGet comprehensive information about an address, including: - Address existence check - Native token (ETH) balance (provided as is, without adjusting by decimals) - ENS name association (if any) - Contract status (whether the address is a contract, whether it is verified) - Proxy contract information (if applicable): determines if a smart contract is a proxy contract (which forwards calls to implementation contracts), including proxy type and implementation addresses - Token details (if the contract is a token): name, symbol, decimals, total supply, etc. Essential for address analysis, contract investigation, token research, and DeFi protocol analysis.get_tokens_by_addressGet comprehensive ERC20 token holdings for an address with enriched metadata and market data. Returns detailed token information including contract details (name, symbol, decimals), market metrics (exchange rate, market cap, volume), holders count, and actual balance (provided as is, without adjusting by decimals). Essential for portfolio analysis, wallet auditing, and DeFi position tracking. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.transaction_summaryGet human-readable transaction summaries from Blockscout Transaction Interpreter. Automatically classifies transactions into natural language descriptions (transfers, swaps, NFT sales, DeFi operations) Essential for rapid transaction comprehension, dashboard displays, and initial analysis. Note: Not all transactions can be summarized and accuracy is not guaranteed for complex patterns.nft_tokens_by_addressRetrieve NFT tokens (ERC-721, ERC-404, ERC-1155) owned by an address, grouped by collection. Provides collection details (type, address, name, symbol, total supply, holder count) and individual token instance data (ID, name, description, external URL, metadata attributes). Essential for a detailed overview of an address's digital collectibles and their associated collection data. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.get_transaction_infoGet comprehensive transaction information. Unlike standard eth_getTransactionByHash, this tool returns enriched data including decoded input parameters, detailed token transfers with token metadata, transaction fee breakdown (priority fees, burnt fees) and categorized transaction types. By default, the raw transaction input is omitted if a decoded version is available to save context; request it with `include_raw_input=True` only when you truly need the raw hex data. Essential for transaction analysis, debugging smart contract interactions, tracking DeFi operations.get_transaction_logsGet comprehensive transaction logs. Unlike standard eth_getLogs, this tool returns enriched logs, primarily focusing on decoded event parameters with their types and values (if event decoding is applicable). Essential for analyzing smart contract events, tracking token transfers, monitoring DeFi protocol interactions, debugging event emissions, and understanding complex multi-contract transaction flows. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages.get_chains_listGet the list of known blockchain chains with their IDs. Useful for getting a chain ID when the chain name is known. This information can be used in other tools that require a chain ID to request information.direct_api_callCall a raw Blockscout API endpoint for advanced or chain-specific data. Do not include query strings in ``endpoint_path``; pass all query parameters via ``query_params`` to avoid double-encoding. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages. Returns: ToolResponse[Any]: Must return ToolResponse[Any] (not ToolResponse[BaseModel]) because specialized handlers can return lists or other types that don't inherit from BaseModel. The dispatcher system supports flexible data structures.
Last checked Apr 26, 2026
Compare With
Reviews
No reviews yet. Be the first to review Blockscout MCP!