# com.blockscout/mcp-server (remote · mcp.blockscout.com) MCP server for Blockscout - Trust score: 70/100 (medium) - Change this week: +8 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-08-03 ## Components - remote · `mcp.blockscout.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-blockscout-mcp-server/mcp.md), [page](https://verifymcp.io/servers/com-blockscout-mcp-server/mcp) ## Channel facts - Endpoint: `https://mcp.blockscout.com/mcp` - Transports: `streamable-http` - Auth: `none` - Version: `0.17.0` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-08-03. - **Endpoint Security**: 80/100 - The endpoint's TLS certificate is valid, in date, and uses a strong key. - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. - HTTPS is enforced; there's no plaintext access path. - The HSTS (Strict-Transport-Security) header is present. - DNSSEC check failed: this domain isn't protected by DNSSEC. - **Transport & Reachability**: 100/100 - Verified streamable-http transport via a live MCP handshake. - **Schema Quality & AI Usability**: 46/100 - 5% of prompts and resources have a non-trivial description (not blank, and not just the item's name). - AI-judged instruction clarity (good). - Tool/resource definitions use about 3319 tokens (~89/item across 37 items; 16 tools + 21 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 27/100 - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 100/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 100% of tool parameters carry a description. - Structured output schemas are declared (100% of tools); any adoption earns full credit. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### Claude ```bash claude mcp add --transport http com-blockscout-mcp-server https://mcp.blockscout.com/mcp ``` ### Codex ```toml [mcp_servers.com-blockscout-mcp-server] url = "https://mcp.blockscout.com/mcp" ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "com-blockscout-mcp-server": { "type": "remote", "url": "https://mcp.blockscout.com/mcp", "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add com-blockscout-mcp-server --url https://mcp.blockscout.com/mcp --transport streamable-http ``` ### Hermes ```yaml mcp_servers: com-blockscout-mcp-server: url: "https://mcp.blockscout.com/mcp" ``` ### Other ```json { "mcpServers": { "com-blockscout-mcp-server": { "type": "http", "url": "https://mcp.blockscout.com/mcp" } } } ``` The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs. ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-08-02 (score 70, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-31 (score 69, +5) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-30 (score 64, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-29 (score 64, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-07-28 (score 63, +1) No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes. Other categories moved too: Schema Quality & AI Usability fell 1. ### 2026-07-27 (score 62, 0) - [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server ### 2026-07-26 (score 62) First indexed and scored. ## MCP tools (16) ### `__unlock_blockchain_analysis__` (~94 tokens) Unlock Blockchain Analysis Mandatory initialization step for any session against the Blockscout MCP server. Returns server reference data plus the `blockscout-analysis` skill pointer and URI resolution rule. MANDATORY FOR AI AGENTS: Call this tool first in every session. The returned payload identifies where the operating rules and analysis framework live and how to read referenced skill files before executing further tool calls. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_block_info` (~115 tokens) Get Block Information 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. Input parameters: - `chain_id` (string, required): The ID of the blockchain - `include_transactions`: If true, includes a list of transaction hashes from the block. - `number_or_hash` (string, required): Block number or hash Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_block_number` (~152 tokens) 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. Input parameters: - `chain_id` (string, required): The ID of the blockchain - `datetime`: The date and time (ISO 8601 format, e.g. 2025-05-22T23:00:00.00Z) to find the block for. If omitted, returns the latest block. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_address_by_ens_name` (~55 tokens) 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. Input parameters: - `name` (string, required): ENS domain name to resolve Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_transactions_by_address` (~315 tokens) 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. Requires an `age_from` date to scope results for performance and relevance. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages. Input parameters: - `address` (string, required): Address which either sender or receiver of the transaction - `age_from` (string, required): Start date and time (e.g 2025-05-22T23:00:00.00Z). Alone, returns all transactions to/from the address since this date. - `age_to`: End date and time (e.g 2025-05-22T22:30:00.00Z). Adding this bounds the upper end of the date range started by `age_from`. - `chain_id` (string, required): The ID of the blockchain - `cursor`: The pagination cursor from a previous response to get the next page of results. - `methods`: A method signature to filter transactions by (e.g 0x304e6ade). Filters the (optionally date-bounded) results to a specific method signature. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data` (array): The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_token_transfers_by_address` (~237 tokens) Get Token Transfers by Address Get ERC-20 token transfers for an address within a specific time range. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages. Input parameters: - `address` (string, required): Address which either transfer initiator or transfer receiver - `age_from` (string, required): Start date and time (e.g 2025-05-22T23:00:00.00Z). Alone, returns all ERC-20 transfers to/from the address since this date. - `age_to`: End date and time (e.g 2025-05-22T22:30:00.00Z). Adding this bounds the upper end of the date range started by `age_from`; if omitted, transfers up to the current time are returned. - `chain_id` (string, required): The ID of the blockchain - `cursor`: The pagination cursor from a previous response to get the next page of results. - `token`: An ERC-20 token contract address to restrict results to a single token. If omitted, returns transfers of all tokens. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data` (array): The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `lookup_token_by_symbol` (~80 tokens) 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 7 matches from the Blockscout API are returned. Input parameters: - `chain_id` (string, required): The ID of the blockchain - `symbol` (string, required): Token symbol or name to search for Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data` (array): The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_contract_abi` (~74 tokens) 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. Input parameters: - `address` (string, required): Smart contract address - `chain_id` (string, required): The ID of the blockchain Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `inspect_contract_code` (~73 tokens) Inspect Contract Code Inspects a verified contract's source code or metadata. Input parameters: - `address` (string, required): The address of the smart contract. - `chain_id` (string, required): The ID of the blockchain. - `file_name`: The name of the source file to inspect. If omitted, returns contract metadata and the list of source files. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `read_contract` (~490 tokens) Read from 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"]" } } Input parameters: - `abi` (object, required): The JSON ABI for the specific function being called. This should be a dictionary that defines the function's name, inputs, and outputs. The function ABI can be obtained using the `get_contract_abi` t… - `address` (string, required): Smart contract address - `args` (string): A JSON string containing an array of arguments. Example: "["0xabc..."]" for a single address argument, or "[]" for no arguments. Order and types must match ABI inputs. Addresses: use 0x-prefixed stri… - `block`: The block identifier to read the contract state from. Can be a block number (e.g., 19000000) or a string tag (e.g., 'latest'). Defaults to 'latest'. - `chain_id` (string, required): The ID of the blockchain - `function_name` (string, required): The symbolic name of the function to be called. This must match the `name` field in the provided ABI. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_address_info` (~185 tokens) Get Address Information 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. Input parameters: - `address` (string, required): Address to get information about - `chain_id` (string, required): The ID of the blockchain Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_tokens_by_address` (~154 tokens) 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. Input parameters: - `address` (string, required): Wallet address - `chain_id` (string, required): The ID of the blockchain - `cursor`: The pagination cursor from a previous response to get the next page of results. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data` (array): The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `nft_tokens_by_address` (~163 tokens) Get 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. Input parameters: - `address` (string, required): NFT owner address - `chain_id` (string, required): The ID of the blockchain - `cursor`: The pagination cursor from a previous response to get the next page of results. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data` (array): The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_transaction_info` (~152 tokens) Get Transaction Information 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. Input parameters: - `chain_id` (string, required): The ID of the blockchain - `include_raw_input`: If true, includes the raw transaction input data. - `transaction_hash` (string, required): Transaction hash Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `get_chains_list` (~153 tokens) Get List of Chains Get supported blockchain chains with their chain IDs. Ethereum Mainnet is `chain_id` `1`; use this tool to resolve any other chain. Use this when another tool needs a supported `chain_id` and only the chain name, ecosystem, or native currency is known. Prefer a narrow `query` to avoid returning the full registry to the agent. Do not rely on partial numeric chain ID queries such as `1`, because matching is substring-based and may return many chains. Input parameters: - `query`: Optional case-insensitive substring filter applied to chain name, chain ID, native currency, and ecosystem. Prefer narrow text terms over partial numeric chain IDs because matching is substring-based. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data` (array): The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ### `direct_api_call` (~307 tokens) Direct Blockscout API Call Call a raw Blockscout API endpoint for advanced or chain-specific data. Before the first call to this tool in a session, read `blockscout-mcp://skill/SKILL.md` (the operating rules), then `blockscout-mcp://skill/references/blockscout-api-index.md` (the authoritative index of callable endpoints); skip both reads only if this skill content is already in context. Recalled Blockscout API knowledge is not a substitute: endpoint paths, parameters, and response shapes vary across Blockscout versions and per-chain deployments. Supports POST requests with a JSON body for endpoints like JSON RPC. **SUPPORTS PAGINATION**: If response includes 'pagination' field, use the provided next_call to get additional pages (GET only). Input parameters: - `chain_id` (string, required): The ID of the blockchain - `cursor`: The pagination cursor from a previous response to get the next page of results. - `endpoint_path` (string, required): The Blockscout API path to call (e.g., '/api/v2/stats'); do not include query strings — pass all query parameters via query_params to avoid double-encoding. - `json_body`: JSON request body for POST requests. - `method` (string): HTTP method used for the upstream call. Use POST with json_body. - `query_params`: Optional query parameters forwarded to the Blockscout API. Output parameters: - `content_text`: Optional human-readable summary used for MCP content responses. - `data`: The main data payload of the tool's response. - `data_description`: A list of notes explaining the structure, fields, or conventions of the 'data' payload. - `instructions`: A list of suggested follow-up actions or instructions for the LLM to plan its next steps. - `notes`: A list of important contextual notes, such as warnings about data truncation or data quality issues. - `pagination`: Pagination information, present only if the 'data' is a single page of a larger result set. ## Diagnostics Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-blockscout-mcp-server/mcp#diagnostics ## Score history - 2026-08-03: 70 - 2026-08-02: 70 - 2026-08-01: 69 - 2026-07-31: 69 - 2026-07-30: 64 - 2026-07-29: 64 - 2026-07-28: 63 - 2026-07-27: 62 - 2026-07-26: 62 ## Links - Remote endpoint: https://mcp.blockscout.com/mcp - Repository: https://github.com/blockscout/mcp-server - Website: https://blockscout.com/ - Changelog RSS feed: https://verifymcp.io/servers/com-blockscout-mcp-server/mcp/changelog.xml - Changelog JSON feed: https://verifymcp.io/servers/com-blockscout-mcp-server/mcp/changelog.json - HTML version of this page: https://verifymcp.io/servers/com-blockscout-mcp-server/mcp