Skip to main content
Glama
CryptoAPIs-io

@cryptoapis-io/mcp-blockchain-events

Official

Related Servers

Alternatives to @cryptoapis-io/mcp-blockchain-events

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Webhook management and debugging. Validate signatures, log events, replay, and analyze webhook traffic.
      59 PyPI
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Convoy's webhooks proxy API for managing and monitoring webhook delivery, events, and configurations through natural language.
      56 npm
      -

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues