cryptoapis-mcp-block-data
Official# @cryptoapis-io/mcp-block-data
MCP server for [Crypto APIs](https://cryptoapis.io/) Block Data product. Get block details by height or hash for EVM, UTXO, and XRP blockchains.
> **API Version:** Compatible with Crypto APIs version **2024-12-12**
## Features
- Get block details by block height or block hash
- List transactions by block height or block hash
- Get last mined block and list latest mined blocks
- Supported EVM chains: Ethereum, Ethereum Classic, BSC, Polygon, Avalanche (C-Chain), Arbitrum, Base, Optimism, Tron
- Supported UTXO chains: Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash
- Supported other: XRP (mainnet, testnet)
## Prerequisites
- Node.js 18+
- [Crypto APIs](https://cryptoapis.io/) account and API key ([sign up](https://app.cryptoapis.io/signup) | [get API key](https://app.cryptoapis.io/api-keys))
## Installation
```bash
npm install @cryptoapis-io/mcp-block-data
```
Or install all Crypto APIs MCP servers: `npm install @cryptoapis-io/mcp`
## Usage
```bash
# Run with API key
npx @cryptoapis-io/mcp-block-data --api-key YOUR_API_KEY
# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-block-data
# HTTP transport (listens on 127.0.0.1; see "Exposing the server beyond localhost")
npx @cryptoapis-io/mcp-block-data --transport http --port 3000 --api-key YOUR_API_KEY
```
### Claude Desktop
Add to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS, `%APPDATA%\Claude\claude_desktop_config.json` on Windows):
```json
{
"mcpServers": {
"cryptoapis-block-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-block-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
```
### Cursor
Add to `.cursor/mcp.json` (project) or `~/.cursor/mcp.json` (global):
```json
{
"mcpServers": {
"cryptoapis-block-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-block-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
```
### MCP Inspector
```bash
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-block-data --api-key YOUR_API_KEY
```
### n8n
1. Start the server in HTTP mode:
```bash
npx @cryptoapis-io/mcp-block-data --transport http --port 3000 --api-key YOUR_API_KEY
```
2. In your n8n workflow, add an **AI Agent** node
3. Under **Tools**, add an **MCP Client Tool** and set the URL to `http://localhost:3000/mcp`
> **n8n in Docker:** `localhost` inside the container is not your machine. Start the server with `--host 0.0.0.0` and `MCP_AUTH_TOKEN` set (see [Exposing the server beyond localhost](#exposing-the-server-beyond-localhost)), use `http://host.docker.internal:3000/mcp` as the URL, and add an `Authorization: Bearer <token>` header to the MCP Client Tool credential.
> All servers default to port 3000. Use `--port` to assign different ports when running multiple servers.
## Available Tools
### `evm_block_data`
Get EVM block details.
| Action | Description |
|--------|-------------|
| `get-block-by-height` | Get block details by block number |
| `get-block-by-hash` | Get block details by block hash |
| `list-transactions-by-block-height` | List transactions in a block by block height |
| `list-transactions-by-block-hash` | List transactions in a block by block hash |
| `get-last-mined-block` | Get the latest mined block details |
| `list-latest-mined-blocks` | List the latest mined blocks |
### `utxo_block_data`
Get UTXO block details (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).
| Action | Description |
|--------|-------------|
| `get-block-by-height` | Get block details by block number |
| `get-block-by-hash` | Get block details by block hash |
| `list-transactions-by-block-height` | List transactions in a block by block height |
| `list-transactions-by-block-hash` | List transactions in a block by block hash |
| `get-last-mined-block` | Get the latest mined block details |
| `list-latest-mined-blocks` | List the latest mined blocks |
### `xrp_block_data`
Get XRP block (ledger) details.
| Action | Description |
|--------|-------------|
| `get-block-by-height` | Get ledger details by ledger index |
| `get-block-by-hash` | Get ledger details by ledger hash |
| `list-transactions-by-block-height` | List transactions in a block by block height |
| `list-transactions-by-block-hash` | List transactions in a block by block hash |
| `get-last-mined-block` | Get the latest mined block details |
| `list-latest-mined-blocks` | List the latest mined blocks |
## CLI Arguments
| Argument | Description | Default |
|----------|-------------|---------|
| `--api-key` | Crypto APIs API key | `CRYPTOAPIS_API_KEY` env var |
| `--transport` | Transport type: `stdio` or `http` | `stdio` |
| `--host` | HTTP host (use `0.0.0.0` to accept remote connections — requires an auth token with `--api-key`) | `127.0.0.1` |
| `--auth-token` | Bearer token callers must send (`Authorization: Bearer <token>`); prefer the `MCP_AUTH_TOKEN` env var | `MCP_AUTH_TOKEN` env var |
| `--allowed-hosts` | Comma-separated `Host` header allowlist for non-loopback binds | — |
| `--port` | HTTP port | `3000` |
| `--path` | HTTP path | `/mcp` |
| `--stateless` | Enable stateless HTTP mode | `false` |
### HTTP API Key Modes
When using HTTP transport, the server supports two API key modes:
- **With `--api-key`:** The key is used for all requests. `x-api-key` request headers are ignored.
- **Without `--api-key`:** Each request must include an `x-api-key` header with a valid Crypto APIs key. This enables hosting a public server where each user provides their own key.
```bash
# Per-request key mode (multi-tenant)
npx @cryptoapis-io/mcp-block-data --transport http --port 3000
# Clients send x-api-key header with each request
```
### Exposing the server beyond localhost
HTTP mode listens on `127.0.0.1` by default, so only processes on the same machine can reach it.
To accept connections from other machines or containers, bind explicitly and protect the port:
```bash
# Startup-key mode: callers must present the token (the server refuses to start without one)
export MCP_AUTH_TOKEN=$(openssl rand -hex 32)
npx @cryptoapis-io/mcp-block-data --transport http --host 0.0.0.0 --port 3000 --api-key YOUR_API_KEY \
--allowed-hosts mcp.internal.example
# Clients send: Authorization: Bearer $MCP_AUTH_TOKEN
# Per-request key mode: no startup key, every request must carry the caller's own x-api-key
npx @cryptoapis-io/mcp-block-data --transport http --host 0.0.0.0 --port 3000
```
`--allowed-hosts` restricts the `Host` header (DNS rebinding protection) when not bound to loopback. Prefer `MCP_AUTH_TOKEN` over `--auth-token`: command-line arguments are visible in the process list.
> Stdio transport always requires an API key at startup.
## Important: API Key Required
> **Warning:** Making requests without a valid API key — or with an incorrect one — may result in your IP being banned from the Crypto APIs ecosystem. Always ensure a valid API key is configured before starting any server.
## Remote MCP Server
Crypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at [https://ai.cryptoapis.io/mcp](https://ai.cryptoapis.io/mcp). Pass your API key via the `x-api-key` header — no installation required.
## License
MIT
TDQS
Scored across 4 tools
The three block-data tools are separated by blockchain family (EVM, UTXO, XRP), which gives clear selection rules when the chain is known. However, they expose identical action names, so an agent must first classify the target chain and could confuse EVM vs. UTXO if the chain is unspecified. system_info is clearly distinct as a reference tool.
The three main tools follow a predictable snake_case pattern of [chain_family]_block_data. system_info deviates from that pattern but is a clearly separate reference utility, making the inconsistency minor and understandable.
Four tools is well-scoped for a block-data server: three chain-family wrappers plus one reference tool. Each tool earns its place by consolidating multiple related actions, avoiding an overly fragmented surface.
The surface covers the full block-data lifecycle for all supported chain families: block by height/hash, transaction listing by block height/hash, and latest-mined-block retrieval. system_info fills the supporting reference/documentation role, leaving no obvious gaps for the stated purpose.