Skip to main content
Glama
@cryptoapis-io/mcp-blockchain-events

@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
      A
      quality
      B
      maintenance
      Enables 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.
      21
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Provides 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.
      31
      99 npm
      15
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables 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.
      11
      2
      ISC
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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

    A4.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data