Etherscan

Look up wallets, transactions, contracts, logs and gas across EVM chains from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Etherscan connector does

The Etherscan MCP server connects Claude to Etherscan's block-explorer data across the EVM chains the Etherscan API V2 supports. The keyless server in Claude's directory exposes 17 read-only tools for balances, transactions, token transfers, verified contracts, event logs, blocks and gas prices. It needs no account or API key, and nothing it does signs or sends a transaction.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Etherscan tools (17)

  • get_native_balanceRead-only

    Get the native coin (e.g. ETH) balance of an address, in wei.

  • get_transactionsRead-only

    Get the list of normal (external) transactions for an address.

  • get_internal_transactionsRead-only

    Get internal transactions for an address, or by a specific parent transaction hash.

  • get_token_transfersRead-only

    Get token transfer events for an address, optionally filtered by token contract. Select the token standard: erc20 (fungible, default), erc721 (NFT), or erc1155 (multi-token).

  • resolve_ens_nameRead-only

    Resolve an ENS name (or onchain subdomain, e.g. etherscan.eth or gm.etherscan.eth) to its Ethereum address. Ethereum mainnet only. Offchain names that require CCIP Read / wildcard resolution (e.g. *.base.eth) are not supported. A name that does not resolve returns ok:true with a null result.

  • get_contract_sourceRead-only

    Get the verified source code and metadata for a contract address.

  • get_contract_abiRead-only

    Get the verified ABI (JSON) for a contract address.

  • get_contract_creationRead-only

    Get the creator address and creation transaction hash for up to 5 contract addresses. The multi-kilobyte creation bytecode is omitted by default to keep responses small; set include_creation_bytecode=true to include it.

  • get_transaction_receipt_statusRead-only

    Get the receipt status of a transaction (1 = success, 0 = failed). Post-Byzantium only.

  • get_transaction_statusRead-only

    Get the contract execution status of a transaction (detects failed/erroring executions).

  • get_gas_oracleRead-only

    Get current gas price recommendations (safe / propose / fast) from the gas tracker.

  • get_block_by_timestampRead-only

    Get the block number closest to a given Unix timestamp (seconds).

  • get_supported_chainsRead-only

    Get the chains / chain IDs supported by the Etherscan V2 API. In the hosted (proxy) deployment this returns a bundled snapshot shipped with the server, refreshed when the package is updated; in direct/stdio mode it queries the live chain-list endpoint. A chain's absence from the returned list is not proof that it lacks live support.

  • get_logsRead-only

    Search event logs by contract address and/or topics over a block range. Topics are 32-byte hex values; topic0 is usually the keccak256 event-signature hash. Adjacent-topic operators (and/or) combine multiple topic filters. Provide 'address' and/or at least one topic.

  • get_transaction_by_hashRead-only

    Get the full transaction object for a transaction hash (from, to, value, input data, gas, gas price, nonce, block number/hash, transaction index). Returns null if the hash is unknown.

  • get_transaction_receiptRead-only

    Get the transaction receipt for a transaction hash (execution status, gas used, cumulative gas used, effective gas price, logs, and the created contract address for deployments). Returns null if the hash is unknown or the transaction is still pending.

  • render_etherscan_widgetRead-only

    Present exact facts returned by Etherscan data tools in a fast explorer-style card. Call the relevant Etherscan data tool first and copy only supported values into this tool. Never invent scores, risk labels, historical prices, forecasts, or audit conclusions.

Read from the server on 2026-11-18, including each tool's own safety annotations.

Limits

  • Read-only by design. It cannot sign, broadcast, verify a contract or manage keys. Acting on what you find happens in your own wallet.
  • Keyless rate limits are unpublished. Etherscan says the keyless server is rate limited separately from API plans, without giving a number.
  • No PRO data. Token holdings with USD values, token info, top holders, funding source and labels need the authenticated server.
  • The chain list can lag. get_supported_chains says that on the hosted server it returns a bundled snapshot, and that a chain missing from it is not proof it lacks live support.
  • ENS is mainnet only. resolve_ens_name does not resolve offchain names that need CCIP Read or wildcard resolution, such as names under base.eth.
  • Prompt injection. Etherscan advises enabling your client's confirmation prompts and taking care when combining Etherscan with other connectors in one chat. Onchain data such as token names is written by anyone.

Frequently asked questions

Do you need an Etherscan API key to use the connector in Claude?

No. The connector in Claude's directory points at Etherscan's keyless server, which Etherscan documents as needing no API key and no account. We confirmed it on 2026-11-18: an anonymous handshake returned all 17 tools with no credential. A key matters only if you want Etherscan's separate authenticated server, which adds the PRO tools and uses your API plan's limits.

Can the Etherscan connector send a transaction or move funds?

No. Etherscan's documentation says every tool reads public onchain data and nothing signs or sends a transaction. The server's own instructions say the tools cannot sign or broadcast transactions, verify contracts, manage API keys or modify state, and every one of the 17 tools is annotated read-only. It has no wallet, no private key and no write path.

Why are token holdings and address labels missing?

Because those are PRO tools, and the keyless server leaves them out. Etherscan lists five tools that only its authenticated server carries: token balances with USD values, token info, top holders, the address that first funded a wallet, and Etherscan name tags and labels. Name tags need the Pro Plus API plan. To use them, connect the authenticated server with your own API key instead.

Which blockchains does the Etherscan connector cover?

Every chain the Etherscan API V2 supports, through one connection. You name the chain in your question, such as Base or Arbitrum, and the agent passes the matching chain ID. Etherscan's own documentation says 50+ chains, while Anthropic's directory listing says 60+. The get_supported_chains tool returns the current list, though on the hosted server it is a bundled snapshot.

Sources

Use it in an agent

Put Etherscan to work.

Connect Etherscan once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.