Blockscout MCP server
16 tools · Last check that passed 27 Oct 2026, 01:50 UTC
Blockscout's own remote MCP server gives an agent blockchain data from Blockscout explorers, such as balances, tokens, NFTs, transactions and contract code, across many chains. Once a day, Stackduke connects to it the way any MCP client would, with no account and no sign-in, and lists its tools. It never runs them.
All 16 tools
| Tool | Counted as |
|---|---|
__unlock_blockchain_analysis__ | Changes things |
direct_api_call | Changes things |
get_address_by_ens_name | Said to only read |
get_address_info | Said to only read |
get_block_info | Said to only read |
get_block_number | Said to only read |
get_chains_list | Said to only read |
get_contract_abi | Said to only read |
get_token_transfers_by_address | Said to only read |
get_tokens_by_address | Said to only read |
get_transaction_info | Said to only read |
get_transactions_by_address | Said to only read |
inspect_contract_code | Said to only read |
lookup_token_by_symbol | Said to only read |
nft_tokens_by_address | Said to only read |
read_contract | Said to only read |
The tools the server listed at the last check that passed, at its default address and settings, with no sign-in; an account that signs in, or other settings, may see other tools. What a tool is counted as doing is Stackduke's cautious reading of the server's labels, the tool's name and its description: where they disagree it takes whichever says the tool can do most, so it overcounts on purpose. It does not say the server is safe, and it does not list what a tool cannot do. Descriptions are not shown, because they are written for models and may try to steer them.
Recent checks
12 of the last 12 checks passed
A check passes when the server lists its tools. Checked at https://mcp.blockscout.com/mcp.
Recent changes
No change seen across the last 12 checks that passed.
From the scan of 27 Oct 2026, 01:52 UTC. "Changed" and "Can do more" count changes from the last 30 days; older ones stay listed here. A change made and undone between two checks is not seen. Every check is in the scanner's public data.
Know when Blockscout's tools change.
One email when Blockscout's official MCP server adds, removes or changes tools, with what changed. Nothing else.
What to watch for
- Its direct_api_call tool calls a raw Blockscout API endpoint, and supports POST requests with a JSON body as well as GET. Blockscout's MCP server README
- Blockscout says most data tools need a Blockscout PRO API key, sent in a request header, and fail without one. Blockscout's MCP server README
- Contract source files, token names and public tags written by other people come back to the agent as text, and text an agent reads can carry instructions for it. OWASP, prompt injection
How to limit it
With Blockscout's own settings, as its documentation describes them. Stackduke has not tested them.
- We recommend a PRO API key made only for the agent, from the Blockscout Developer Portal, where Blockscout says the free tier does not require a credit card. Blockscout's MCP server README
What Stackduke is designed to do
Stackduke is designed to sit between your agents and their MCP servers: to check each tool call against your rules before it runs, hold the risky ones for a person to approve, and keep a record of what was decided.
It does not yet forward or block tool calls for customers. Today it reads what this server offers and publishes what changes.