4,000+ servers built on vurb.ts
Vinkius

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

MCP Inspector GDPR Free for Subscribers

Google Agent Development Kit (ADK) is Google's framework for building production AI agents. Add GetBlock (Web3 RPC Provider) as an MCP tool provider through Vinkius and your ADK agents can call every tool with full schema introspection.

Ask AI about this MCP Server for Google ADK

The GetBlock (Web3 RPC Provider) MCP Server for Google ADK 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 google.adk.agents import Agent
from google.adk.tools.mcp_tool import McpToolset
from google.adk.tools.mcp_tool.mcp_session_manager import (
    StreamableHTTPConnectionParams,
)

# Your Vinkius token. get it at cloud.vinkius.com
mcp_tools = McpToolset(
    connection_params=StreamableHTTPConnectionParams(
        url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp",
    )
)

agent = Agent(
    model="gemini-2.5-pro",
    name="getblock_web3_rpc_provider_agent",
    instruction=(
        "You help users interact with GetBlock (Web3 RPC Provider) "
        "using 26 available tools."
    ),
    tools=[mcp_tools],
)
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.

Google ADK natively supports GetBlock (Web3 RPC Provider) as an MCP tool provider. declare Vinkius Edge URL and the framework handles discovery, validation, and execution automatically. Combine 26 tools with Gemini's long-context reasoning for complex multi-tool workflows, with production-ready session management and evaluation built in.

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 Google ADK 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 Google ADK

When Google ADK 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 Google ADK via MCP

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

01

Install Google ADK

Run pip install google-adk
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token
03

Create the agent

Save the code above and integrate into your ADK workflow
04

Explore tools

The agent will discover 26 tools from GetBlock (Web3 RPC Provider) via MCP

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

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

01

Google ADK natively supports MCP tool servers. declare a tool provider and the framework handles discovery, validation, and execution

02

Built on Gemini models, ADK provides long-context reasoning ideal for complex multi-tool workflows with GetBlock (Web3 RPC Provider)

03

Production-ready features like session management, evaluation, and deployment come built-in. not bolted on

04

Seamless integration with Google Cloud services means you can combine GetBlock (Web3 RPC Provider) tools with BigQuery, Vertex AI, and Cloud Functions

GetBlock (Web3 RPC Provider) + Google ADK Use Cases

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

01

Enterprise data agents: ADK agents query GetBlock (Web3 RPC Provider) and cross-reference results with internal databases for comprehensive analysis

02

Multi-modal workflows: combine GetBlock (Web3 RPC Provider) tool responses with Gemini's vision and language capabilities in a single agent

03

Automated compliance checks: schedule ADK agents to query GetBlock (Web3 RPC Provider) regularly and flag policy violations or configuration drift

04

Internal tool platforms: build self-service agent platforms where teams connect their own MCP servers including GetBlock (Web3 RPC Provider)

Example Prompts for GetBlock (Web3 RPC Provider) in Google ADK

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

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

01

McpToolset not found

Update: pip install --upgrade google-adk

GetBlock (Web3 RPC Provider) + Google ADK FAQ

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

01

How does Google ADK connect to MCP servers?

Import the MCP toolset class and pass the server URL. ADK discovers and registers all tools automatically, making them available to your agent's tool-use loop.
02

Can ADK agents use multiple MCP servers?

Yes. Declare multiple MCP tool providers in your agent configuration. ADK merges all tool schemas and the agent can call tools from any server in a single turn.
03

Which Gemini models work best with MCP tools?

Gemini 2.0 Flash and Pro models both support function calling required for MCP tools. Flash is recommended for latency-sensitive use cases, Pro for complex reasoning.

Explore More MCP Servers

View all →