Is the Blockscout MCP server down?

mcp-registry/com.blockscout/mcp-server · v1.26.0

Compare: vs Sturs49 Cryptotaxedge MCP server · vs Emercoin Agent MCP server · vs Cabalspy Wallet Tracker MCP server · vs Maddegen Agent Synapse Risk MCP server

As of 2026-10-26 22:34 UTC, the Blockscout MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 3 minutes.

MCP server for Blockscout

claude mcp add --transport http blockscout-mcp-server https://mcp.blockscout.com/mcp

{
  "mcpServers": {
    "blockscout-mcp-server": {
      "type": "http",
      "url": "https://mcp.blockscout.com/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: A (100/100)

No problems found.

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/com.blockscout/mcp-server"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/com.blockscout/mcp-server"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• Every tool declares whether it is read-only or destructive.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~5,057 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 99.98% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• read_contract ~600 tokens
• get_transactions_by_address ~524 tokens
• direct_api_call ~515 tokens
• get_token_transfers_by_address ~453 tokens
• get_transaction_info ~329 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blockscout%2Fmcp-server.svg)](https://glimind.com/server/mcp-registry%2Fcom.blockscout%2Fmcp-server?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fcom.blockscout%2Fmcp-server?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blockscout%2Fmcp-server.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fcom.blockscout%2Fmcp-server.svg
   :target: https://glimind.com/server/mcp-registry%2Fcom.blockscout%2Fmcp-server?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:78f00da95575f786…, first seen 2026-10-17, included at leaf 2988 of 75,857. Version history · verify what your client received.

Tools (25)

• __unlock_blockchain_analysis__
• direct_api_call
• get_address_by_ens_name
• get_address_info
• get_balance
• get_block
• get_block_info
• get_block_number
• get_chains_list
• get_contract_abi
• get_contract_metadata
• get_nft_info
• get_nfts
• get_token_balances
• get_token_info
• get_token_transfers_by_address
• get_tokens_by_address
• get_transaction
• get_transaction_info
• get_transactions_by_address
• inspect_contract_code
• lookup_token_by_symbol
• nft_tokens_by_address
• read_contract
• search

Compare: most reliable other servers · most reliable web3 servers · most reliable blockchain servers · most reliable finance servers · most reliable data servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Blockscout MCP server down right now?

As of 2026-10-26 22:34 UTC, the Blockscout MCP server is up with a Glimind reliability score of 96/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks. It had 5 outages in 90 days, with a median recovery of 3 minutes.

How many tools does Blockscout MCP server provide?

Blockscout MCP server advertises 25 tools, including __unlock_blockchain_analysis__, direct_api_call, get_address_by_ens_name, get_address_info, get_balance.

How do I install Blockscout MCP server?

Point your MCP client at this streamable-http endpoint: https://mcp.blockscout.com/mcp

Is the Blockscout MCP server safe to connect to an AI agent?

Glimind scanned all 16 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Blockscout MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.