MCP Hub
Back to servers

mcp-blockchain-events

MCP server for subscribing to and managing on-chain event webhooks via Crypto APIs

Registry
Updated
Mar 5, 2026

Quick Install

npx -y @cryptoapis-io/mcp-blockchain-events

@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

# 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
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

  1. Start the server in HTTP mode:
    npx @cryptoapis-io/mcp-blockchain-events --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

All servers default to port 3000. Use --port to assign different ports when running multiple servers.

Available Tools

blockchain_events_manage

Manage existing webhook subscriptions.

ActionDescription
list-subscriptionsList all webhook subscriptions
get-subscriptionGet details of a specific subscription
delete-subscriptionDelete a subscription
activate-subscriptionActivate a paused subscription

blockchain_events_create

Create new webhook subscriptions for blockchain events.

ParameterDescription
eventTypeEvent type to subscribe to (e.g., new block, confirmed transaction, address coins)
callbackUrlURL to receive webhook notifications
blockchainTarget blockchain (optional, depends on event type)
networkTarget network (optional, depends on event type)
addressAddress to monitor (optional, depends on event type)

CLI Arguments

ArgumentDescriptionDefault
--api-keyCrypto APIs API keyCRYPTOAPIS_API_KEY env var
--transportTransport type: stdio or httpstdio
--hostHTTP host0.0.0.0
--portHTTP port3000
--pathHTTP path/mcp
--statelessEnable stateless HTTP modefalse

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.
# Per-request key mode (multi-tenant)
npx @cryptoapis-io/mcp-blockchain-events --transport http --port 3000
# Clients send x-api-key header with each request

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

Reviews

No reviews yet

Sign in to write a review