No user-submitted related servers found.
Scored across 16 tools
Several tools overlap: address_overview and native_balance both return native balance, address_history_page and scan_address_transactions both traverse address transactions, and contract_logs/decode_event_logs/historical_availability all touch logs or historical state. Descriptions add caveats and pinned-block distinctions, but an agent must read carefully to choose correctly.
All names use snake_case, which is consistent, but the convention is split between noun phrases (chain_status, block_details, token_info) and verb phrases (read_contract, decode_event_logs, scan_address_transactions). The mixed style remains readable but is not a single predictable pattern.
16 tools is slightly above the typical 3-15 range but reasonable for a read-only chain inspection and analysis surface. Each tool maps to a specific query type, though a few overlaps suggest some could be consolidated.
The surface covers core read-only chain workflows: status, blocks, transactions, addresses, contracts, logs, tokens, NFTs, validators, supply reconciliation, and historical probes. Minor gaps remain around gas estimation, broad event/topic filtering, and richer token/NFT enumeration, but no major dead ends for the stated purpose.
