@cryptoapis-io/mcp-blockchain-events
OfficialSupports creating and managing webhook subscriptions for on-chain events on the Solana blockchain, enabling monitoring of blocks, transactions, address activity, and token transfers.
Supports creating and managing webhook subscriptions for on-chain events on the XRP blockchain, enabling monitoring of blocks, transactions, address activity, and token transfers.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@@cryptoapis-io/mcp-blockchain-events subscribe to new blocks on Ethereum mainnet"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@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)
Related MCP server: Blockchain Payment MCP Server
Prerequisites
Node.js 18+
Crypto APIs account and API key (sign up | get API key)
Installation
npm install @cryptoapis-io/mcp-blockchain-eventsOr install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
Usage
# Run with API key
npx @cryptoapis-io/mcp-blockchain-events --api-key YOUR_API_KEY
# Or use environment variable
export CRYPTOAPIS_API_KEY=YOUR_API_KEY
npx @cryptoapis-io/mcp-blockchain-events
# HTTP transport (listens on 127.0.0.1; see "Exposing the server beyond localhost")
npx @cryptoapis-io/mcp-blockchain-events --transport http --port 3000 --api-key YOUR_API_KEYClaude 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_KEYn8n
Start the server in HTTP mode:
npx @cryptoapis-io/mcp-blockchain-events --transport http --port 3000 --api-key YOUR_API_KEYIn 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:
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.
Available Tools
blockchain_events_manage
Manage existing webhook subscriptions.
Action | Description |
| List all webhook subscriptions |
| Get details of a specific subscription |
| Delete a subscription |
| Activate a paused subscription |
blockchain_events_create
Create new webhook subscriptions for blockchain events.
Parameter | Description |
| Event type to subscribe to (e.g., new block, confirmed transaction, address coins) |
| URL to receive webhook notifications |
| Target blockchain (optional, depends on event type) |
| Target network (optional, depends on event type) |
| Address to monitor (optional, depends on event type) |
CLI Arguments
Argument | Description | Default |
| Crypto APIs API key |
|
| Transport type: |
|
| HTTP host (use |
|
| Bearer token callers must send ( |
|
| Comma-separated | — |
| HTTP port |
|
| HTTP path |
|
| Enable stateless HTTP mode |
|
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-keyrequest headers are ignored.Without
--api-key: Each request must include anx-api-keyheader 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-blockchain-events --transport http --port 3000
# Clients send x-api-key header with each requestExposing 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:
# 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-blockchain-events --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-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
Available Tools
3 toolsblockchain_events_createCreate blockchain event subscriptionA
Create a webhook subscription for on-chain events. When the specified event occurs, CryptoAPIs sends a POST request to your callbackUrl with the event data. Subscriptions persist until deleted.
Event types (supported blockchains vary per type — an invalid blockchain for the chosen eventType is rejected before calling the API): • address-coins-transactions-unconfirmed: fires when an unconfirmed coin transaction touches the address • address-coins-transactions-confirmed: fires once a coin transaction confirms (optionally on an exact confirmation via receiveCallbackOn) • address-coins-transactions-confirmed-each-confirmation: fires on every confirmation up to confirmationsCount (required) • address-tokens-transactions-confirmed: fires once a token transfer confirms • address-tokens-transactions-confirmed-each-confirmation: fires on every confirmation up to confirmationsCount (required) • address-internal-transactions-confirmed: fires once a confirmed internal (contract-internal) transaction touches the address • address-internal-transactions-confirmed-each-confirmation: fires on every confirmation up to confirmationsCount (required) • block-mined: fires on every new block (no address field)
All event types except block-mined require an address.
Note: 'create' actions require confirmation. They return a preview with a one-time token instead of executing immediately.
Credits per call: 30
Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
Inputs: network (required), eventType (required), blockchain (required), callbackUrl (required), +7 more.
blockchain_events_manageManage blockchain event subscriptionsADestructive
Manage existing webhook subscriptions for on-chain events. Use this to view, delete, or re-activate event subscriptions created via blockchain_events_create.
Actions: • list-subscriptions: List all active subscriptions for a blockchain/network (paginated) • get-subscription: Get details of a specific subscription by its referenceId • delete-subscription: Remove a subscription (stops webhook delivery) • activate-subscription: Re-activate a previously deactivated subscription
Note: 'delete-subscription', 'activate-subscription' actions require confirmation. They return a preview with a one-time token instead of executing immediately.
Credits by action (source: OpenAPI): • activate-subscription: 12 • delete-subscription: 12 • get-subscription: 12 • list-subscriptions: 12
Credits are indicative only and may change at any time. The actual credits spent for each API request are returned in the response headers.
Inputs: action (required), limit, offset, context, +4 more.
system_infoCryptoAPIs reference infoARead-onlyIdempotent
CryptoAPIs reference documentation — no API call, no credits consumed.
Actions: • blockchains — Supported blockchains, networks, products per chain, denominations, fiat currencies • errors — Complete error code table (HTTP status, error code, message) • credits — Credit charging structure, cost multipliers per blockchain, monitoring & operations taxes (xPub, synced addresses, blockchain events), pay-as-you-go • callbacks — Webhook mechanics: URL requirements, retry strategy (5 retries, exponential backoff), HMAC security, idempotency • limits — Throughput soft/hard limits per plan, 2.1x penalty multiplier, rate limiting behavior
Inputs: action (required), context.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
The three tools have clearly distinct roles: create subscriptions, manage existing subscriptions, and retrieve reference documentation. The manage tool's list/get/delete/activate actions are explicitly scoped to existing subscriptions, so it should not be confused with create.
The two core event tools follow a consistent blockchain_events_* snake_case pattern, and system_info is also snake_case. The only minor deviation is that system_info belongs to a different domain and the verb position differs across the event tools.
Three tools is a reasonable, focused surface for a blockchain webhook-events server, with lifecycle actions grouped under manage. The count is slightly thin, and system_info is auxiliary rather than a core event operation, but nothing is excessive.
The surface covers create, list, get, delete, and activate, but lacks an update operation and, notably, a deactivate action even though activate-subscription implies subscriptions can be deactivated. These gaps mean some lifecycle changes require delete-and-recreate workarounds.
Maintenance
Related MCP Connectors
Webhook alerts for EVM wallets, contract admin changes, Safe queues and custom events.
Webhooks for AI agents: send events, manage endpoints, inspect and retry deliveries.
Decoded on-chain events for AI agents: find triggers, subscribe a webhook, read delivery logs.
Send and debug webhooks — applications, endpoints, messages, delivery attempts and replays.
Related MCP Servers
AlicenseBqualityCmaintenanceProvides access to Tatum's blockchain API across 40+ networks, enabling developers to interact with blockchain data, manage notifications, estimate fees, access RPC nodes, and work with smart contracts through natural language.3199 npm15MIT- AlicenseNot gradedqualityDmaintenanceEnables blockchain payment operations across multiple networks including Base, Ethereum, BSC, Polygon, and Avalanche. Supports balance queries, token transfers, transaction tracking, wallet management, and gas fee estimation with built-in security limits.MIT
- AlicenseAqualityDmaintenanceEnables cryptocurrency payment processing through the Infini Payment API, supporting order management, multi-chain withdrawals, and webhook verification for USDC/USDT transactions.71AGPL 3.0

RouteMesh MCP Serverofficial
AlicenseAqualityCmaintenanceEnables querying blockchain data across multiple EVM chains via RouteMesh, offering built-in RPC tools for blocks, transactions, logs, balances, and gas estimation, plus customer management tools for API keys and usage.112ISC