@cryptoapis-io/mcp-block-data
MCP server for Crypto APIs 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
에이전트 강화
게시자의 자체 명령입니다. PlugMCP 엔드포인트가 아닙니다.
Host a copy with our keys and logs.
npx -y @cryptoapis-io/[email protected]Claude Code에는 로컬 명령용 설치 링크가 없습니다. 아래 명령을 복사해 터미널에서 실행합니다.
CRYPTOAPIS_API_KEY=<secret> claude mcp add io.github.cryptoapis-io-mcp-block-data -- npx -y @cryptoapis-io/mcp-block-data@0.5.0터미널에서 실행합니다.
{ "mcpServers": { "io.github.cryptoapis-io-mcp-block-data": { "command": "npx", "args": [ "-y", "@cryptoapis-io/[email protected]" ], "env": { "CRYPTOAPIS_API_KEY": "<secret>" } } }}claude_desktop_config.json
원격 URL인가요, 내 컴퓨터에서 실행하는 명령인가요? 두 설치 방식의 차이
PlugMCP에서 실행
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
실행게시자 제공
MCP server for Crypto APIs 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
MCP server for retrieving block-level data from EVM, UTXO, and XRP blockchains via Crypto APIs
npm install @cryptoapis-io/mcp-block-data
Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
# 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
Add to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):
{
"mcpServers": {
"cryptoapis-block-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-block-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-block-data": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-block-data"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-block-data --api-key YOUR_API_KEY
npx @cryptoapis-io/mcp-block-data --transport http --port 3000 --api-key YOUR_API_KEY
http://localhost:3000/mcpn8n in Docker:
localhostinside the container is not your machine. Start the server with--host 0.0.0.0andMCP_AUTH_TOKENset (see Exposing the server beyond localhost), usehttp://host.docker.internal:3000/mcpas the URL, and add anAuthorization: Bearer <token>header to the MCP Client Tool credential.
All servers default to port 3000. Use
--portto assign different ports when running multiple servers.
evm_block_dataGet EVM block details.
utxo_block_dataGet UTXO block details (Bitcoin, Bitcoin Cash, Litecoin, Dogecoin, Dash, Zcash).
xrp_block_dataGet XRP block (ledger) details.
When using HTTP transport, the server supports two API key modes:
--api-key: The key is used for all requests. x-api-key request headers are ignored.--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.# 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
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:
# 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.
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.
Crypto APIs provides an official remote MCP server with all tools available via HTTP Streamable transport at https://ai.cryptoapis.io/mcp. Pass your API key via the x-api-key header — no installation required.
MIT
MCP server for retrieving block-level data from EVM, UTXO, and XRP blockchains via Crypto APIs
{ "mcpServers": { "io.github.cryptoapis-io-mcp-block-data": { "command": "npx", "args": [ "-y", "@cryptoapis-io/[email protected]" ], "env": { "CRYPTOAPIS_API_KEY": "<secret>" } } }}도구
아직 도구 목록이 없습니다. 원격 서버는 첫 상태 확인 후에 도구 목록이 생깁니다.
FAQ
이 페이지에서 Cursor, Claude Desktop, Claude Code 또는 VS Code용 stdio 설정을 복사합니다. PlugMCP 프록시가 아니라 게시자의 설치 방식을 사용합니다.
게시자가 등록한 환경 변수: CRYPTOAPIS_API_KEY.
MCP Block Data은(는) stdio를 통해 로컬에서 실행됩니다.
마지막 확인: 2026-11-18. MCP server for retrieving block-level data from EVM, UTXO, and XRP blockchains via Crypto APIs