Is io.github.CryptoAPIs-io/mcp-blockchain-events safe to use?

io.github.CryptoAPIs-io/mcp-blockchain-events has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.

How do I install io.github.CryptoAPIs-io/mcp-blockchain-events?

io.github.CryptoAPIs-io/mcp-blockchain-events supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What can io.github.CryptoAPIs-io/mcp-blockchain-events do?

io.github.CryptoAPIs-io/mcp-blockchain-events provides 2 tools: blockchain_events_manage, blockchain_events_create. See the full tools list on the server page for descriptions and parameters.

What AI clients work with io.github.CryptoAPIs-io/mcp-blockchain-events?

io.github.CryptoAPIs-io/mcp-blockchain-events is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.

Is io.github.CryptoAPIs-io/mcp-blockchain-events actively maintained?

io.github.CryptoAPIs-io/mcp-blockchain-events is less actively maintained — last commit was 108 days ago.

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

@cryptoapis-io/mcp-blockchain-events

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

82/wk 2 tools GitHub npm

No known CVEs

No license

Maintained

Last commit 108d ago

Works with most clients

Transport: stdio, http

2 tools · ~353 tok

Grade A · 0.2% of 200K ctx

Edit this pageView history

Finance

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "cryptoapis-blockchain-events": {
      "env": {
        "CRYPTOAPIS_API_KEY": "your_api_key_here"
      },
      "args": [
        "-y",
        "@cryptoapis-io/mcp-blockchain-events"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-cryptoapis-io-mcp-blockchain-events)](https://mcppedia.org/s/io-github-cryptoapis-io-mcp-blockchain-events)

Read me

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

MCP server for Crypto APIs Blockchain Events product. Create and manage webhook subscriptions for on-chain events.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y '@cryptoapis-io/mcp-blockchain-events' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

79/100across 5 weighted dimensions

How we score →

0255075100

−21

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @cryptoapis-io/mcp-blockchain-events against OSV.dev.

Inventory

Tools (2)

Click any tool to inspect its schema.

~353 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.CryptoAPIs-io/mcp-blockchain-events safe to use?: io.github.CryptoAPIs-io/mcp-blockchain-events has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.CryptoAPIs-io/mcp-blockchain-events?: io.github.CryptoAPIs-io/mcp-blockchain-events supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.CryptoAPIs-io/mcp-blockchain-events do?: io.github.CryptoAPIs-io/mcp-blockchain-events provides 2 tools: blockchain_events_manage, blockchain_events_create. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.CryptoAPIs-io/mcp-blockchain-events?: io.github.CryptoAPIs-io/mcp-blockchain-events is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is io.github.CryptoAPIs-io/mcp-blockchain-events actively maintained?: io.github.CryptoAPIs-io/mcp-blockchain-events is less actively maintained — last commit was 108 days ago.

Similar servers

Others in finance

View all →

io.github.wyre-technology/qbo-mcp92

MCP server for QuickBooks Online — accounts, customers, invoices, bills, and reports.

2 11

Printr MCP Server92

Let AI agents create, discover, and track tokens across chains via Printr.

3 9

Alpha Vantage Mcp91

Real-time financial market data: stocks, forex, crypto, commodities, and economic indicators

178 3

io.github.imbenrabi/financial-modeling-prep-mcp-server90

MCP server for Financial Modeling Prep API with 250+ financial data tools

138 5

MCP Security Weekly

Get CVE alerts and security updates for io.github.CryptoAPIs-io/mcp-blockchain-events and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

Finance

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktopstdio, http · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "cryptoapis-blockchain-events": {
      "env": {
        "CRYPTOAPIS_API_KEY": "your_api_key_here"
      },
      "args": [
        "-y",
        "@cryptoapis-io/mcp-blockchain-events"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-cryptoapis-io-mcp-blockchain-events)](https://mcppedia.org/s/io-github-cryptoapis-io-mcp-blockchain-events)

Read me

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

MCP server for Crypto APIs Blockchain Events product. Create and manage webhook subscriptions for on-chain events.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y '@cryptoapis-io/mcp-blockchain-events' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

@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

Node.js 18+
Crypto APIs account and API key (sign up | get API key)

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

Start the server in HTTP mode:

npx @cryptoapis-io/mcp-blockchain-events --transport http --port 3000 --api-key YOUR_API_KEY

In your n8n workflow, add an AI Agent node
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.

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	`0.0.0.0`
`--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

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

79/100across 5 weighted dimensions

How we score →

0255075100

−21

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

No known CVEs.

Checked @cryptoapis-io/mcp-blockchain-events against OSV.dev.

Inventory

Tools (2)

Click any tool to inspect its schema.

~353 tokens total

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.CryptoAPIs-io/mcp-blockchain-events safe to use?: io.github.CryptoAPIs-io/mcp-blockchain-events has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments.
How do I install io.github.CryptoAPIs-io/mcp-blockchain-events?: io.github.CryptoAPIs-io/mcp-blockchain-events supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What can io.github.CryptoAPIs-io/mcp-blockchain-events do?: io.github.CryptoAPIs-io/mcp-blockchain-events provides 2 tools: blockchain_events_manage, blockchain_events_create. See the full tools list on the server page for descriptions and parameters.
What AI clients work with io.github.CryptoAPIs-io/mcp-blockchain-events?: io.github.CryptoAPIs-io/mcp-blockchain-events is compatible with claude-desktop, cursor, claude-code. It uses stdio and http transport.
Is io.github.CryptoAPIs-io/mcp-blockchain-events actively maintained?: io.github.CryptoAPIs-io/mcp-blockchain-events is less actively maintained — last commit was 108 days ago.