blockscout-analysis
Blockscout Analysis
Analyze blockchain activity and build scripts, tools, and applications that query on-chain data. All data access goes through the Blockscout MCP Server — via native MCP tool calls, the MCP REST API, or both.
Infrastructure
Blockscout MCP Server
The server is the sole runtime data source. It is multichain — almost all tools accept a chain_id parameter. Use get_chains_list to discover supported chains. Always pass its query parameter — a case-insensitive substring match by chain name, ecosystem, or native currency — so the call returns only the relevant chains instead of the full registry. Fall back to a no-argument call only when a query returns no matches.
| Access method | URL | Use case |
|---|---|---|
| Native MCP | https://mcp.blockscout.com/mcp |
Direct tool calls from the agent |
| REST API | https://mcp.blockscout.com/v1/{tool_name}?params |
HTTP GET calls from scripts |
Response format equivalence: Native MCP tool calls and REST API calls to the same tool return identical JSON response structures. When writing scripts targeting the REST API, use native MCP tool calls to probe and validate the expected response shape.
Available tools (16): unlock_blockchain_analysis, get_chains_list, get_address_info, get_address_by_ens_name, get_tokens_by_address, nft_tokens_by_address, get_transactions_by_address, get_token_transfers_by_address, get_block_info, get_block_number, get_transaction_info, get_contract_abi, inspect_contract_code, read_contract, lookup_token_by_symbol, direct_api_call.