Skip to main content
Glama
@cryptoapis-io/mcp-blockchain-events

@cryptoapis-io/mcp-blockchain-events

Official

@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

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 (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_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

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.

Available Tools

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.

# 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

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:

# 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 tools
blockchain_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 subscriptionsA
Destructive

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 infoA
Read-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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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

    ActivityNo data
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      C
      maintenance
      Provides 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.
      31
      99 npm
      15
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      11
      2
      ISC