How much does Blockscout MCP cost?

Blockscout MCP uses a free pricing model.

What are the main advantages of Blockscout MCP?

Extensive multi-chain support covering 3,000+ EVM-compatible networks through a single interface.. Smart context optimization that slices and paginates large datasets to prevent AI context overflow.. Native integration with popular AI hosts like Claude Desktop and Cursor for zero-code setup.. Supports progress notifications, providing real-time feedback during long-running blockchain queries.. Unified architecture that serves both MCP and versioned REST API endpoints for developer flexibility..

What are the drawbacks of Blockscout MCP?

Performance and data accuracy are strictly dependent on the underlying Blockscout API's availability.. Free public endpoints are limited by rate limits, making a Pro API key necessary for production traffic.. Primarily focused on EVM chains, leaving agents blind to non-EVM ecosystems like Solana or Bitcoin.. The setup requires local configuration files (mcp-config.json) which may be intimidating for non-technical users..

Blockscout MCP

Unverified verified 13 jun 2026

Pricing: Free Company: blockscout Last verified: 2026-06-13

Visit Website

Updated May 26, 2026

TL;DR

Blockscout MCP is a middleware server that connects AI agents like Claude and Cursor to live blockchain data across 3,000+ EVM-compatible chains. It eliminates the need for complex RPC calls by providing a standardized Model Context Protocol (MCP) interface for querying balances, transactions, and smart contract metadata.

What Users Actually Pay

No user-reported pricing yet.

Our Take

Blockscout MCP addresses a critical bottleneck in the 'AI + Crypto' ecosystem: the high token cost and technical complexity of feeding raw blockchain data into Large Language Models. By acting as a specialized 'bridge,' it translates the dense, often hex-heavy output of blockchain nodes into structured, context-optimized data that LLMs can process efficiently. Its integration with over 3,000 chains through the Blockscout ecosystem makes it one of the most comprehensive data sources for agentic crypto workflows. The product's standout strength is its 'smart' data handling, featuring response slicing and automatic truncation to prevent LLM context window overflows—a frequent issue when querying large transaction histories. However, users should be aware that while the middleware is free and open-source, production-level reliability still hinges on the rate limits of the underlying Blockscout API instances, which may require a Pro tier for high-frequency agents. Blockscout MCP is best suited for developers building AI-powered crypto wallets, automated security auditors, and cross-chain portfolio management tools. It successfully moves blockchain interaction away from manual dashboard surfing toward seamless, natural-language-driven automation.

Similar Products

Instagram

Google Sheets

Clay

Pros

+ Extensive multi-chain support covering 3,000+ EVM-compatible networks through a single interface.
+ Smart context optimization that slices and paginates large datasets to prevent AI context overflow.
+ Native integration with popular AI hosts like Claude Desktop and Cursor for zero-code setup.
+ Supports progress notifications, providing real-time feedback during long-running blockchain queries.
+ Unified architecture that serves both MCP and versioned REST API endpoints for developer flexibility.

Cons

- Performance and data accuracy are strictly dependent on the underlying Blockscout API's availability.
- Free public endpoints are limited by rate limits, making a Pro API key necessary for production traffic.
- Primarily focused on EVM chains, leaving agents blind to non-EVM ecosystems like Solana or Bitcoin.
- The setup requires local configuration files (mcp-config.json) which may be intimidating for non-technical users.

Sentiment Analysis

+0.85 — Very PositiveUpdated May 9, 2026

Sentiment has improved since last capture. Sentiment is overwhelmingly positive, particularly among the AI developer community. Users appreciate the standardized interface for 3,000+ chains, which solves the fragmented data problem in Web3. The sentiment has improved significantly from 0.40 as the product matured and gained more mentions in major MCP registries.

Sentiment Over Time

By Source

github+0.85

15 mentions

Sample quotes (1)

"This server wraps Blockscout APIs and exposes blockchain data via MCP so that AI agents and tools can access and analyze it contextually."

X (Twitter)+0.90

25 mentions

Sample quotes (1)

"The Blockscout MCP Server gives AI agents a clean tool surface for on-chain data across 3000+ chains — no RPC plumbing required."

smithery+0.80

7630 mentions

Sample quotes (1)

"Enable multi-chain support and deliver enhanced user experience with progress notifications for long-running queries."

Agent Readiness

68/100

Blockscout MCP is highly agent-ready, specifically designed for the Model Context Protocol ecosystem. It features a unified architecture serving both REST and MCP, excellent technical documentation via GitHub, and specialized 'Agent Skills' for structured instruction handling. While it lacks direct Zapier/Make modules, its native n8n support and deep integration with Claude/Cursor make it a top-tier choice for autonomous blockchain agents.

API Surface100

Public APIRESTJSON-RPC (MCP)Free TieropenApi

Protocol Support40

MCP (18 tools)

SDK Availability35

npm: @0xagmaso/blockscout-mcp

Integration Ecosystem50

n8nWebhooksClaude DesktopCursorChainscoutAgent-Skills

Developer Experience100

Docs: excellentSandboxVersioningChangelogStatus Page

Last checked May 9, 2026

MCP Integrations

1 server16 tools5,940 total uses

Blockscout MCP Serverblockscout/mcp-server

smitheryVerifiedRemoteHigh match

Provide 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.

5,940 uses

16 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_info Get 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_block_number Retrieves the block number and timestamp for a specific date/time or the latest block. Use when you need a block height for a specific point in time (e.g., "block at 2024-01-01") or the current chain tip. If `datetime` is provided, finds the block immediately preceding that time. If omitted, returns the latest indexed block.
get_address_by_ens_name Useful for when you need to convert an ENS domain name (e.g. "blockscout.eth") to its corresponding Ethereum address.
get_transactions_by_address Retrieves 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. Requires an `age_from` date to scope results for performance and relevance. 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_address Get 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_symbol Search 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_abi Get 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_contract Calls 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_info Get comprehensive information about an address, including: - Address existence check - Native token (ETH) balance (provided as is, without adjusting by decimals) - First transaction details (block number and timestamp) for age calculation - 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_address Get 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.
nft_tokens_by_address Retrieve 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_info Get 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_chains_list Get 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.