Analytics
blockscout.com
Provides blockchain data retrieval and analysis, including block information, ENS name resolution, and transaction history.
ENDPOINT 1
https://mcp.blockscout.com/mcp
MCP server metadata
- Name
- blockscout-mcp-server
- Version
- 1.26.0
Blockscout MCP server version: 0.17.0 Operating rules, execution strategies, and the curated `direct_api_call` endpoint reference for analyzing Blockscout data live in the `blockscout-analysis` skill (version 0.6.0). If the skill is already loaded in your context, use that copy. If no copy is loaded, fetch the entry point from `blockscout-mcp://skill/SKILL.md` over MCP resources or `GET /skill/SKILL.md` over HTTP. When `SKILL.md` mentions a reference path such as `references/foo.md`, resolve it as `blockscout-mcp://skill/` plus that path over MCP resources, or `GET /skill/` plus that path over HTTP.
Known tools 16
__unlock_blockchain_analysis__Mandatory initialization step for any session against the Blockscout MCP server.
Inferred read-onlyget_block_infoGet block information like timestamp, gas used, burnt fees, transaction count etc.
Inferred read-onlyget_block_numberRetrieves the block number and timestamp for a specific date/time or the latest block.
Inferred read-onlyget_transactions_by_addressRetrieves native currency transfers and smart contract interactions (calls, internal txs) for an address.
Inferred read-onlyget_token_transfers_by_addressGet ERC-20 token transfers for an address within a specific time range.
Inferred read-onlyread_contractCalls a smart contract function (view/pure, or non-view/pure simulated via eth_call) and returns the decoded result.
Inferred read-onlyget_address_infoGet 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.
Inferred read-onlyget_tokens_by_addressGet comprehensive ERC20 token holdings for an address with enriched metadata and market data.
Inferred read-onlynft_tokens_by_addressRetrieve NFT tokens (ERC-721, ERC-404, ERC-1155) owned by an address, grouped by collection.
Inferred read-onlydirect_api_callCall a raw Blockscout API endpoint for advanced or chain-specific data.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.blockscout-mcp-server]
url = "https://mcp.blockscout.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"blockscout-mcp-server": {
"type": "http",
"url": "https://mcp.blockscout.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: blockscout-mcp-server
Remote MCP URL: https://mcp.blockscout.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"blockscout-mcp-server": {
"url": "https://mcp.blockscout.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"blockscout-mcp-server": {
"type": "http",
"url": "https://mcp.blockscout.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "blockscout-mcp-server",
"transport": "streamable-http",
"url": "https://mcp.blockscout.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for blockscout.com was fetched 2026-07-26T08:58:42.683Z.
blockscout.com is assessed as Trusted: Domain has an established technology history spanning over a year.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.