Bring Web3
to Cursor
Learn how to connect Blockdaemon (Blockchain Infrastructure) to Cursor and start using 4 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Blockdaemon (Blockchain Infrastructure) MCP Server?
Connect your Blockdaemon account to any AI agent to interact with major blockchain protocols through a single, unified interface. This MCP server leverages the Ubiquity API to provide seamless access to multi-chain data.
What you can do
- Block Exploration — Retrieve block identifiers and metadata for protocols like Bitcoin, Ethereum, Solana, and Polkadot using
list_blocks. - Transaction Tracking — Query full transaction histories for specific account addresses across supported networks with
list_transactions. - UTXO Management — Fetch Unspent Transaction Outputs for UTXO-based chains (Bitcoin, Dogecoin, Litecoin) using
get_utxos. - Financial Reporting — Generate detailed financial reports for addresses on protocols like Algorand, Stellar, and Tezos via
get_financial_report. - Multi-Network Support — Switch between mainnet and testnet environments effortlessly for development and auditing.
How it works
- Subscribe to this server
- Enter your Blockdaemon API Key
- Start querying blockchain data directly from Claude, Cursor, or any MCP client
Who is this for?
- Web3 Developers — Debug transactions and verify block data without leaving your IDE.
- Data Analysts — Aggregate financial reports and transaction histories for cross-chain auditing.
- Crypto Operations — Monitor wallet activity and UTXO sets for treasury management.
Built-in capabilities (4)
Get a financial report for an address
Get Unspent Transaction Outputs (UTXOs)
Get a list of block identifiers
Get a list of transactions for an address
Why Cursor?
Cursor's Agent mode turns Blockdaemon (Blockchain Infrastructure) into an in-editor superpower. Ask Cursor to generate code using live data from Blockdaemon (Blockchain Infrastructure) and it fetches, processes, and writes. all in a single agentic loop. 4 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Blockdaemon (Blockchain Infrastructure) in Cursor
Blockdaemon (Blockchain Infrastructure) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Blockdaemon (Blockchain Infrastructure) to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Blockdaemon (Blockchain Infrastructure) in Cursor
The Blockdaemon (Blockchain Infrastructure) 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. All 4 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Blockdaemon (Blockchain Infrastructure) for Cursor
Every tool call from Cursor to the Blockdaemon (Blockchain Infrastructure) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Which protocols are supported for financial reports?
The get_financial_report tool currently supports Algorand, Polkadot, Stellar, Tezos, and XRP.
Can I filter transactions by date?
Yes, the list_transactions tool allows you to provide 'from' and 'to' Unix timestamps to narrow down your search.
How do I check unspent balances for Bitcoin?
Use the get_utxos tool with the 'bitcoin' protocol and the specific wallet address. You can also toggle 'check_mempool' to include unconfirmed transactions.
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.
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.
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.
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.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.
Explore More MCP Servers
View all →
Gerrit
10 toolsManage code reviews via Gerrit — query changes and patch sets, handle reviewers and approvals, and audit project branches directly from any AI agent.
Vald
6 toolsPower your agent with Vald — query, insert, and manage dense vectors on a highly scalable, distributed nearest-neighbor engine.
Rick and Morty Alternative
9 toolsExplore the Rick and Morty multiverse — query characters, locations, and episodes directly from any AI agent.
iNaturalist
10 toolsExplore biodiversity data — search wildlife observations, identify species, find taxa and discover nature projects.