@cryptoapis-io/mcp-blockchain-events
OfficialRelated Servers
Alternatives to @cryptoapis-io/mcp-blockchain-events
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceWebhook management and debugging. Validate signatures, log events, replay, and analyze webhook traffic.59 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceA webhook management and delivery service with MCP tools for endpoints, deliveries, relay, and incoming webhooks, enabling autonomous agents to send, track, and relay webhooks.MIT

mcp-events-outpost-demoofficial
AlicenseNot gradedqualityBmaintenanceEnables agents such as ChatGPT to subscribe to events happening behind an MCP server (for example, order.created with filters) and receive them as signed webhooks without the builder implementing delivery itself. Hookdeck Outpost handles filtering, Standard Webhooks signing, retries, and delivery to each subscriber's callback URL.MIT- AlicenseNot gradedqualityCmaintenanceEnables subscription management in a single connected Wallos account via Streamable HTTP tools — reference data lookup, search and pagination, cost summaries, upcoming payments, subscription creation and patching, tracking-state toggles, and reminder settings. Writes are idempotent and version-checked against the underlying Wallos records.Do What The F*ck You Want To Public
- FlicenseNot gradedqualityDmaintenanceEnables management and inspection of webhook tokens (URLs) and incoming requests via webhook-test.com, allowing users to create, list, fetch details, fetch payloads, and delete webhooks without custom API integrations.-
- FlicenseNot gradedqualityCmaintenanceEnables interaction with Convoy's webhooks proxy API for managing and monitoring webhook delivery, events, and configurations through natural language.56 npm-
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.