Skip to main content
Glama
CryptoAPIs-io

@cryptoapis-io/mcp-blockchain-fees

Official
by CryptoAPIs-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

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

No user-submitted related servers found.

    Related Servers

    • @cryptoapis-io/mcp-aml by CryptoAPIs-io

      @cryptoapis-io/mcp-amlofficial

      CryptoAPIs-io
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Crypto APIs AML, enabling verification of blockchain addresses and screening of transactions for fraud, sanctions, and other AML risk categories.
      2
      30 npm
      MIT

    • @cryptoapis-io/mcp-utils

      CryptoAPIs-io
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Crypto APIs Utils, enabling address validation, raw transaction decoding, and XRP X-Address encoding/decoding for UTXO, EVM, and XRP blockchains.
      194 npm
      MIT

    • @cryptoapis-io/mcp

      CryptoAPIs-io
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Crypto APIs Transactions Data. Enables lookup of transaction details by hash across EVM, UTXO, Solana, XRP, and Kaspa blockchains.
      53 npm
      MIT
    • @cryptoapis-io/mcp-address-history by CryptoAPIs-io

      @cryptoapis-io/mcp-addressofficial

      CryptoAPIs-io
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Crypto APIs Address History product, enabling querying full blockchain address transaction history for synced addresses across EVM and UTXO blockchains.
      4
      75 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct blockchain family (UTXO, EVM, XRP) or serves a clearly separate documentation purpose (system_info). There is no overlap or ambiguity between tool purposes.

    Naming Consistency4/5

    The three fee tools follow a consistent 'blockchain_fees_<type>' pattern, making their scope predictable. system_info deviates from the fee-focused naming but is a clear utility name, so the overall set is mostly consistent.

    Tool Count5/5

    Four tools is a well-scoped count for a fee-estimation server. Each tool handles a distinct category (UTXO, EVM, XRP, documentation) without unnecessary bloat or missing essentials.

    Completeness4/5

    The server covers the primary blockchain fee estimation families (UTXO, EVM, XRP) and includes detailed internal actions for each. Minor gaps exist for other fee types or chains, but the core domain is well covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources