4,000+ servers built on vurb.ts
Vinkius
CrewAIFramework
The Graph (Web3 Indexing) MCP Server

Bring Web3
to CrewAI

Learn how to connect The Graph (Web3 Indexing) to CrewAI and start using 8 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 Evm Historical BalancesGet Evm HoldersGet Evm SwapsGet Evm TransfersGet Svm HoldersGet Svm SwapsGet Svm TransfersQuery Subgraph

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
The Graph (Web3 Indexing)

What is the The Graph (Web3 Indexing) MCP Server?

Connect to The Graph to index and retrieve real-time blockchain data across multiple ecosystems. This MCP server allows your AI agent to query decentralized data from Ethereum, Polygon, Solana, and more through standardized tools and custom GraphQL subgraphs.

What you can do

  • EVM Data Access — Retrieve token transfers, top holders, and DEX swap events (Uniswap, Curve) for any EVM-compatible chain.
  • Solana (SVM) Integration — Fetch SPL token transfers, holders, and AMM swaps (Jupiter, Raydium) directly from the Solana network.
  • Historical Analysis — Access wallet balance changes in OHLCV format to track portfolio performance over time.
  • Custom Subgraph Queries — Execute raw GraphQL queries against any specific subgraph ID for deep, specialized data extraction.
  • Market Intelligence — Monitor liquidity pool activities and token distribution metrics without manual block explorer searching.

How it works

  1. Subscribe to this server
  2. Enter your The Graph API Token, API URL, and optional API Key
  3. Start querying on-chain data from Claude, Cursor, or any MCP-compatible client

Who is this for?

  • Web3 Developers — debug smart contract events and verify on-chain state directly from your IDE
  • Data Analysts — aggregate token holder distributions and DEX volume metrics for research
  • DeFi Power Users — track wallet movements and liquidity pool swaps through natural language

Built-in capabilities (8)

get_evm_historical_balances

Get EVM historical balances

get_evm_holders

Get EVM token holders

get_evm_swaps

) for EVM chains. Get EVM DEX swaps

get_evm_transfers

Get EVM token transfers

get_svm_holders

Get SVM (Solana) token holders

get_svm_swaps

) for Solana. Get SVM (Solana) DEX swaps

get_svm_transfers

Get SVM (Solana) token transfers

query_subgraph

Requires THE_GRAPH_API_KEY. Query a subgraph using GraphQL

Why CrewAI?

When paired with CrewAI, The Graph (Web3 Indexing) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call The Graph (Web3 Indexing) 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

The Graph (Web3 Indexing) in CrewAI

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

The Graph (Web3 Indexing) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect The Graph (Web3 Indexing) 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 The Graph (Web3 Indexing) in CrewAI

The The Graph (Web3 Indexing) 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 8 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.

The Graph (Web3 Indexing)
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 The Graph (Web3 Indexing) for CrewAI

Every tool call from CrewAI to the The Graph (Web3 Indexing) 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 query any specific subgraph if I have its ID?

Yes! Use the query_subgraph tool by providing the subgraph_id and your GraphQL query string. This allows for deep, custom data extraction beyond the standard tools.

02

Does this server support Solana token data?

Absolutely. You can use get_svm_transfers, get_svm_holders, and get_svm_swaps to interact with SPL tokens and decentralized exchanges on the Solana network.

03

Can I track historical balance changes for a specific wallet?

Yes, the get_evm_historical_balances tool provides historical balance data in OHLCV format for EVM chains, making it easy to analyze portfolio trends.

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 →