4,000+ servers built on vurb.ts
Vinkius

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

MCP Inspector GDPR Free for Subscribers

LlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add GetBlock (Web3 RPC Provider) as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.

Ask AI about this MCP Server for LlamaIndex

The GetBlock (Web3 RPC Provider) MCP Server for LlamaIndex 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
import asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI

async def main():
    # Your Vinkius token. get it at cloud.vinkius.com
    mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
    mcp_tool_spec = McpToolSpec(client=mcp_client)
    tools = await mcp_tool_spec.to_tool_list_async()

    agent = FunctionAgent(
        tools=tools,
        llm=OpenAI(model="gpt-4o"),
        system_prompt=(
            "You are an assistant with access to GetBlock (Web3 RPC Provider). "
            "You have 26 tools available."
        ),
    )

    response = await agent.run(
        "What tools are available in GetBlock (Web3 RPC Provider)?"
    )
    print(response)

asyncio.run(main())
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.

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.

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 LlamaIndex 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 LlamaIndex

When LlamaIndex 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 LlamaIndex via MCP

Follow these steps to wire GetBlock (Web3 RPC Provider) into LlamaIndex. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install dependencies

Run pip install llama-index-tools-mcp llama-index-llms-openai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token
03

Run the agent

Save to agent.py and run: python agent.py
04

Explore tools

The agent discovers 26 tools from GetBlock (Web3 RPC Provider)

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

LlamaIndex provides unique advantages when paired with GetBlock (Web3 RPC Provider) through the Model Context Protocol.

01

Data-first architecture: LlamaIndex agents combine GetBlock (Web3 RPC Provider) tool responses with indexed documents for comprehensive, grounded answers

02

Query pipeline framework lets you chain GetBlock (Web3 RPC Provider) tool calls with transformations, filters, and re-rankers in a typed pipeline

03

Multi-source reasoning: agents can query GetBlock (Web3 RPC Provider), a vector store, and a SQL database in a single turn and synthesize results

04

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) + LlamaIndex Use Cases

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

01

Hybrid search: combine GetBlock (Web3 RPC Provider) real-time data with embedded document indexes for answers that are both current and comprehensive

02

Data enrichment: query GetBlock (Web3 RPC Provider) to augment indexed data with live information before generating user-facing responses

03

Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying GetBlock (Web3 RPC Provider) for fresh data

04

Analytical workflows: chain GetBlock (Web3 RPC Provider) queries with LlamaIndex's data connectors to build multi-source analytical reports

Example Prompts for GetBlock (Web3 RPC Provider) in LlamaIndex

Ready-to-use prompts you can give your LlamaIndex 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 LlamaIndex

Common issues when connecting GetBlock (Web3 RPC Provider) to LlamaIndex through Vinkius, and how to resolve them.

01

BasicMCPClient not found

Install: pip install llama-index-tools-mcp

GetBlock (Web3 RPC Provider) + LlamaIndex FAQ

Common questions about integrating GetBlock (Web3 RPC Provider) MCP Server with LlamaIndex.

01

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.
02

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.
03

Does LlamaIndex support async MCP calls?

Yes. LlamaIndex's async agent framework supports concurrent MCP tool calls for high-throughput data processing pipelines.

Explore More MCP Servers

View all →