Keyless, read-only BNB Chain and Ethereum data: transactions by hash, tokens with a lookalike check
Scored across 2 tools
get_token and get_transaction target completely different resources (a token contract vs a transaction) with no overlap in inputs or outputs. An agent can select between them unambiguously based on whether it has a contract address or a tx hash.
Both tools follow the same clean get_<noun> verb_noun pattern, using snake_case consistently. The convention is predictable and readable.
Only 2 tools for something branded as an 'explorers' server feels thin; explorers typically expose several lookup surfaces. The two present are reasonable, but the set is under-scoped relative to the apparent domain.
There is no address/balance lookup, no address transaction history, no block lookup, and no token transfer listing, which are core explorer operations. An agent asked to inspect a wallet or gather a token's activity has no tool available and would hit a dead end.
A BNB Chain or Ethereum token contract: name, symbol, decimals, total supply, indexed holder count, and lookalike: the well-known token (e.g. USDT) whose name or symbol it imitates, with that token's real contract. lookalike: null only means no match against a short list of well-known tokens; it is not a safety verdict.
Inputs: chain (required), address (required).
One BNB Chain or Ethereum transaction by hash: from, to, value (wei), gas, status. Recent transactions come from the explorer index; older ones are read from the chain (source says which). pending: true means no receipt yet, and fields the node did not report are null. Logs and decoded calls are not included.
Inputs: hash (required), chain (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Wallet balances, ERC-20, blocks, transactions, receipts, ENS and payment checks, pay per call
Signed BNB Chain reads (balances, tokens, NFTs, prices, TapeOut names) with verifiable receipts
Read-only Etherscan V2 blockchain data: balances, transactions, transfers, tokens, contracts, logs.
Explore blockchain data across addresses, tokens, blocks, and transactions. Investigate any transa…
Add one secure layer between your agents and this server.
