MCP server for subscribing to and managing on-chain event webhooks via Crypto APIs
MCP server for subscribing to and managing on-chain event webhooks via Crypto APIs
Valid MCP server (2 strong, 3 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry. Trust signals: trusted author (14/14 approved).
12 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Set these up before or after installing:
Environment variable: CRYPTOAPIS_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-cryptoapis-io-mcp-blockchain-events": {
"env": {
"CRYPTOAPIS_API_KEY": "your-cryptoapis-api-key-here"
},
"args": [
"-y",
"@cryptoapis-io/mcp-blockchain-events"
],
"command": "npx"
}
}
}Once installed, try these example prompts and explore these capabilities:
From the project's GitHub README.
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
npm install @cryptoapis-io/mcp-blockchain-events
Or install all Crypto APIs MCP servers: npm install @cryptoapis-io/mcp
# 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
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"
}
}
}
}
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"
}
}
}
}
npx @modelcontextprotocol/inspector npx @cryptoapis-io/mcp-blockchain-events --api-key YOUR_API_KEY
npx @cryptoapis-io/mcp-blockchain-events --transport http --port 3000 --api-key YOUR_API_KEY
http://localhost:3000/mcpAll servers default to port 3000. Use
--portto assign different ports when running multiple servers.
blockchain_events_manageManage 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_createCreate 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) |
| Argument | Description | Default |
|---|---|---|
--api-key | Crypto APIs API key | CRYPTOAPIS_API_KEY env var |
--transport | Transport type: stdio or http | stdio |
--host | HTTP host | 0.0.0.0 |
--port | HTTP port | 3000 |
--path | HTTP path | /mcp |
--stateless | Enable stateless HTTP mode | false |
When using HTTP transport, the server supports two API key modes:
--api-key: The key is used for all requests. x-api-key request headers are ignored.--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.
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.
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.
MIT
Be the first to review this server!
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.
by Microsoft · Content & Media
Convert files (PDF, Word, Excel, images, audio) to Markdown for LLM consumption
by mcp-marketplace · Developer Tools
Scaffold, build, and publish TypeScript MCP servers to npm — conversationally
by mcp-marketplace · Finance
Free stock data and market news for any MCP-compatible AI assistant.
by Taylorwilsdon · Productivity
Control Gmail, Calendar, Docs, Sheets, Drive, and more from your AI