BlockPi (Distributed RPC Network) MCP. Query any blockchain node without leaving your editor
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
BlockPi lets you manage decentralized RPC nodes directly through natural language queries. Check your Request Unit (RU) balances, track consumption across multiple chains—like Ethereum or Polygon—and execute any standard JSON-RPC call without leaving your agent environment.
It gives developers immediate, deep access to multi-chain blockchain data.
What your AI agents can do
Get package expiration
Checks the expiration dates and remaining amounts for your active resource packages.
Get ru balance
Retrieves your current Request Unit (RU) balance, showing how much budget you have left.
Get ru consumed
Reports the total RU usage for a specified time window or endpoint.
Get a real-time count of remaining Request Units (RU) for billing visibility.
Retrieve your actual monetary balance stored in US dollars.
See how many RUs were used over configurable periods like 1, 3, or 7 days to predict costs.
Confirm the SKU details and precise timestamps for all active RU packages.
Run standard JSON-RPC methods (like eth_call) across supported networks like BSC or Polygon.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
BlockPi (Distributed RPC Network) - 5 Tools
Use these five tools to manage your blockchain resources. Query RU balances, track consumption history, check package expiry, or run any standardized JSON-RPC call across multiple networks.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using BlockPi (Distributed RPC Network) on Vinkius019e5d00get package expiration
Checks the expiration dates and remaining amounts for your active resource packages.
019e5d00get ru balance
Retrieves your current Request Unit (RU) balance, showing how much budget you have left.
019e5d00get ru consumed
Reports the total RU usage for a specified time window or endpoint.
019e5d00get wallet balance
Provides your remaining wallet funds, measured in US dollars.
019e5d00rpc call
Makes a generic JSON-RPC call to execute methods like `eth_blockNumber` on supported blockchains.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with BlockPi (Distributed RPC Network), then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by BlockPi. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 5 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Dealing with fragmented node status and resource dashboards is a nightmare.
Today, checking if your decentralized application nodes are healthy means logging into three separate dashboards: one for billing (to check USD funds), one for usage metrics (to see RU consumption), and another to run the actual data query. You copy keys here, you switch tabs there, and you spend minutes cross-referencing dates just to get a simple balance report.
With this MCP, you treat it like talking to a teammate who already knows all your node credentials. You ask for a status check, and it gathers the RU balance, checks the wallet funds, and validates package expiry—all without you ever leaving your chat window or code editor.
The `rpc_call` tool gives you direct access to blockchain data.
Previously, getting basic chain data meant writing a specific script for every single function (like one script for block number and another for balance). You were locked into the API's structure and couldn't easily swap chains or functions on the fly.
Now, you just use `rpc_call`. It handles the complexity of formatting that JSON-RPC payload across Ethereum, Polygon, Solana, and more. You get raw data instantly, making your agent a universal blockchain query tool.
What you can do with this MCP connector
Look, managing Web3 infrastructure is complicated. You're dealing with dozens of nodes and constantly juggling costs and balances across different chains. This MCP lets you connect that complexity directly into your AI client. Instead of running multiple commands in separate terminals, you just ask your agent what you need. It checks your Request Unit (RU) balance, shows you how much you've consumed over the last seven days, and tells you when your current packages expire.
If you need raw blockchain data—say, the latest block number or a specific transaction detail—it runs that generic JSON-RPC call on Ethereum, Solana, Polygon, and more. You handle all your resource monitoring and querying from one place using Vinkius’s catalog.
019e5d01-1923-7133-af2c-149e394e1e5b 
How BlockPi (Distributed RPC Network) MCP Works
- 1 Subscribe to the BlockPi MCP on Vinkius and provide your API key.
- 2 Connect your preferred AI client to authorize access to the distributed RPC tools.
- 3 Ask your agent a question—for example, 'What was my RU consumption last week?' or 'Get the current block number on Polygon.' — and it handles the rest.
The bottom line is that you stop managing infrastructure via multiple dashboards and start doing it through simple conversation.
Who Is BlockPi (Distributed RPC Network) MCP For?
This MCP is for the Web3 Developer who gets frustrated having to jump between terminal windows, dashboard APIs, and billing portals just to check node health. It’s for the DevOps Engineer needing continuous monitoring of resource usage, or the Data Analyst pulling raw data from multiple chains.
Writes smart contracts and dApps that need frequent, low-latency access to blockchain state. They use this MCP to quickly validate node health and test complex calls.
Maintains the decentralized application infrastructure. They rely on it to monitor RU consumption over time and ensure no package expires unexpectedly, keeping the service running 24/7.
Needs raw blockchain data points for deep analysis. They use this MCP to query standard RPC methods across various networks without writing complex scripts every time.
What Changes When You Connect
- Real-time visibility into costs. Use
get_ru_balanceandget_wallet_balanceto instantly confirm both your RU budget and the cash in your wallet, eliminating guessing games. - Predictive cost management. Check usage trends with
get_ru_consumedfor 1, 3, or 7 days. This lets you optimize your dApp spending before hitting a wall. - Infrastructure reliability checks. Use
get_package_expirationto inspect package details and expiry timestamps, ensuring zero downtime for mission-critical decentralized apps. - Universal data access. The
rpc_calltool executes standard blockchain methods across Ethereum, Polygon, Solana, and more networks—all from one query. - Reduced context switching. Instead of opening multiple tabs or running separate scripts to check balances and run queries, your agent handles it all via natural conversation.
Real-World Use Cases
Checking spending limits before deployment
A developer needs to ensure a new feature won't crash the node due to high usage. They ask their agent, 'What is my RU consumption for the last 7 days on Polygon?' The MCP runs get_ru_consumed and reports back, allowing them to scale resources before launch.
Validating the current network state
A data analyst needs the absolute latest block height from a secondary chain. They ask their agent to run an rpc_call for eth_blockNumber on that specific chain, getting immediate, accurate confirmation.
Pre-deployment resource audit
A DevOps engineer needs to confirm they have enough funds. They ask the agent to check both get_ru_balance and get_wallet_balance. The MCP confirms resources are available, preventing a costly service outage.
Troubleshooting connectivity issues
A user suspects their node is running out of budget. They ask the agent to check for package expiry using get_package_expiration, which immediately flags an upcoming resource limit, solving the mystery instantly.
The Tradeoffs
Checking balances manually
A user runs a query that works but forgets to check if their wallet has enough USD first. The agent replies 'Success,' but the system fails later due to insufficient funds.
→
Always start by checking your financial standing with get_wallet_balance before running resource-intensive tasks or making calls using rpc_call.
Assuming network consistency
A developer assumes the current RU balance is enough for a complex query, but another process depleted the budget moments before. The tool call fails with an 'Insufficient Budget' error.
→
Before any major operation, run get_ru_balance and cross-reference it against your expected usage to confirm capacity.
Running generic queries without scope
A user runs an RPC call for a general query but doesn't specify the target chain (e.g., Ethereum vs Polygon). The agent defaults to the wrong network, giving bad data.
→
Always explicitly name the intended blockchain and ensure you use rpc_call with parameters that define both the function and the supported network.
When It Fits, When It Doesn't
Use this MCP if your work involves monitoring decentralized node infrastructure or running raw, multi-chain RPC calls. You need a single point of truth for resource management—checking balances (get_ru_balance, get_wallet_balance), tracking usage over time (get_ru_consumed), and verifying package status (get_package_expiration). Don't use this if you just need to call a simple, singular REST endpoint or interact with non-blockchain data sources; for those cases, a standard API connector is better. If your primary goal is merely writing code logic without needing external financial or network state validation, then the MCP might be overkill.
Common Questions About BlockPi (Distributed RPC Network) MCP
How do I check my remaining RU budget using `get_ru_balance`? +
Just ask your agent to run the get_ru_balance tool. It immediately reports your current Request Unit count, letting you know exactly how much spending capacity you have left.
Can I check my wallet balance and RU usage together? +
Yes. You can ask the agent to run both get_wallet_balance and get_ru_consumed. This gives you a single view of both your cash funds and your consumed resource budget.
What if I want to query a specific chain using `rpc_call`? +
You simply tell the agent which network and which function. The MCP uses rpc_call to execute standard methods like eth_blockNumber across supported chains, no matter what they are.
How does `get_package_expiration` help me avoid downtime? +
It checks your active resource packages. If a package is nearing expiration or has low remaining amounts, the tool tells you exactly when that will happen, letting you top up proactively.
How do I use get_ru_consumed to analyze my RU usage over a specific time period? +
It provides total consumption figures for defined windows. You can specify periods like 1, 3, or 7 days to track spending trends accurately and optimize your dApp's infrastructure costs.
What credentials do I need when calling get_wallet_balance? +
You must provide an active BlockPi API Key. This key authenticates your request, allowing the MCP to securely track usage and report your remaining wallet balance in USD.
If my blockchain data request fails using rpc_call, how do I troubleshoot the error? +
The MCP returns specific JSON-RPC error codes. These codes tell you if the issue is invalid input parameters or a network problem, helping you quickly adjust your query structure and fix the failure.
Does rpc_call support all major blockchains, or is it limited to Ethereum? +
No, it supports multiple chains. You can execute standard JSON-RPC calls across networks like Polygon, BSC, Solana, and more, making it highly versatile for multi-chain development.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.