4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
Arbiscan (Arbitrum Explorer) MCP Server

Bring Arbitrum
to CrewAI

Learn how to connect Arbiscan (Arbitrum Explorer) to CrewAI and start using 16 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Get AbiGet BalanceGet Balance MultiGet Block CountdownGet Block RewardGet Eth PriceGet Eth SupplyGet LogsGet Source CodeGet StatusGet Token Nft TxGet Token TxGet Tx ListGet Tx List InternalGet Tx Receipt StatusVerify Source Code

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Arbiscan (Arbitrum Explorer)

What is the Arbiscan (Arbitrum Explorer) MCP Server?

Connect your AI agent to Arbiscan to query the Arbitrum L2 network in real-time. This MCP server allows you to fetch blockchain data without leaving your chat interface or IDE.

What you can do

  • Account Auditing — Check Ether balances for single or multiple addresses simultaneously.
  • Transaction Tracking — Retrieve full history for normal, internal, ERC20, and ERC721 (NFT) transactions.
  • Contract Intelligence — Fetch verified source code and ABIs to understand how dApps operate.
  • Network Insights — Get real-time ETH price on Arbitrum, total supply, and block rewards.
  • Developer Tools — Submit and verify contract source code directly through the API.

How it works

  1. Subscribe to this server
  2. Enter your Arbiscan API Key
  3. Start querying Arbitrum data from Claude, Cursor, or any MCP client

Who is this for?

  • Web3 Developers — Inspect contract ABIs and source code while writing code in your IDE.
  • Crypto Analysts — Track whale movements and token transfers using natural language.
  • Security Researchers — Quickly audit transaction history and internal calls for suspicious activity.

Built-in capabilities (16)

get_abi

Get Contract ABI for Verified Source Codes

get_balance

Get Ether Balance for a Single Address

get_balance_multi

Get Ether Balance for Multiple Addresses

get_block_countdown

Get Estimated Block Countdown Time by BlockNo

get_block_reward

Get Block Rewards by BlockNo

get_eth_price

Get Ether Last Price

get_eth_supply

Get Total Supply of Ether on Arbitrum

get_logs

Get Event Logs

get_source_code

Get Contract Source Code for Verified Source Codes

get_status

Check Contract Execution Status

get_token_nft_tx

Get List of ERC721 Token Transfer Events By Address

get_token_tx

Get List of ERC20 Token Transfer Events By Address

get_tx_list

Get List of Normal Transactions By Address

get_tx_list_internal

Get List of Internal Transactions By Address

get_tx_receipt_status

Check Transaction Receipt Status

verify_source_code

Verify Source Code

Why CrewAI?

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

  • 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

  • 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

  • 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

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

See it in action

Arbiscan (Arbitrum Explorer) in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Arbiscan (Arbitrum Explorer) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Arbiscan (Arbitrum Explorer) to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Arbiscan (Arbitrum Explorer) in CrewAI

The Arbiscan (Arbitrum Explorer) 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. All 16 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Arbiscan (Arbitrum Explorer)
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

The Vinkius Advantage

How Vinkius secures Arbiscan (Arbitrum Explorer) for CrewAI

Every tool call from CrewAI to the Arbiscan (Arbitrum Explorer) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I check the balances of multiple Arbitrum addresses at once?

Yes! Use the get_balance_multi tool and provide a comma-separated list of addresses. The agent will return the Ether balance for each one in a single response.

02

How do I view the source code of a verified smart contract?

Simply provide the contract address to the get_source_code tool. If the contract is verified on Arbiscan, your agent will retrieve the full source code for you to inspect.

03

Can I track NFT (ERC721) transfers for a specific wallet?

Yes, the get_token_nft_tx tool allows you to list ERC721 token transfer events associated with any Arbitrum address, including block numbers and transaction hashes.

04

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.

05

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.

06

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.

07

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.

08

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.

09

MCP tools not discovered

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

10

Agent not using tools

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

11

Timeout errors

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

12

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.

Explore More MCP Servers

View all →