
Gives Claude access to Etherscan's blockchain explorer API across multiple chains. You get three core tools: check ERC-20 token balances for any address, pull verified contract ABIs as JSON, and fetch full contract source code with compiler settings and license info. Runs through Pipeworx's gateway, which means you can either connect to just Etherscan or hook into their full suite of 250+ data sources. The ask_pipeworx tool lets you query in plain English instead of calling individual methods. Useful when you're building blockchain analytics workflows, auditing smart contracts, or need to inspect on-chain data without leaving your AI chat interface.
Public tool metadata for what this MCP can expose to an agent.
check-balanceCheck the ETH balance of an Ethereum address1 paramsCheck the ETH balance of an Ethereum address
addressstringget-transactionsGet recent transactions for an Ethereum address2 paramsGet recent transactions for an Ethereum address
addressstringlimitnumberget-token-transfersGet ERC20 token transfers for an Ethereum address2 paramsGet ERC20 token transfers for an Ethereum address
addressstringlimitnumberget-contract-abiGet the ABI for a smart contract1 paramsGet the ABI for a smart contract
addressstringget-contract-codeGet the source code for a smart contract1 paramsGet the source code for a smart contract
addressstringget-gas-pricesGet current gas prices in GweiGet current gas prices in Gwei
No parameter schema in public metadata yet.
get-ens-nameGet the ENS name for an Ethereum address1 paramsGet the ENS name for an Ethereum address
addressstringEtherscan V2 MCP — multichain (50+ EVM chains) block-explorer access.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
get_balance(address, chain?) — native-token balance.get_token_balance(address, contract_address, chain?) — ERC-20 balance.list_transactions(address, type?, chain?, ...) — normal / internal / erc20 / erc721 / erc1155.get_contract_abi(address, chain?) — verified ABI.get_contract_source(address, chain?) — verified source + metadata.PLATFORM_ETHERSCAN_KEY.?_apiKey=<key> after registering at https://etherscan.io/apis (free 100k/day, 5 req/sec).https://api.etherscan.io/v2/api — single key works across all supported chains via chainid param.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"etherscan": {
"url": "https://gateway.pipeworx.io/etherscan/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/etherscan/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Etherscan data" })
The gateway picks the right tool and fills the arguments automatically.
MIT