render_etherscan_widget — Etherscan MCP Tool
render_etherscan_widget
(render etherscan widget) is one of 16 tools on the
Etherscan
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call render_etherscan_widget from your client
- Claude Code Etherscan render_etherscan_widget run in your project directory
- Claude Desktop Etherscan render_etherscan_widget ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Etherscan render_etherscan_widget ~/.cursor/mcp.json
- VS Code Etherscan render_etherscan_widget .vscode/mcp.json
- Zed Etherscan render_etherscan_widget ~/.config/zed/settings.json
- Windsurf Etherscan render_etherscan_widget ~/.codeium/windsurf/mcp_config.json
- Cline Etherscan render_etherscan_widget ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Etherscan render_etherscan_widget ~/.gemini/settings.json
- Grok Etherscan render_etherscan_widget .mcp.json (in your project root)
- ChatGPT Etherscan render_etherscan_widget Settings → Connectors → Advanced → Developer mode
- Claude.ai Etherscan render_etherscan_widget Settings → Connectors → Add custom connector
- LangChain Etherscan render_etherscan_widget pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http etherscan-mcp https://mcp-keyless.etherscan.io/mcpOther tools on this server
- get_native_balance
- get_transactions
- get_internal_transactions
- get_token_transfers
- get_contract_source
- get_contract_abi
- get_contract_creation
- get_transaction_receipt_status
- get_transaction_status
- get_gas_oracle
- get_block_by_timestamp
- get_supported_chains
- get_logs
- get_transaction_by_hash
- get_transaction_receipt
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.