blockscout-mcp
Server Details
Blockscout - 56 tools for data, metrics, and on-chain analytics
- Status
- Unhealthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- junct-bot/blockscout-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Average 2.7/5 across 56 of 56 tools scored. Lowest: 1.8/5.
Many tools have overlapping purposes with unclear boundaries, such as multiple address-related tools (e.g., get_address_tokens, get_address_token_balances, get_address_token_transfers) that could confuse agents about which to use for specific queries. While descriptions provide some guidance, the sheer number and similarity in naming (e.g., get_token_transfers vs get_token_token_transfers) create significant ambiguity in tool selection.
Tool names follow a consistent snake_case pattern with a 'get_' prefix for most tools, making them predictable and readable. Minor deviations exist, such as 'health_check' without 'get_' and some tools with specific prefixes like 'celestia_service_', but overall naming is largely uniform across the set.
With 56 tools, this server is excessively large for an MCP server, likely overwhelming agents and causing confusion. While the domain (blockchain explorer) is broad, the tool count feels bloated with many similar or overlapping endpoints, suggesting poor scoping and a need for consolidation or better organization.
The tool set provides comprehensive coverage for a blockchain explorer domain, including endpoints for addresses, blocks, transactions, tokens, NFTs, smart contracts, and indexing status. It supports full CRUD-like operations (though mostly read-only as expected) and includes discovery tools, ensuring agents can access all necessary data without significant gaps.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!