How much does Blockscout MCP cost?

Blockscout MCP uses a free pricing model.

What are the main advantages of Blockscout MCP?

Official Claude Connector allows for one-click installation without terminal configuration.. Native support for 3,000+ EVM chains via unified Chainscout metadata integration.. Sophisticated context optimization features like base64-encoded cursor pagination and intelligent response slicing.. Open-source server architecture allows for both local Docker hosting and managed remote access.. Provides 'Agent Skills' which are markdown-based expertise packs that guide AI reasoning for complex on-chain tasks..

What are the drawbacks of Blockscout MCP?

Requires a Blockscout PRO API key for many high-data tools, which may involve costs for enterprise-level volume.. Mandatory 'unlock' tool calls and custom instructions can feel cumbersome for simple, one-off queries.. Community discussions on Reddit highlight potential security risks of running third-party MCP servers without thorough local review.. Currently focused strictly on EVM and Celestia; developers working on Solana or Bitcoin lack comparable functionality..

What are the best alternatives to Blockscout MCP?

Alternatives to Blockscout MCP in this category include Linkup, Google Sheets, Slack, Gmail, AgentMail.

Blockscout MCP

Unclaimed verified 26 jul 2026

[ score · 31 ]

Pricing: Free Company: blockscout Last verified: 2026-07-26

Visit Website

Updated Jul 27, 2026

TL;DR

Blockscout MCP is a server implementation that connects AI agents to real-time blockchain data across 3,000+ EVM chains through the Model Context Protocol. It is designed for developers and analysts using AI IDEs and assistants like Claude or Cursor to query on-chain balances, tokens, and contract metadata. Its key differentiator is its sophisticated context management, including response slicing and progress notifications to prevent LLM context overflow.

What Users Actually Pay

No user-reported pricing yet.

Our Take

Blockscout is making a strategic play to become the primary data layer for the emerging 'Web3 Agent' ecosystem. By adopting the MCP standard early and providing an official Claude connector, they have significantly lowered the barrier for developers building crypto-native assistants. The product is not just a raw API wrapper; it includes intelligent features like 'Agent Skills' (structured reasoning instructions) and 'Chainscout' integration for seamless multi-chain discovery. The tool's market position is currently unique: while other providers offer APIs, Blockscout is one of the few providing a production-ready, hosted MCP server that requires zero local setup for standard AI chat interfaces. Its strengths lie in its deep integration with the Claude ecosystem and its ability to handle large blockchain datasets without crashing the agent's context window through automated truncation and pagination. However, limitations include a dependency on the Blockscout Pro API for high-volume usage and the inherent security risks associated with running external MCP servers in local environments. It is best suited for Web3 developers building automated auditing tools, portfolio managers, and security researchers who need to interact with smart contracts through natural language.

Alternatives

Ranked by Revuo score — paid tiers never affect order.

Linkup

Google Sheets

Slack

Gmail

AgentMail

GitHub

Pros

+ Official Claude Connector allows for one-click installation without terminal configuration.
+ Native support for 3,000+ EVM chains via unified Chainscout metadata integration.
+ Sophisticated context optimization features like base64-encoded cursor pagination and intelligent response slicing.
+ Open-source server architecture allows for both local Docker hosting and managed remote access.
+ Provides 'Agent Skills' which are markdown-based expertise packs that guide AI reasoning for complex on-chain tasks.

Cons

- Requires a Blockscout PRO API key for many high-data tools, which may involve costs for enterprise-level volume.
- Mandatory 'unlock' tool calls and custom instructions can feel cumbersome for simple, one-off queries.
- Community discussions on Reddit highlight potential security risks of running third-party MCP servers without thorough local review.
- Currently focused strictly on EVM and Celestia; developers working on Solana or Bitcoin lack comparable functionality.

Agent Readiness

64/100

Blockscout MCP is highly optimized for autonomous AI agents, featuring a native Model Context Protocol implementation that supports both local stdio and remote HTTP transports. It excels in developer experience by providing a versioned REST API that mirrors its MCP tools, comprehensive GitHub documentation, and a ready-to-use Docker image for local testing. While it lacks standard SaaS connectors like Zapier, its direct integration into AI IDEs and the Anthropic Connectors Directory makes it a top-tier choice for agentic workflows.

API Surface100

Public APIRESTJSON-RPCSSEFree TieropenApi

Protocol Support40

MCP (16 tools)

SDK Availability35

npm: @0xagmaso/blockscout-mcp

Integration Ecosystem25

WebhooksClaude DesktopClaude CodeCursor IDEGemini CLIChatGPT Apps

Developer Experience100

Docs: excellentSandboxVersioningChangelogStatus Page

Last checked Jul 15, 2026

MCP Integrations

1 server16 tools927 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.

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