Etherscan
REMOTE · MCP.ETHERSCAN.IO · 2 COMPONENTS
Read-only Etherscan V2 blockchain data: balances, transactions, transfers, tokens, contracts, logs.
Available components
Last scanned (9 hours ago)
Scores higher than 18% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Crypto and Web3
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 Security86
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, but returns a challenge with no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- 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 & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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.
- 24 Oct 26 0
- Endpoint reachability: unreachable → behind authorisation ▼ security
- HSTS header: unverified → fail ▼ security
- Authorization: unverified → fail ▼ security
- Transport: fail → unverified ▼ security
- Tool safety: Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools. security
- Capabilities: Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- Tool coverage: Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools. functional
- 23 Oct 26 0
- Endpoint reachability: behind authorisation → unreachable ▼ security
- Transport: unverified → fail ▼ security
- Authorization: fail → unverified ▼ security
- HSTS header: fail → unverified ▼ security
- Tool safety: Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. security
- Tool coverage: Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list. functional
- Schema quality: Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list. functional
- Capabilities: Capabilities not yet verified: we couldn't read the endpoint's capabilities. functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Sept 26 0
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: partial → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 3 Sept 26 0
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: fail → partial ▲ security
- First check of Judged manipulation: pass security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: pass functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Destructive annotations: pass functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Aug 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://mcp.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 | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 4e525730814467f60e56e6fb5466910a |
| 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.etherscan.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| etherscan.io. | present | 2371 | 13 | Verified |
| mcp.etherscan.io. | Verified address RRset verified with the apex keys |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.etherscan.io/mcp | Auth required | 401 | |
| http (plaintext) | http://mcp.etherscan.io/mcp | HTTPS enforced | 301 | https://mcp.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_address_labels Get Address Labels ~83
Get the public nametag, labels and attributes for an address (token type, trust rating, contract name, source-code status, etc.).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Address to look up. |
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). Defaults to server config. |
No output schema declared.
No examples provided.
get_block_by_timestamp Get Block By Timestamp ~85
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). Defaults to server config. |
| closest | string | – | Return closest block before or after. Default before. |
| timestamp | integer | yes | Unix timestamp in seconds. |
No output schema declared.
No examples provided.
get_contract_abi Get Contract Abi ~66
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). Defaults to server config. |
No output schema declared.
No examples provided.
get_contract_creation Get Contract Creation ~76
Get the creator address and creation transaction hash for up to 5 contract addresses.
| Name | Type | Req | Description |
|---|---|---|---|
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). Defaults to server config. |
| contractaddresses | array | yes | List of contract addresses (1-5). |
No output schema declared.
No examples provided.
get_contract_source Get Contract Source ~65
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). Defaults to server config. |
No output schema declared.
No examples provided.
get_funded_by Get Funded By ~75
Get the address that first funded a given address (the source of its initial funds).
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Account address to trace funding for. |
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). Defaults to server config. |
No output schema declared.
No examples provided.
get_gas_oracle Get Gas Oracle ~63
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). Defaults to server config. |
No output schema declared.
No examples provided.
get_internal_transactions Get Internal Transactions ~151
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). Defaults to server config. |
| 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). |
No output schema declared.
No examples provided.
get_logs Get Logs ~302
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). Defaults to server config. |
| 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 | – | – | Topic 1 (first indexed argument). |
| topic1_2_opr | – | – | Combine topic1 and topic2: and | or. |
| topic2 | – | – | Topic 2 (second indexed argument). |
| topic2_3_opr | – | – | Combine topic2 and topic3: and | or. |
| topic3 | – | – | Topic 3 (third indexed argument). |
No output schema declared.
No examples provided.
get_native_balance Get Native Balance ~85
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). Defaults to server config. |
| tag | string | – | Block tag. Default latest. |
No output schema declared.
No examples provided.
get_supported_chains Get Supported Chains ~23
Get the list of chains / chain IDs supported by the API.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_token_balances Get Token Balances ~114
Get the ERC-20 tokens held by an address, with human-readable quantities and USD values. Tokens with no USD price are filtered out.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Account address to query. |
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). Defaults to server config. |
| offset | integer | – | Records per page. Default 100. |
| page | integer | – | Page number (1-based). Default 1. |
No output schema declared.
No examples provided.
get_token_info Get Token Info ~87
Get token project details and social links for a contract: name, symbol, divisor, type, total supply, description, website, socials, price, etc.
| Name | Type | Req | Description |
|---|---|---|---|
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). Defaults to server config. |
| contractaddress | string | yes | Token contract address. |
No output schema declared.
No examples provided.
get_token_top_holders Get Token Top Holders ~101
Get the top holders of an ERC-20 token contract, with each holder's address and quantity.
| Name | Type | Req | Description |
|---|---|---|---|
| chainid | string | – | Numeric chain id (e.g. 1=Ethereum, 56=BNB, 137=Polygon). Defaults to server config. |
| contractaddress | string | yes | ERC-20 token contract address. |
| limit | integer | – | Number of holders to return (1-1000). Default 10. |
No output schema declared.
No examples provided.
get_token_transfers Get Token Transfers ~195
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). Defaults to server config. |
| contractaddress | – | – | 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. |
No output schema declared.
No examples provided.
get_transaction_by_hash Get Transaction By Hash ~96
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). Defaults to server config. |
| txhash | string | yes | Transaction hash. |
No output schema declared.
No examples provided.
get_transaction_receipt Get Transaction Receipt ~102
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). Defaults to server config. |
| txhash | string | yes | Transaction hash. |
No output schema declared.
No examples provided.
get_transaction_receipt_status Get Transaction Receipt Status ~80
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). Defaults to server config. |
| txhash | string | yes | Transaction hash. |
No output schema declared.
No examples provided.
get_transaction_status Get Transaction Status ~70
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). Defaults to server config. |
| txhash | string | yes | Transaction hash. |
No output schema declared.
No examples provided.
get_transactions Get Transactions ~128
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). Defaults to server config. |
| 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. |
No output schema declared.
No examples provided.
How do I install the Etherscan MCP server?
Etherscan is a hosted endpoint at https://mcp.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.etherscan.io
claude mcp add --transport http io-etherscan-etherscan-mcp 'https://mcp.etherscan.io/mcp'
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.etherscan.io/mcp).
Is the Etherscan MCP server safe to use?
Etherscan scores 34 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 20 tools: get_native_balance, get_transactions, get_internal_transactions, get_token_transfers, get_token_balances, and 15 more. Their descriptions and schemas cost roughly 2,047 tokens of context every time the server is loaded.
Does the Etherscan MCP server require authentication?
Yes. Etherscan asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Etherscan MCP server still maintained?
Etherscan is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.