@cryptoapis-io/mcp-blockchain-events
OfficialRelated Servers
Alternatives to @cryptoapis-io/mcp-blockchain-events
No user-submitted related servers found.
Related Servers
AlicenseAqualityBmaintenanceEnables merchants and AI agents to create and manage non-custodial multi-chain crypto payment sessions, configure webhook endpoints, and enforce spending policies for autonomous agent payments across EVM, TRON, Solana, and Arc networks.21MIT
Tatum MCP Serverofficial
AlicenseBqualityCmaintenanceProvides 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.3199 npm15MIT
RouteMesh MCP Serverofficial
AlicenseAqualityCmaintenanceEnables 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.112ISC- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents and MCP hosts to register a workspace, create stablecoin checkout and payment links, configure webhooks, verify crypto payment status, and add webhook-based access logic to applications.-
- AlicenseAqualityDmaintenanceEnables cryptocurrency payment processing through the Infini Payment API, supporting order management, multi-chain withdrawals, and webhook verification for USDC/USDT transactions.71AGPL 3.0
- AlicenseNot gradedqualityDmaintenanceEnables 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
TDQS
Scored across 3 tools
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.
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.
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.
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.