4,000+ servers built on vurb.ts
Vinkius

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

MCP Inspector GDPR Free for Subscribers

Cursor is an AI-first code editor built on VS Code that integrates LLM-powered coding assistance directly into the development workflow. Its Agent mode enables autonomous multi-step coding tasks, and MCP support lets agents access external data sources and APIs during code generation.

Ask AI about this MCP Server for Cursor

The GetBlock (Web3 RPC Provider) MCP Server for Cursor 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
Classic Setup·json
{
  "mcpServers": {
    "getblock-web3-rpc-provider": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install GetBlock (Web3 RPC Provider) and 4,000+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
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.

Cursor's Agent mode turns GetBlock (Web3 RPC Provider) into an in-editor superpower. Ask Cursor to generate code using live data from GetBlock (Web3 RPC Provider) and it fetches, processes, and writes. all in a single agentic loop. 26 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.

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

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

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

01

Open MCP Settings

Press Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) → search "MCP Settings"
02

Add the server config

Paste the JSON configuration above into the mcp.json file that opens
03

Save the file

Cursor will automatically detect the new MCP server
04

Start using GetBlock (Web3 RPC Provider)

Open Agent mode in chat and ask: "Using GetBlock (Web3 RPC Provider), help me...". 26 tools available

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

Cursor AI Code Editor provides unique advantages when paired with GetBlock (Web3 RPC Provider) through the Model Context Protocol.

01

Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context

02

Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards

03

MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment

04

VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools

GetBlock (Web3 RPC Provider) + Cursor Use Cases

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

01

Code generation with live data: ask Cursor to generate a security report module using live DNS and subdomain data fetched through MCP

02

Automated documentation: have Cursor query your API's tool schemas and generate TypeScript interfaces or OpenAPI specs automatically

03

Infrastructure-as-code: Cursor can fetch domain configurations and generate corresponding Terraform or CloudFormation templates

04

Test scaffolding: ask Cursor to pull real API responses via MCP and generate unit test fixtures from actual data

Example Prompts for GetBlock (Web3 RPC Provider) in Cursor

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

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

01

Tools not appearing in Cursor

Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
02

Server shows as disconnected

Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.

GetBlock (Web3 RPC Provider) + Cursor FAQ

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

01

What is Agent mode and why does it matter for MCP?

Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
02

Where does Cursor store MCP configuration?

Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
03

Can Cursor use MCP tools in inline edits?

No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
04

How do I verify MCP tools are loaded?

Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.

Explore More MCP Servers

View all →