
Mcp Block Data
Pull block-level metadata from EVM, UTXO, and XRP chains inside your agent while building explorers, sync jobs, or debugging tools.
Overview
io.github.CryptoAPIs-io/mcp-block-data is a MCP server for the Build phase that retrieves block-level data from EVM, UTXO, and XRP blockchains through Crypto APIs.
What is this MCP server?
- Block-level data for EVM, UTXO, and XRP via Crypto APIs
- npm package @cryptoapis-io/mcp-block-data v0.3.0 with stdio transport
- CRYPTOAPIS_API_KEY-gated access for agent hosts
- Complements address-latest and fees servers in the same CryptoAPIs-io MCP family
- Repository: github.com/CryptoAPIs-io/cryptoapis-mcp-block-data
- Version 0.3.0
- Chains: EVM, UTXO, XRP
- Registry package @cryptoapis-io/mcp-block-data
What problem does it solve?
Building block-aware agent features usually means juggling different RPC formats for Ethereum-class, UTXO, and XRP networks.
Who is it for?
Builders prototyping block explorers, sync checkpoints, or agent-assisted chain debugging against Crypto APIs.
Skip if: Projects requiring Solana or Kaspa block data (not listed for this server) or fully decentralized indexing without a commercial API.
What do I get? / Deliverables
Agents call unified MCP block-data tools so you can implement block lookups and validation logic with less integration code.
- Agent-invokable tools for EVM, UTXO, and XRP block-level queries
- Reduced custom client code for block fetches during integration
Recommended MCP Servers
Journey fit
Block retrieval underpins backends, indexers, and agent reasoning during implementation—canonical Build placement even if you reuse it later in Operate. The server is a direct Crypto APIs block-data MCP bridge, fitting the integrations subphase where external data providers are registered.
How it compares
Hosted block-data MCP over Crypto APIs, not a local Erigon or bitcoind node skill.
Common Questions / FAQ
Who is mcp-block-data for?
Developers and solo founders who use MCP agents to build products that need authoritative block information on EVM, UTXO, or XRP without operating their own nodes.
When should I use mcp-block-data?
Use it while integrating backends or agent tools that must resolve blocks by height or hash, verify inclusion context, or enrich transactions with block metadata.
How do I add mcp-block-data to my agent?
Add @cryptoapis-io/mcp-block-data to your MCP server list with stdio transport and export CRYPTOAPIS_API_KEY before starting the agent session.