4,000+ servers built on vurb.ts
Vinkius

Etherscan MCP Server for CrewAIGive CrewAI instant access to 19 tools to Get Abi, Get Address Tag, Get Address Token Balance, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Etherscan through Vinkius, pass the Edge URL in the `mcps` parameter and every Etherscan tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Etherscan MCP Server for CrewAI is a standout in the Data Analytics category — giving your AI agent 19 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Etherscan Specialist",
    goal="Help users interact with Etherscan effectively",
    backstory=(
        "You are an expert at leveraging Etherscan tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Etherscan "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 19 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Etherscan
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Etherscan MCP Server

Connect your Etherscan API key to any AI agent and gain instant access to on-chain data across Ethereum and other EVM-compatible networks through natural conversation.

When paired with CrewAI, Etherscan becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Etherscan tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Native Balances — Retrieve the native token balance (ETH, MATIC, etc.) for single or multiple addresses (up to 20) using get_balance and get_balance_multi.
  • Transaction History — Fetch comprehensive lists of normal and internal transactions for any wallet address with get_tx_list and get_tx_list_internal.
  • Token Tracking — Monitor transfers for ERC-20, ERC-721 (NFTs), and ERC-1155 tokens using specialized tools like get_token_tx and get_token_nft_tx.
  • Multi-Chain Support — Query data across different networks by specifying the chainid (e.g., 1 for Ethereum, 137 for Polygon).
  • Granular Filtering — Filter transaction results by block range, pagination, and sort order to find exactly what you need.

The Etherscan MCP Server exposes 19 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 19 Etherscan tools available for CrewAI

When CrewAI connects to Etherscan through Vinkius, your AI agent gets direct access to every tool listed below — spanning ethereum, evm, block-explorer, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

get

Get abi on Etherscan

Get Contract ABI

get

Get address tag on Etherscan

Get address name tag (PRO Plus)

get

Get address token balance on Etherscan

Get address portfolio (PRO)

get

Get balance on Etherscan

Get native token balance for an address

get

Get balance multi on Etherscan

Get native token balances for multiple addresses

get

Get block no by time on Etherscan

Get block number by timestamp

get

Get block number on Etherscan

Get latest block number

get

Get eth price on Etherscan

Get Ether last price

get

Get eth supply on Etherscan

Get total supply of Ether

get

Get gas oracle on Etherscan

Get Gas Oracle

get

Get logs on Etherscan

Get event logs

get

Get source code on Etherscan

Get Contract Source Code

get

Get token 1155 tx on Etherscan

Get ERC-1155 token transfers for an address

get

Get token nft tx on Etherscan

Get ERC-721 token transfers for an address

get

Get token tx on Etherscan

Get ERC-20 token transfers for an address

get

Get transaction by hash on Etherscan

Get transaction by hash

get

Get tx list on Etherscan

Max 10,000 records. Get normal transactions for an address

get

Get tx list internal on Etherscan

Get internal transactions for an address

verify

Verify source code on Etherscan

Verify Contract Source Code

Connect Etherscan to CrewAI via MCP

Follow these steps to wire Etherscan into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 19 tools from Etherscan

Why Use CrewAI with the Etherscan MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Etherscan through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Etherscan + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Etherscan MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Etherscan for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Etherscan, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Etherscan tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Etherscan against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Etherscan in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Etherscan immediately.

01

"What is the ETH balance of address 0xde0B295669a9FD93d5F28D9Ec85E40f4cb697BAe on Ethereum?"

02

"Show me the last 5 ERC-20 token transfers for 0x742d35Cc6634C0532925a3b844Bc454e4438f44e."

03

"List the normal transactions for address 0x123... on Polygon (Chain ID 137)."

Troubleshooting Etherscan MCP Server with CrewAI

Common issues when connecting Etherscan to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Etherscan + CrewAI FAQ

Common questions about integrating Etherscan MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Explore More MCP Servers

View all →