How to Use the Arbiscan (Arbitrum Explorer) MCP in LlamaIndex

Q: Can I use Arbiscan (Arbitrum Explorer) with LlamaIndex RAG pipelines?

Yes. The output from tools like gettokentx can be vectorized and stored. This lets your agent perform retrieval-augmented generation over actual transaction histories.

Index live Arbitrum ledger data into your LlamaIndex knowledge base for semantic search.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Arbiscan (Arbitrum Explorer) MCP to LlamaIndex

Create your Vinkius account to connect Arbiscan (Arbitrum Explorer) to LlamaIndex and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Arbiscan (Arbitrum Explorer) with LlamaIndex

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Turn on-chain data into searchable knowledge

`get_source_code` is an MCP tool that fetches verified smart contract source code from Arbitrum. LlamaIndex indexes this code directly into your vector database, making complex solidity logic searchable via natural language queries. Instead of reading raw code, you query your index to find specific functions. Your agent uses this indexed data to explain contract mechanics without querying the API twice.

Build RAG pipelines for Arbitrum transaction logs

`get_logs` is an MCP tool that retrieves event logs from the Arbitrum blockchain. LlamaIndex takes these raw events, structures them, and embeds them into your local index so your agent can answer questions about past smart contract events. This prevents the agent from hallucinating transaction histories. It grounds every answer in the actual log data pulled from the network.

Query token metrics using LlamaIndex

`get_eth_supply` is an MCP tool that checks the total supply of Ether on the Arbitrum network. Your LlamaIndex agent combines this with `get_eth_price` to build a live financial profile of the chain. The framework indexes these metrics over time. You get a historical record of price and supply changes that your agent can analyze semantically.

Setup guide

Set up Arbiscan (Arbitrum Explorer) MCP in LlamaIndex

Prerequisites

Python 3.10+ installed
llama-index-tools-mcp package
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install llama-index-tools-mcp llama-index-llms-openai. The MCP tools package provides BasicMCPClient and McpToolSpec.
2

Connect with BasicMCPClient
Point BasicMCPClient to your Vinkius endpoint URL. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. Supports SSE and Streamable HTTP transports.
3

Convert to LlamaIndex tools
Call mcp_tool_spec.to_tool_list_async() to convert all Arbiscan (Arbitrum Explorer) MCP tools into native FunctionTool objects that any LlamaIndex agent can use.
4

Run with any LLM
Create a FunctionAgent with the tools and your preferred LLM. Swap OpenAI for Anthropic, Gemini, or any LlamaIndex-supported provider.

agent.py

from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

# Connect to the MCP
mcp_client = BasicMCPClient(
    "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)
mcp_tool_spec = McpToolSpec(client=mcp_client)

# Convert MCP tools to LlamaIndex tools
tools = await mcp_tool_spec.to_tool_list_async()

# Create and run the agent
agent = FunctionAgent(
    tools=tools,
    llm=OpenAI(model="gpt-4o"),
    system_prompt="You have access to Arbiscan (Arbitrum Explorer) tools.",
)
response = await agent.run("List recent Arbiscan (Arbitrum Explorer) data")

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Arbiscan. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Arbiscan (Arbitrum Explorer) now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Arbiscan (Arbitrum Explorer) MCP in LlamaIndex

Use the LlamaIndex MCP tool spec to pull the tools into your agent. Once the tool returns data, you can load it into a document object and index it.

Yes. The output from tools like `get_token_tx` can be vectorized and stored. This lets your agent perform retrieval-augmented generation over actual transaction histories.

Yes, you can load the tools asynchronously. This is useful when fetching data from multiple endpoints like `get_balance_multi` or checking block countdowns with `get_block_countdown`.

You can pass an allowed tools list when initializing the MCP tool spec. This lets you restrict your agent to read-only tools like `get_balance` if you want to avoid execution tools.

Yes, Vinkius executes this MCP Server in a zero-trust, ephemeral sandbox. The contract ABIs and transaction lists fetched from Arbiscan are processed in memory and never written to persistent disk storage on the hosting platform.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript