Home / MCP registry index / com.blockscout/mcp-server
com.blockscout/mcp-server
com.blockscout/mcp-server in the official MCP registry.
Endpoint https://mcp.blockscout.com/mcp. Source: github.com/blockscout/mcp-server.
The registry describes it as: MCP server for Blockscout
We read its 16 tools on 2026-10-22. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
__unlock_blockchain_analysis__ get_block_info get_block_number get_address_by_ens_name get_transactions_by_address get_token_transfers_by_address lookup_token_by_symbol get_contract_abi inspect_contract_code read_contract get_address_info get_tokens_by_address nft_tokens_by_address get_transaction_info get_chains_list direct_api_call
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-blockscout-mcp-server)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.