MCP Etherscan Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Etherscan Server?

MCP Etherscan Server is a server that provides tools for accessing Ethereum blockchain data through Etherscan's API, enabling users to check balances, view transaction history, and more.

how to use MCP Etherscan Server?

To use the MCP Etherscan Server, clone the repository, install dependencies, set up your Etherscan API key, and start the server. You can then interact with it using compatible clients like Claude Desktop.

key features of MCP Etherscan Server?

  • Balance Checking: Get ETH balance for any Ethereum address
  • Transaction History: View recent transactions with detailed information
  • Token Transfers: Track ERC20 token transfers with token details
  • Contract ABI: Fetch smart contract ABIs for development
  • Gas Prices: Monitor current gas prices (Safe Low, Standard, Fast)
  • ENS Resolution: Resolve Ethereum addresses to ENS names

use cases of MCP Etherscan Server?

  1. Checking the ETH balance of any address
  2. Viewing transaction history for auditing purposes
  3. Tracking ERC20 token transfers for investment analysis
  4. Fetching contract ABIs for smart contract development
  5. Monitoring gas prices for transaction optimization

FAQ from MCP Etherscan Server?

  • Do I need an API key to use this server?

Yes, you need an Etherscan API key to access the features.

  • Can I use this server with any client?

Yes, it is designed to work with MCP-compatible clients like Claude Desktop.

  • Is there a limit to the number of requests I can make?

The limits depend on your Etherscan API key plan.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago