@cryptoapis-io/mcp-blockchain-events
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_AUTH_TOKEN | No | Bearer token callers must send in HTTP mode when exposing the server beyond localhost. Prefer this over the --auth-token CLI flag. | |
| CRYPTOAPIS_API_KEY | Yes | Crypto APIs API key. Required for all requests. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| blockchain_events_manageA | 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. |
| blockchain_events_createA | 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. |
| system_infoA | 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 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| setup-webhook | Set up a webhook subscription for on-chain events |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| supported-chains | Supported blockchains, networks, event types, and actions for the blockchain-events tools |
TDQS
Scored across 3 tools
The three tools have clearly distinct purposes: managing existing webhook subscriptions, creating new subscriptions, and providing static reference documentation. There is no overlap or confusion between them.
blockchain_events_manage and blockchain_events_create follow a consistent resource_action pattern in snake_case, while system_info breaks the prefix pattern but remains readable. The overall style is consistent snake_case with a minor deviation for the utility tool.
Three tools is well-scoped for a webhook event service: one for creation, one for lifecycle management, and one for reference. Each tool earns its place without redundancy.
The surface covers create, list, get, delete, and reactivate, but there is no deactivate action despite activate-subscription referencing 'previously deactivated' subscriptions. No update operation exists either, leaving a notable lifecycle gap.