io.github.CryptoAPIs-io/mcp-blockchain-events

Subscribe to and manage on-chain event webhooks through Crypto APIs.

Source

Official Registry

Updated

2026-09-24

// securityCaution

Requires keys· CRYPTOAPIS_API_KEY
Runs locally
Official / curated
Open source
Community-trusted

Running security audit…

Credentials
Network egress
Code execution
Data access
Supply chain

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "io.github.CryptoAPIs-io/mcp-blockchain-events" MCP server from askskill:
Run: claude mcp add 'io-github-cryptoapis-io-mcp-blockchain-events' -- npx -y @cryptoapis-io/mcp-blockchain-events

// use cases

Monitor on-chain business events

Developers can use it to track addresses or on-chain activity and receive event notifications via webhooks instead of constant polling. It fits event-driven flows for wallets, payments, or asset tracking systems.

Maintain webhook subscription configurations

DevOps or platform teams can centrally manage existing on-chain event subscriptions, including viewing, updating, or canceling webhook configurations. This helps maintain event callback integrations more reliably.

Add real-time notifications to product features

Product managers or technical teams can use this tool when designing features like on-chain alerts or incoming transfer notifications. It suits scenarios where blockchain events need to trigger downstream business actions.

// docs

No documentation provided

Check the source repo for usage and examples.

Go to source repo ↗

// FAQ

What does this tool do?

This is an MCP server for subscribing to and managing on-chain event webhooks via Crypto APIs. Its core capability is handling on-chain event subscriptions and webhook management.

What prerequisites are needed to use it?

From the description, it clearly depends on Crypto APIs for on-chain event webhook capabilities. For exact requirements such as API keys, accounts, or runtime setup, see the source repository.

How is it different from polling blockchain data?

It focuses on subscribing to and managing on-chain events through webhooks rather than repeatedly querying data manually. That makes it better suited for triggering automated workflows when events occur.