# Etherscan (remote · mcp-keyless.etherscan.io)

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

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.etherscan.io`: 34/100, [markdown](https://verifymcp.io/servers/io-etherscan-etherscan-mcp/mcp.md), [page](https://verifymcp.io/servers/io-etherscan-etherscan-mcp/mcp)
- remote · `mcp-keyless.etherscan.io`: 82/100 (this document), [markdown](https://verifymcp.io/servers/io-etherscan-etherscan-mcp/mcp-keyless.md), [page](https://verifymcp.io/servers/io-etherscan-etherscan-mcp/mcp-keyless)

## Channel facts

- Endpoint: `https://mcp-keyless.etherscan.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `2.3.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1997 tokens (~117/item across 17 items; 16 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 87% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Etherscan MCP server?

Etherscan is a hosted endpoint at https://mcp-keyless.etherscan.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http io-etherscan-etherscan-mcp 'https://mcp-keyless.etherscan.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-etherscan-etherscan-mcp": {
      "url": "https://mcp-keyless.etherscan.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-etherscan-etherscan-mcp": {
      "type": "http",
      "url": "https://mcp-keyless.etherscan.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-etherscan-etherscan-mcp]
url = "https://mcp-keyless.etherscan.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-etherscan-etherscan-mcp": {
      "type": "remote",
      "url": "https://mcp-keyless.etherscan.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-etherscan-etherscan-mcp --url 'https://mcp-keyless.etherscan.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-etherscan-etherscan-mcp:
    url: "https://mcp-keyless.etherscan.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-etherscan-etherscan-mcp": {
      "Transport": "http",
      "Url": "https://mcp-keyless.etherscan.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-etherscan-etherscan-mcp -t streamable-http -u 'https://mcp-keyless.etherscan.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-etherscan-etherscan-mcp": {
      "type": "http",
      "url": "https://mcp-keyless.etherscan.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-21 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 78, +1)

- [functional improvement] Tool coverage: 6% → 100%
- [functional improvement] Tool “get_transaction_receipt_status” now declares an output schema
- [functional improvement] Tool “get_transaction_receipt” now declares an output schema
- [functional improvement] Tool “get_transaction_by_hash” now declares an output schema
- [functional improvement] Tool “get_token_transfers” now declares an output schema
- [functional improvement] Tool “get_supported_chains” now declares an output schema
- [functional improvement] Tool “get_native_balance” now declares an output schema
- [functional improvement] Tool “get_logs” now declares an output schema
- [functional improvement] Tool “get_internal_transactions” now declares an output schema
- [functional improvement] Tool “get_gas_oracle” now declares an output schema
- [functional improvement] Tool “get_contract_source” now declares an output schema
- [functional improvement] Tool “get_contract_creation” now declares an output schema
- [functional improvement] Tool “get_contract_abi” now declares an output schema
- [functional improvement] Tool “get_block_by_timestamp” now declares an output schema
- [functional improvement] Tool “get_transactions” now declares an output schema
- [functional improvement] Tool “get_transaction_status” now declares an output schema

### 2026-09-11 (score 77, 0)

- [security] Tool “get_contract_creation” rewrote its description, which is the text the model reads
- [security] Tool “get_supported_chains” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Schema quality: good → excellent
- [functional] Server version: 2.3.0 → 2.4.0
- [cosmetic] “get_contract_creation” added an optional parameter “include_creation_bytecode”
- [cosmetic] “get_logs” reworded the description of “chainid”
- [cosmetic] “get_block_by_timestamp” reworded the description of “chainid”
- [cosmetic] “get_contract_abi” reworded the description of “chainid”
- [cosmetic] “get_contract_creation” reworded the description of “chainid”
- [cosmetic] “get_contract_source” reworded the description of “chainid”
- [cosmetic] “get_gas_oracle” reworded the description of “chainid”
- [cosmetic] “get_internal_transactions” reworded the description of “chainid”
- [cosmetic] “get_native_balance” reworded the description of “chainid”
- [cosmetic] “get_token_transfers” reworded the description of “chainid”
- [cosmetic] “get_transaction_by_hash” reworded the description of “chainid”
- [cosmetic] “get_transaction_receipt” reworded the description of “chainid”
- [cosmetic] “get_transaction_receipt_status” reworded the description of “chainid”
- [cosmetic] “get_transaction_status” reworded the description of “chainid”
- [cosmetic] “get_transactions” reworded the description of “chainid”

### 2026-09-10 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 76, 0)

- [security] Resource “etherscan-explorer-dashboard” now points somewhere else: ui://etherscan/explorer-dashboard-v5.html → ui://etherscan/explorer-dashboard-v6.html

## MCP tools (16)

### `get_native_balance` (~91 tokens)

Get Native Balance

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

Input parameters:

- `address` (string, required): Account address to query.
- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `tag` (string): Block tag. Default latest.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_transactions` (~134 tokens)

Get Transactions

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

Input parameters:

- `address` (string, required): Account address to query.
- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `endblock` (integer): End block number.
- `offset` (integer): Records per page (max 10000).
- `page` (integer): Page number (1-based).
- `sort` (string): Sort order by block number.
- `startblock` (integer): Start block number.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_internal_transactions` (~157 tokens)

Get Internal Transactions

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

Input parameters:

- `address` (string): Account address (omit if using txhash).
- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `endblock` (integer): End block number.
- `offset` (integer): Records per page (max 10000).
- `page` (integer): Page number (1-based).
- `sort` (string): Sort order by block number.
- `startblock` (integer): Start block number.
- `txhash` (string): Parent transaction hash (omit if using address).

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_token_transfers` (~203 tokens)

Get Token Transfers

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).

Input parameters:

- `address` (string): Account address.
- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `contractaddress` (string): Token contract address to filter by.
- `endblock` (integer): End block number.
- `offset` (integer): Records per page (max 10000).
- `page` (integer): Page number (1-based).
- `sort` (string): Sort order by block number.
- `standard` (string): Token standard: erc20 (default), erc721, or erc1155.
- `startblock` (integer): Start block number.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_contract_source` (~71 tokens)

Get Contract Source

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

Input parameters:

- `address` (string, required): Contract address.
- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_contract_abi` (~72 tokens)

Get Contract Abi

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

Input parameters:

- `address` (string, required): Contract address.
- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_contract_creation` (~138 tokens)

Get Contract Creation

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.

Input parameters:

- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `contractaddresses` (array, required): List of contract addresses (1-5).
- `include_creation_bytecode` (boolean): Include the full contract creation bytecode (several KB per contract). Omitted by default.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_transaction_receipt_status` (~86 tokens)

Get Transaction Receipt Status

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

Input parameters:

- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `txhash` (string, required): Transaction hash.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_transaction_status` (~76 tokens)

Get Transaction Status

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

Input parameters:

- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `txhash` (string, required): Transaction hash.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_gas_oracle` (~69 tokens)

Get Gas Oracle

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

Input parameters:

- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_block_by_timestamp` (~91 tokens)

Get Block By Timestamp

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

Input parameters:

- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `closest` (string): Return closest block before or after. Default before.
- `timestamp` (integer, required): Unix timestamp in seconds.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_supported_chains` (~80 tokens)

Get Supported Chains

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.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_logs` (~318 tokens)

Get Logs

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.

Input parameters:

- `address` (string): Contract address to filter by (optional if filtering by topics).
- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `fromblock`: Start block number, or "latest". Default 0.
- `offset` (integer): Records per page (max 1000).
- `page` (integer): Page number (1-based).
- `toblock`: End block number, or "latest". Default latest.
- `topic0` (string): Topic 0 — usually the keccak256 event-signature hash.
- `topic0_1_opr` (string): Combine topic0 and topic1: and | or.
- `topic1` (string): Topic 1 (first indexed argument).
- `topic1_2_opr` (string): Combine topic1 and topic2: and | or.
- `topic2` (string): Topic 2 (second indexed argument).
- `topic2_3_opr` (string): Combine topic2 and topic3: and | or.
- `topic3` (string): Topic 3 (third indexed argument).

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_transaction_by_hash` (~102 tokens)

Get Transaction By Hash

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.

Input parameters:

- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `txhash` (string, required): Transaction hash.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `get_transaction_receipt` (~108 tokens)

Get Transaction Receipt

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.

Input parameters:

- `chainid` (string): Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1).
- `txhash` (string, required): Transaction hash.

Output parameters:

- `data`: The JSON result returned by the Etherscan data tool.

### `render_etherscan_widget` (~142 tokens)

Show Etherscan Result

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.

Input parameters:

- `chain` (string)
- `chart` (object)
- `explorerUrl` (string)
- `footer` (string)
- `items` (array)
- `metrics` (array)
- `sections` (array)
- `subtitle` (string)
- `title` (string, required)
- `view` (string, required): The factual Etherscan result category to display.

Output parameters:

- `chain` (string)
- `chart` (object)
- `explorerUrl` (string)
- `footer` (string)
- `items` (array)
- `metrics` (array)
- `sections` (array)
- `subtitle` (string)
- `title` (string)
- `view` (string): The factual Etherscan result category to display.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-etherscan-etherscan-mcp/mcp-keyless#diagnostics

## Score history

- 2026-09-21: 82
- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 80
- 2026-09-17: 80
- 2026-09-16: 79
- 2026-09-15: 79
- 2026-09-14: 78
- 2026-09-13: 78
- 2026-09-12: 78
- 2026-09-11: 77
- 2026-09-10: 77
- 2026-09-09: 76
- 2026-09-08: 76
- 2026-09-07: 75
- 2026-09-06: 75
- 2026-09-05: 74
- 2026-09-04: 74

## Common questions

### What is the Etherscan MCP server?

Etherscan is an MCP server listed in the public MCP registry as io.etherscan/etherscan-mcp. Read-only Etherscan V2 blockchain data: balances, transactions, transfers, tokens, contracts, logs. This page covers its hosted endpoint (https://mcp-keyless.etherscan.io/mcp).

### Is the Etherscan MCP server safe to use?

Etherscan scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Etherscan MCP server expose?

Etherscan exposes 16 tools: get_native_balance, get_transactions, get_internal_transactions, get_token_transfers, get_contract_source, and 11 more. Their descriptions and schemas cost roughly 1,938 tokens of context every time the server is loaded.

### Does the Etherscan MCP server require authentication?

No. We connected to Etherscan without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Etherscan MCP server still maintained?

Etherscan is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp-keyless.etherscan.io/mcp
- Website: https://docs.etherscan.io/build-with-ai/mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-etherscan-etherscan-mcp/mcp-keyless.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-etherscan-etherscan-mcp/mcp-keyless.json
- HTML version of this page: https://verifymcp.io/servers/io-etherscan-etherscan-mcp/mcp-keyless