4,000+ servers built on vurb.ts
Vinkius
Unlock for AI Agents
CrewAIFramework
Blockdaemon (Blockchain Infrastructure) MCP Server

Bring Web3
to CrewAI

Learn how to connect Blockdaemon (Blockchain Infrastructure) to CrewAI and start using 4 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 Financial ReportGet UtxosList BlocksList Transactions

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Blockdaemon (Blockchain Infrastructure)

What is the Blockdaemon (Blockchain Infrastructure) MCP Server?

Connect your Blockdaemon account to any AI agent to interact with major blockchain protocols through a single, unified interface. This MCP server leverages the Ubiquity API to provide seamless access to multi-chain data.

What you can do

  • Block Exploration — Retrieve block identifiers and metadata for protocols like Bitcoin, Ethereum, Solana, and Polkadot using list_blocks.
  • Transaction Tracking — Query full transaction histories for specific account addresses across supported networks with list_transactions.
  • UTXO Management — Fetch Unspent Transaction Outputs for UTXO-based chains (Bitcoin, Dogecoin, Litecoin) using get_utxos.
  • Financial Reporting — Generate detailed financial reports for addresses on protocols like Algorand, Stellar, and Tezos via get_financial_report.
  • Multi-Network Support — Switch between mainnet and testnet environments effortlessly for development and auditing.

How it works

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

Who is this for?

  • Web3 Developers — Debug transactions and verify block data without leaving your IDE.
  • Data Analysts — Aggregate financial reports and transaction histories for cross-chain auditing.
  • Crypto Operations — Monitor wallet activity and UTXO sets for treasury management.

Built-in capabilities (4)

get_financial_report

Get a financial report for an address

get_utxos

Get Unspent Transaction Outputs (UTXOs)

list_blocks

Get a list of block identifiers

list_transactions

Get a list of transactions for an address

Why CrewAI?

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

Blockdaemon (Blockchain Infrastructure) in CrewAI

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

Blockdaemon (Blockchain Infrastructure) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Blockdaemon (Blockchain Infrastructure) 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 Blockdaemon (Blockchain Infrastructure) in CrewAI

The Blockdaemon (Blockchain Infrastructure) 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 4 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.

Blockdaemon (Blockchain Infrastructure)
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 Blockdaemon (Blockchain Infrastructure) for CrewAI

Every tool call from CrewAI to the Blockdaemon (Blockchain Infrastructure) 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

Which protocols are supported for financial reports?

The get_financial_report tool currently supports Algorand, Polkadot, Stellar, Tezos, and XRP.

02

Can I filter transactions by date?

Yes, the list_transactions tool allows you to provide 'from' and 'to' Unix timestamps to narrow down your search.

03

How do I check unspent balances for Bitcoin?

Use the get_utxos tool with the 'bitcoin' protocol and the specific wallet address. You can also toggle 'check_mempool' to include unconfirmed transactions.

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 →