4,000+ servers built on vurb.ts
Vinkius

GetBlock (Web3 RPC Provider) MCP Server for CrewAIGive CrewAI instant access to 26 tools to Btc Analyzepsbt, Btc Createpsbt, Btc Getbestblockhash, and more

MCP Inspector GDPR Free for Subscribers

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

Ask AI about this MCP Server for CrewAI

The GetBlock (Web3 RPC Provider) MCP Server for CrewAI is a standout in the Developer Tools category — giving your AI agent 26 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="GetBlock (Web3 RPC Provider) Specialist",
    goal="Help users interact with GetBlock (Web3 RPC Provider) effectively",
    backstory=(
        "You are an expert at leveraging GetBlock (Web3 RPC Provider) 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 GetBlock (Web3 RPC Provider) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 26 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
GetBlock (Web3 RPC Provider)
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 GetBlock (Web3 RPC Provider) MCP Server

Connect your GetBlock account to any AI agent and interact with dozens of blockchain protocols through natural conversation. GetBlock provides high-performance RPC node access for developers and crypto enthusiasts.

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

  • Multi-Chain Queries — Fetch data from Ethereum, Solana, Bitcoin, and 50+ other supported networks using specialized tools.
  • Account & Balance Tracking — Check native balances and token holdings across different chains (e.g., eth_get_balance, sol_get_balance).
  • Blockchain Inspection — Retrieve block details, transaction receipts, and blockchain metadata (e.g., eth_block_number, btc_get_blockchain_info).
  • Advanced Debugging — Access deep transaction traces and call simulations to analyze smart contract behavior (e.g., debug_trace_transaction).
  • Generic RPC Access — Use the rpc_call tool to execute any JSON-RPC method supported by the GetBlock nodes.

The GetBlock (Web3 RPC Provider) MCP Server exposes 26 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 26 GetBlock (Web3 RPC Provider) tools available for CrewAI

When CrewAI connects to GetBlock (Web3 RPC Provider) through Vinkius, your AI agent gets direct access to every tool listed below — spanning rpc-nodes, web3, blockchain-infrastructure, 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.

btc

Btc analyzepsbt on GetBlock (Web3 RPC Provider)

Analyze and provide information about a PSBT

btc

Btc createpsbt on GetBlock (Web3 RPC Provider)

Create a transaction in the Partially Signed Bitcoin Transaction format

btc

Btc getbestblockhash on GetBlock (Web3 RPC Provider)

Get the hash of the best (tip) block

btc

Btc getblockchaininfo on GetBlock (Web3 RPC Provider)

Get an object containing various state info regarding blockchain processing

btc

Btc getblockcount on GetBlock (Web3 RPC Provider)

Get the number of blocks in the longest blockchain

btc

Btc sendrawtransaction on GetBlock (Web3 RPC Provider)

Submit raw transaction (serialized, hex-encoded) to local node and network

debug

Debug trace block by number on GetBlock (Web3 RPC Provider)

Get traces for all transactions in a block

debug

Debug trace call on GetBlock (Web3 RPC Provider)

Run an eth_call within the context of the given block execution

debug

Debug trace transaction on GetBlock (Web3 RPC Provider)

Get all traces of a given transaction

eth

Eth accounts on GetBlock (Web3 RPC Provider)

Get a list of addresses owned by client

eth

Eth block number on GetBlock (Web3 RPC Provider)

Get the number of the most recent block

eth

Eth call on GetBlock (Web3 RPC Provider)

Execute a new message call immediately without creating a transaction

eth

Eth estimate gas on GetBlock (Web3 RPC Provider)

Estimate gas necessary to allow the transaction to complete

eth

Eth get balance on GetBlock (Web3 RPC Provider)

Get the balance of an Ethereum account

eth

Eth get block by hash on GetBlock (Web3 RPC Provider)

Get information about a block by hash

eth

Eth get block by number on GetBlock (Web3 RPC Provider)

Get information about a block by block number

eth

Eth get code on GetBlock (Web3 RPC Provider)

Get code at a given address

eth

Eth get transaction by hash on GetBlock (Web3 RPC Provider)

Get information about a transaction by hash

eth

Eth get transaction receipt on GetBlock (Web3 RPC Provider)

Get the receipt of a transaction by hash

rpc

Rpc call on GetBlock (Web3 RPC Provider)

Execute any generic JSON-RPC method via GetBlock

sol

Sol get account info on GetBlock (Web3 RPC Provider)

Get all information associated with the account of provided Pubkey

sol

Sol get balance on GetBlock (Web3 RPC Provider)

Get the balance of the provided Pubkey

sol

Sol get latest blockhash on GetBlock (Web3 RPC Provider)

Get the latest blockhash from the ledger

sol

Sol get token account balance on GetBlock (Web3 RPC Provider)

Get the token balance of an SPL Token account

sol

Sol get transaction on GetBlock (Web3 RPC Provider)

Get transaction details for a confirmed transaction signature

sol

Sol send transaction on GetBlock (Web3 RPC Provider)

Submit a signed transaction to the cluster for processing

Connect GetBlock (Web3 RPC Provider) to CrewAI via MCP

Follow these steps to wire GetBlock (Web3 RPC Provider) 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 26 tools from GetBlock (Web3 RPC Provider)

Why Use CrewAI with the GetBlock (Web3 RPC Provider) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with GetBlock (Web3 RPC Provider) 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

GetBlock (Web3 RPC Provider) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the GetBlock (Web3 RPC Provider) MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries GetBlock (Web3 RPC Provider) 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 GetBlock (Web3 RPC Provider), analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain GetBlock (Web3 RPC Provider) 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 GetBlock (Web3 RPC Provider) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for GetBlock (Web3 RPC Provider) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with GetBlock (Web3 RPC Provider) immediately.

01

"What is the current Ethereum block height?"

02

"Check the ETH balance for address 0x742d35Cc6634C0532925a3b844Bc454e4438f44e."

03

"Get the latest Bitcoin blockchain info."

Troubleshooting GetBlock (Web3 RPC Provider) MCP Server with CrewAI

Common issues when connecting GetBlock (Web3 RPC Provider) 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.

GetBlock (Web3 RPC Provider) + CrewAI FAQ

Common questions about integrating GetBlock (Web3 RPC Provider) 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 →