BlockPi MCP. Monitor balances and run RPC calls across chains
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 (Distributed RPC Network) connects your AI agent to multiple blockchain RPC nodes. Use it to check your Request Unit (RU) balances, monitor wallet funds in USD, track consumption over custom periods, and execute standard JSON-RPC calls (like `eth_blockNumber`) across Ethereum, Polygon, and Solana.
It lets you manage your entire decentralized infrastructure without leaving your chat client.
What your AI agents can do
Get package expiration
Gets details about all active Request Unit (RU) packages you have purchased.
Get ru balance
Retrieves your remaining Request Unit (RU) balance across all connected networks.
Get ru consumed
Calculates how many RUs you've spent for a specific blockchain endpoint or period.
Retrieves your current Request Unit (RU) balance and your wallet balance in USD.
Calculates total RU consumption over custom timeframes (1, 3, or 7 days) for cost optimization.
Gets specific details on active RU packages, including remaining amounts and expiration timestamps.
Runs standard blockchain operations (e.g., fetching block numbers or balances) on specified networks.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
BlockPi (Distributed RPC Network) MCP Server: 5 Tools for Blockchain Data
Use these five tools to query your resource status, track spending, and execute raw JSON-RPC calls across any supported blockchain network.
019e5d00get package expiration
Gets details about all active Request Unit (RU) packages you have purchased.
019e5d00get ru balance
Retrieves your remaining Request Unit (RU) balance across all connected networks.
019e5d00get ru consumed
Calculates how many RUs you've spent for a specific blockchain endpoint or period.
019e5d00get wallet balance
Returns your current fiat wallet balance measured in USD.
019e5d00rpc call
Makes a generic JSON-RPC call to any supported blockchain network (e.g., `eth_blockNumber`).
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,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ 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
What you can do with this MCP connector
BlockPi (Distributed RPC Network) is how your AI agent talks to multiple blockchains. You can manage your entire decentralized setup—checking funds, tracking usage, and running RPC calls—all from your chat client. You'll never have to leave your conversation window just to check a block number or see how much RU you're blowing through.
How BlockPi MCP Works
- 1 Subscribe to the BlockPi server and input your API Key.
- 2 Ask your AI client to run a specific check, like 'What's my RU balance on Polygon?'
- 3 The server executes the required tool (e.g.,
get_ru_balance) and returns the balance data directly to your agent.
The bottom line is: you query the status of your infrastructure and the blockchain using standard language, and the server runs the necessary background calls.
Who Is BlockPi MCP For?
The Web3 developer who needs to check node health and balances without switching tabs. The DevOps engineer who has to monitor infrastructure consumption and package expiration to prevent downtime. Data analysts who need to fetch raw, complex blockchain data using simple queries.
Checks node health, verifies balances, and executes specific RPC methods directly within their code editor or terminal.
Monitors infrastructure consumption and tracks package expiration dates to ensure continuous uptime for decentralized applications.
Fetches raw blockchain data using natural language queries based on standard RPC methods.
What Changes When You Connect
- Instantly check your financial status. Use
get_wallet_balanceto see your USD funds, andget_ru_balancefor your operational RU pool, all in one chat session. - Optimize spending by tracking usage. Run
get_ru_consumedto see exactly how much RU a specific endpoint has eaten, preventing unexpected cost spikes. - Prevent downtime by managing packages. Use
get_package_expirationto view SKUs and expiration timestamps, so you never run out of operational units unexpectedly. - Talk to any blockchain. The
rpc_calltool lets you run standard JSON-RPC methods—likeeth_blockNumber—on Ethereum, Polygon, or Solana, without writing boilerplate code. - Consolidate data views. You can compare your RU consumption history (1, 3, or 7 days) against your current
get_ru_balanceto get a full picture of your dApp's cost trajectory.
Real-World Use Cases
Need to verify the current block height on a new chain.
A developer needs to confirm the latest block number on Arbitrum. They ask their agent to run rpc_call with eth_blockNumber on Arbitrum. The agent executes the call and returns the precise block height, allowing the developer to proceed with writing the smart contract logic.
Running out of credits and need a usage report.
An operations engineer notices the system is slowing down. They ask the agent to run get_ru_consumed for the last 7 days. The agent reports the total RU usage, letting the engineer know they need to buy a new package immediately.
Checking if the primary RPC node is still healthy.
A Web3 dev runs a status check. They ask the agent to check get_ru_balance and get_wallet_balance. The agent reports both the remaining RU and the USD balance, confirming that both operational funds are available.
Debugging a complex cross-chain interaction.
A data analyst needs to fetch a specific transaction hash detail. They use rpc_call with eth_call on Polygon. The agent returns the raw payload data, which the analyst can then feed into a local data processing script for deep inspection.
The Tradeoffs
Treating the system like a single RPC endpoint
Asking the agent to just 'get all blockchain data' and hoping it knows which balance or package status you need. This results in a vague error or incomplete data.
→
Be specific. If you need the funds, use get_ru_balance. If you need the chain state, use rpc_call with the specific method name (e.g., eth_blockNumber). Never assume the tool knows your intent.
Forgetting the package expiration date
Writing code that relies on a package that has passed its expiration date, leading to silent failure and unexpected service downtime.
→
Always check get_package_expiration first. It shows the SKU and precise expiration timestamp, making sure your operational funds are current.
Ignoring USD vs. RU balances
Assuming that having a high RU balance means you can afford an operation, only to find out the underlying wallet balance is zero.
→
Check both get_ru_balance and get_wallet_balance together. This ensures you have both the operational units and the fiat funding required for the call.
When It Fits, When It Doesn't
Use this server if you need to monitor the operational state of a multi-chain dApp. It's perfect for Web3 developers and DevOps engineers who need to query resource consumption, check package validity, and run raw blockchain queries without leaving their editor. Don't use this if you just need a simple API endpoint for a single chain; use a dedicated, single-purpose library instead. If you are building a complex business logic flow (e.g., 'check balance AND then execute call'), you must sequence the calls: first get_ru_balance to confirm funds, then rpc_call to execute the action. Never skip the balance checks.
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.
Available Capabilities
Checking blockchain health shouldn't require jumping between a dashboard and a terminal.
Today, checking your node's operational status means logging into the BlockPi dashboard, clicking the 'Balances' tab, then navigating to 'Packages' to check expirations. Then you have to open a separate terminal window to run `eth_blockNumber` and see if the chain is actually responding.
With this MCP server, you just ask your agent, 'What's the status of the Polygon node?' The agent runs `get_ru_balance` and `rpc_call` in the background and gives you a single, cohesive answer: the current balance, the available funds, and the latest block number.
BlockPi (Distributed RPC Network) MCP Server: Get the real data you need.
Before, fetching raw blockchain data required writing a specific library call for every single chain and endpoint. You had to manage the connection, the parameters, and the error handling yourself.
Now, you just ask for the data. The agent uses `rpc_call` to execute the generic JSON-RPC call, handling the multi-chain connectivity and formatting the result for you. It's direct.
Common Questions About BlockPi MCP
How do I check my current RU balance using the `get_ru_balance` tool? +
You ask your agent to 'check my RU balance.' The tool returns your remaining Request Unit count. This is separate from your USD wallet balance, which you check with get_wallet_balance.
Can I check the block number on multiple chains using the `rpc_call` tool? +
Yes. You specify the target network and the method (e.g., eth_blockNumber) in the prompt. The rpc_call tool handles the connection to the specified blockchain.
What is the difference between `get_ru_balance` and `get_ru_consumed`? +
get_ru_balance gives you the remaining units right now. get_ru_consumed calculates the total amount you've spent over a specific time window (like 3 days).
How do I check when my RU package expires using `get_package_expiration`? +
Simply ask the agent to 'show package expiration details.' The tool provides the SKU and the exact expiration timestamp for all your active RU packages.
Does BlockPi support all blockchains? Does `rpc_call` work everywhere? +
It supports major chains like Ethereum, Polygon, Solana, and more. Always specify the network when using rpc_call to ensure the agent hits the right endpoint.
How do I check my remaining wallet balance in USD using the `get_wallet_balance` tool? +
It fetches your current fiat balance in USD. This is separate from your Request Units (RU) and tracks the actual money available to fund your node operations.
Can I track how much I've used for a specific function using the `get_ru_consumed` tool? +
Yes, this tool pinpoints consumption for a specific endpoint. It tells you exactly how much RU was used for a targeted operation, helping you pinpoint cost drivers.
What happens if I use the `rpc_call` tool with an unsupported network? +
The system returns a specific error message detailing the unsupported network. You must check the supported list for the blockchain you want to query before running the call.
How can I check my remaining Request Unit (RU) credits? +
You can use the get_ru_balance tool. Simply specify the network (e.g., 'ethereum') to see the current RU balance associated with your account.
Can I execute standard Ethereum methods like getting the latest block number? +
Yes! Use the rpc_call tool. Provide the network (e.g., 'ethereum') and the method name 'eth_blockNumber' to get real-time data from the blockchain.
How do I monitor my API usage over the last week? +
Use the get_ru_consumed tool and set the 'days' parameter to '7'. This will return the total RU consumption for your endpoints over that period.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
OceanBase
Enterprise distributed relational database — manage clusters, tenants, and databases via AI.
Pipedream
Manage Pipedream serverless workflows, sources, webhooks, and raw event data natively via AI agents.
Google Search Console
Monitor your website's search performance, fix indexing issues, and manage sitemaps via AI.
You might also like
URL Metadata Scraper
Stop wasting tokens scraping entire websites. Instantly extract clean OpenGraph metadata (title, description, image) from any URL.
Squarespace
Equip your AI with read-only superpowers over your Squarespace platform. Scan transactions, track orders, and audit inventory effortlessly.
SerpApi
Equip your AI agent with real-time web search capabilities across Google, Bing, Baidu, Yahoo, and DuckDuckGo.