Skip to main content
Glama

Etherscan

by io.etherscan
OverviewDiscussionsAdmin

Server Details

Read-only Etherscan V2 blockchain data: balances, transactions, transfers, tokens, contracts, logs.

Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
5.0% over 41 days
Last Tested
Transport
Streamable HTTP
URL

TDQS

A3.7/5.0

Scored across 20 tools

Disambiguation4/5

Most tools target clearly distinct data types: balances, transactions, logs, contracts, tokens, gas, and chains. The main confusion risk is between get_transaction_status, get_transaction_receipt_status, and get_transaction_receipt, which all relate to transaction outcomes and could be easily misselected.

Naming Consistency5/5

Every tool follows the get_<object> or get_<object>_<qualifier> snake_case pattern. The naming is highly predictable and makes the tool purpose evident from the name alone.

Tool Count3/5

20 tools is on the heavier side, approaching the upper bound for a coherent MCP server. However, given Etherscan's broad read-only domain—addresses, transactions, contracts, tokens, logs, and gas—the count is defensible even if it feels somewhat large.

Completeness4/5

The toolset covers the major Etherscan data-access patterns: balances, normal/internal transactions, receipts, token transfers, contract ABI/source/creation, logs, and gas. Obvious gaps like fetching a block by number/hash or listing transactions within a block are missing, but agents can accomplish most explorer workflows.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 20 tool updates
    • First observedget_address_labels
    • First observedget_block_by_timestamp
    • First observedget_contract_abi
    • First observedget_contract_creation
    • First observedget_contract_source
    • First observedget_funded_by
    • First observedget_gas_oracle
    • First observedget_internal_transactions
    • First observedget_logs
    • First observedget_native_balance
    • First observedget_supported_chains
    • First observedget_token_balances
    • First observedget_token_info
    • First observedget_token_top_holders
    • First observedget_token_transfers
    • First observedget_transaction_by_hash
    • First observedget_transaction_receipt
    • First observedget_transaction_receipt_status
    • First observedget_transaction_status
    • First observedget_transactions

Related MCP Connectors

Related MCP Servers

Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources