CrewAIFramework

GetBlock (Web3 RPC Provider) MCP Server

Bring Rpc Nodes
to CrewAI

Name: GetBlock (Web3 RPC Provider) MCP Server
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

Learn how to connect GetBlock (Web3 RPC Provider) to CrewAI and start using 26 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Btc AnalyzepsbtBtc CreatepsbtBtc GetbestblockhashBtc GetblockchaininfoBtc GetblockcountBtc SendrawtransactionDebug Trace Block By NumberDebug Trace CallDebug Trace TransactionEth AccountsEth Block NumberEth CallEth Estimate GasEth Get BalanceEth Get Block By HashEth Get Block By NumberEth Get CodeEth Get Transaction By HashEth Get Transaction ReceiptRpc CallSol Get Account InfoSol Get BalanceSol Get Latest BlockhashSol Get Token Account BalanceSol Get TransactionSol Send Transaction

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the 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.

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.

How it works

Subscribe to this server
Enter your GetBlock Access Token (API Key)
Start querying blockchain data from Claude, Cursor, or any MCP-compatible client

Who is this for?

Web3 Developers — debug transactions and check contract states without leaving your code editor.
Crypto Analysts — pull real-time on-chain data and block statistics for reporting and research.
DeFi Users — monitor wallet balances and transaction statuses across multiple protocols via a single interface.

Built-in capabilities (26)

btc_analyzepsbt

Analyze and provide information about a PSBT

btc_createpsbt

Create a transaction in the Partially Signed Bitcoin Transaction format

btc_getbestblockhash

Get the hash of the best (tip) block

btc_getblockchaininfo

Get an object containing various state info regarding blockchain processing

btc_getblockcount

Get the number of blocks in the longest blockchain

btc_sendrawtransaction

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

debug_trace_block_by_number

Get traces for all transactions in a block

debug_trace_call

Run an eth_call within the context of the given block execution

debug_trace_transaction

Get all traces of a given transaction

eth_accounts

Get a list of addresses owned by client

eth_block_number

Get the number of the most recent block

eth_call

Execute a new message call immediately without creating a transaction

eth_estimate_gas

Estimate gas necessary to allow the transaction to complete

eth_get_balance

Get the balance of an Ethereum account

eth_get_block_by_hash

Get information about a block by hash

eth_get_block_by_number

Get information about a block by block number

eth_get_code

Get code at a given address

eth_get_transaction_by_hash

Get information about a transaction by hash

eth_get_transaction_receipt

Get the receipt of a transaction by hash

rpc_call

Execute any generic JSON-RPC method via GetBlock

sol_get_account_info

Get all information associated with the account of provided Pubkey

sol_get_balance

Get the balance of the provided Pubkey

sol_get_latest_blockhash

Get the latest blockhash from the ledger

sol_get_token_account_balance

Get the token balance of an SPL Token account

sol_get_transaction

Get transaction details for a confirmed transaction signature

sol_send_transaction

Submit a signed transaction to the cluster for processing

Why CrewAI?

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.

—
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

GetBlock (Web3 RPC Provider) in CrewAI

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

GetBlock (Web3 RPC Provider) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect GetBlock (Web3 RPC Provider) 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 catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for CrewAI →

Enterprise Security

Why teams choose Vinkius for GetBlock (Web3 RPC Provider) in CrewAI

The GetBlock (Web3 RPC Provider) 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 26 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.

Unlock for AI Agents View full GetBlock (Web3 RPC Provider) details →

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
GetBlock (Web3 RPC Provider) for CrewAI

Every tool call from CrewAI to the GetBlock (Web3 RPC Provider) 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

Can I query blockchains other than Ethereum?

Yes! This server includes specific tools for multiple networks, such as sol_get_balance for Solana and btc_get_blockchain_info for Bitcoin, leveraging GetBlock's multi-chain infrastructure.

How do I execute a custom RPC method not listed in the tools?

Use the rpc_call tool. You can provide the method name (e.g., 'eth_chainId') and a JSON string of parameters to interact with any available endpoint feature.

Is it possible to debug failed smart contract transactions?

Yes. Use the debug_trace_transaction tool with the transaction hash. It will return the execution traces, helping you identify exactly where a call reverted or failed.

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.

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.

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.

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.

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.