@cryptoapis-io/mcp-blockchain-events
MCP server for Crypto APIs Blockchain Events product. Create and manage webhook subscriptions for on-chain events.
API Version: Compatible with Crypto APIs version 2024-12-12
Features
- Create webhook subscriptions for blockchain events (new block, confirmed transaction, address coins, token transfers, etc.)
- List, get, activate, and delete existing subscriptions
- Supports all major blockchains (EVM, UTXO, Solana, XRP)
Prerequisites
Installation
npm install @cryptoapis-io/mcp-blockchain-events
Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
Usage
npx @cryptoapis-io/mcp-blockchain-events --api-key YOUR_API_KEY
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-blockchain-events
npx @cryptoapis-io/mcp-blockchain-events --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):
{
"mcpServers": {
"cryptoapis-blockchain-events": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-blockchain-events"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
Cursor
Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"cryptoapis-blockchain-events": {
"command": "npx",
"args": ["-y", "@cryptoapis-io/mcp-blockchain-events"],
"env": {
"CRYPTOAPIS_API_KEY": "your_api_key_here"
}
}
}
}
MCP Inspector
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-blockchain-events --api-key YOUR_API_KEY
n8n
- Start the server in HTTP mode:
npx @cryptoapis-io/mcp-blockchain-events --transport http --port 3000 --api-key YOUR_API_KEY
- In your n8n workflow, add an AI Agent node
- 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), 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.
blockchain_events_manage
Manage existing webhook subscriptions.
| Action | Description |
|---|
list-subscriptions | List all webhook subscriptions |
get-subscription | Get details of a specific subscription |
delete-subscription | Delete a subscription |
activate-subscription | Activate a paused subscription |
blockchain_events_create
Create new webhook subscriptions for blockchain events.
| Parameter | Description |
|---|
eventType | Event type to subscribe to (e.g., new block, confirmed transaction, address coins) |
callbackUrl | URL to receive webhook notifications |
blockchain | Target blockchain (optional, depends on event type) |
network | Target network (optional, depends on event type) |
address | Address to monitor (optional, depends on event type) |
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.
npx @cryptoapis-io/mcp-blockchain-events --transport http --port 3000
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:
export MCP_AUTH_TOKEN=$(openssl rand -hex 32)
npx @cryptoapis-io/mcp-blockchain-events --transport http --host 0.0.0.0 --port 3000 --api-key YOUR_API_KEY \
--allowed-hosts mcp.internal.example
npx @cryptoapis-io/mcp-blockchain-events --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. Pass your API key via the x-api-key header — no installation required.
License
MIT