Etherscan
REMOTE · MCP-KEYLESS.ETHERSCAN.IO · 2 COMPONENTS · SCANNED SEP 20
Read-only Etherscan V2 blockchain data: balances, transactions, transfers, tokens, contracts, logs.
Available components
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. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 16 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
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.
remote · mcp-keyless.etherscan.io
claude mcp add --transport http io-etherscan-etherscan-mcp 'https://mcp-keyless.etherscan.io/mcp'
{
"mcpServers": {
"io-etherscan-etherscan-mcp": {
"url": "https://mcp-keyless.etherscan.io/mcp"
}
}
} {
"servers": {
"io-etherscan-etherscan-mcp": {
"type": "http",
"url": "https://mcp-keyless.etherscan.io/mcp"
}
}
} [mcp_servers.io-etherscan-etherscan-mcp] url = "https://mcp-keyless.etherscan.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-etherscan-etherscan-mcp": {
"type": "remote",
"url": "https://mcp-keyless.etherscan.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-etherscan-etherscan-mcp --url 'https://mcp-keyless.etherscan.io/mcp' --transport streamable-http
mcp_servers:
io-etherscan-etherscan-mcp:
url: "https://mcp-keyless.etherscan.io/mcp" {
"McpServers": {
"io-etherscan-etherscan-mcp": {
"Transport": "http",
"Url": "https://mcp-keyless.etherscan.io/mcp"
}
}
} assistant mcp add io-etherscan-etherscan-mcp -t streamable-http -u 'https://mcp-keyless.etherscan.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Sept 26 +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.
- 17 Sept 26 +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.
- 15 Sept 26 +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.
- 12 Sept 26 +1
- Tool coverage: 6% → 100% ▲ functional
- Tool “get_transaction_status” now declares an output schema ▲ functional
- Tool “get_transaction_receipt_status” now declares an output schema ▲ functional
- Tool “get_transaction_receipt” now declares an output schema ▲ functional
- Tool “get_transaction_by_hash” now declares an output schema ▲ functional
- Tool “get_token_transfers” now declares an output schema ▲ functional
- Tool “get_supported_chains” now declares an output schema ▲ functional
- Tool “get_native_balance” now declares an output schema ▲ functional
- Tool “get_logs” now declares an output schema ▲ functional
- Tool “get_internal_transactions” now declares an output schema ▲ functional
- Tool “get_gas_oracle” now declares an output schema ▲ functional
- Tool “get_contract_source” now declares an output schema ▲ functional
- Tool “get_contract_creation” now declares an output schema ▲ functional
- Tool “get_contract_abi” now declares an output schema ▲ functional
- Tool “get_block_by_timestamp” now declares an output schema ▲ functional
- Tool “get_transactions” now declares an output schema ▲ functional
- 11 Sept 26 0
- 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 security
- Schema quality: pass → fail ▼ functional
- Schema quality: good → excellent functional
- Server version: 2.3.0 → 2.4.0 functional
- “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” cosmetic
- 10 Sept 26 +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.
- 9 Sept 26 0
- Resource “etherscan-explorer-dashboard” now points somewhere else: ui://etherscan/explorer-dashboard-v5.html → ui://etherscan/explorer-dashboard-v6.html security
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Probed https://mcp-keyless.etherscan.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=etherscan.io | CN=WE1,O=Google Trust Services,C=US | 20 Aug 2026 | 18 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | fd057e985dc6bc83131141d32e828cd8 |
| SANs: etherscan.io, *.etherscan.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp-keyless.etherscan.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| etherscan.io. | present | 2371 | 13 | Verified |
| mcp-keyless.etherscan.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-keyless.etherscan.io/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-keyless.etherscan.io/mcp | HTTPS enforced | 301 | https://mcp-keyless.etherscan.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_block_by_timestamp Get Block By Timestamp ~91
Get the block number closest to a given Unix timestamp (seconds).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Unix timestamp in seconds. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_contract_abi Get Contract Abi ~72
Get the verified ABI (JSON) for a contract address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address. |
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_contract_creation Get Contract Creation ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1). |
| contractaddresses | array | yes | List of contract addresses (1-5). |
| include_creation_bytecode | boolean | – | Include the full contract creation bytecode (several KB per contract). Omitted by default. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_contract_source Get Contract Source ~71
Get the verified source code and metadata for a contract address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Contract address. |
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_gas_oracle Get Gas Oracle ~69
Get current gas price recommendations (safe / propose / fast) from the gas tracker.
| Name | Type | Req | Description |
|---|---|---|---|
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_internal_transactions Get Internal Transactions ~157
Get internal transactions for an address, or by a specific parent transaction hash.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_logs Get Logs ~318
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_native_balance Get Native Balance ~91
Get the native coin (e.g. ETH) balance of an address, in wei.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_supported_chains Get Supported Chains ~80
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_token_transfers Get Token Transfers ~203
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_transaction_by_hash Get Transaction By Hash ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1). |
| txhash | string | yes | Transaction hash. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_transaction_receipt Get Transaction Receipt ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1). |
| txhash | string | yes | Transaction hash. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_transaction_receipt_status Get Transaction Receipt Status ~86
Get the receipt status of a transaction (1 = success, 0 = failed). Post-Byzantium only.
| Name | Type | Req | Description |
|---|---|---|---|
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1). |
| txhash | string | yes | Transaction hash. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_transaction_status Get Transaction Status ~76
Get the contract execution status of a transaction (detects failed/erroring executions).
| Name | Type | Req | Description |
|---|---|---|---|
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). If omitted, defaults to Ethereum Mainnet (1). |
| txhash | string | yes | Transaction hash. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
get_transactions Get Transactions ~134
Get the list of normal (external) transactions for an address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | yes | The JSON result returned by the Etherscan data tool. |
No examples provided.
render_etherscan_widget Show Etherscan Result ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| chart | object | – | – |
| explorerUrl | string | – | – |
| footer | string | – | – |
| items | array | – | – |
| metrics | array | – | – |
| sections | array | – | – |
| subtitle | string | – | – |
| title | string | yes | – |
| view | string | yes | The factual Etherscan result category to display. |
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | – |
| chart | object | – | – |
| explorerUrl | string | – | – |
| footer | string | – | – |
| items | array | – | – |
| metrics | array | – | – |
| sections | array | – | – |
| subtitle | string | – | – |
| title | string | yes | – |
| view | string | yes | The factual Etherscan result category to display. |
No examples provided.
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 81 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.