Compatible with every major AI agent and IDE
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_calltool 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)
Analyze and provide information about a PSBT
Create a transaction in the Partially Signed Bitcoin Transaction format
Get the hash of the best (tip) block
Get an object containing various state info regarding blockchain processing
Get the number of blocks in the longest blockchain
Submit raw transaction (serialized, hex-encoded) to local node and network
Get traces for all transactions in a block
Run an eth_call within the context of the given block execution
Get all traces of a given transaction
Get a list of addresses owned by client
Get the number of the most recent block
Execute a new message call immediately without creating a transaction
Estimate gas necessary to allow the transaction to complete
Get the balance of an Ethereum account
Get information about a block by hash
Get information about a block by block number
Get code at a given address
Get information about a transaction by hash
Get the receipt of a transaction by hash
Execute any generic JSON-RPC method via GetBlock
Get all information associated with the account of provided Pubkey
Get the balance of the provided Pubkey
Get the latest blockhash from the ledger
Get the token balance of an SPL Token account
Get transaction details for a confirmed transaction signature
Submit a signed transaction to the cluster for processing
Why LlamaIndex?
LlamaIndex agents combine GetBlock (Web3 RPC Provider) tool responses with indexed documents for comprehensive, grounded answers. Connect 26 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
- —
Data-first architecture: LlamaIndex agents combine GetBlock (Web3 RPC Provider) tool responses with indexed documents for comprehensive, grounded answers
- —
Query pipeline framework lets you chain GetBlock (Web3 RPC Provider) tool calls with transformations, filters, and re-rankers in a typed pipeline
- —
Multi-source reasoning: agents can query GetBlock (Web3 RPC Provider), a vector store, and a SQL database in a single turn and synthesize results
- —
Observability integrations show exactly what GetBlock (Web3 RPC Provider) tools were called, what data was returned, and how it influenced the final answer
GetBlock (Web3 RPC Provider) in LlamaIndex
GetBlock (Web3 RPC Provider) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect GetBlock (Web3 RPC Provider) to LlamaIndex 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.
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 |
Why teams choose Vinkius for GetBlock (Web3 RPC Provider) in LlamaIndex
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 LlamaIndex 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.

* 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
How Vinkius secures
GetBlock (Web3 RPC Provider) for LlamaIndex
Every tool call from LlamaIndex 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.
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 LlamaIndex connect to MCP servers?
Use the MCP client adapter to create a connection. LlamaIndex discovers all tools and wraps them as query engine tools compatible with any LlamaIndex agent.
Can I combine MCP tools with vector stores?
Yes. LlamaIndex agents can query GetBlock (Web3 RPC Provider) tools and vector store indexes in the same turn, combining real-time and embedded data for grounded responses.
Does LlamaIndex support async MCP calls?
Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.
BasicMCPClient not found
Install: pip install llama-index-tools-mcp
Explore More MCP Servers
View all →
OpenAI
10 toolsUse GPT-4o, DALL-E 3, embeddings, fine-tuning, and moderation as tools inside your AI agent workflows.

WSLA (WhatsApp)
5 toolsSend WhatsApp messages, templates, and reactions via AI using the Meta Cloud API.

Markdown Utilities Engine
2 toolsEquip your AI with programmatic Markdown tools. Deterministically generate Table of Contents (TOC) with correct anchor links and format perfect Markdown tables from JSON.

Mashvisor
10 toolsAnalyze real estate investments — compare Airbnb vs traditional rental ROI via AI.
