Skip to main content
Glama
CryptoAPIs-io

@cryptoapis-io/mcp-signer

Official
by CryptoAPIs-io
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @cryptoapis-io/mcp-signer

No user-submitted related servers found.

    Related Servers

    • paraswap-mcp

      rustok-org
      A
      license
      A
      quality
      C
      maintenance
      MCP server that builds unsigned Paraswap token swap transactions for self-custody wallets, holding no keys and signing nothing. It returns raw transaction data for a human to review and approve before execution.
      1
      MIT No Attribution

    • shardnest

      hua-hua3321
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for self-custodial wallet infrastructure, enabling secure key generation, Shamir secret sharing, signing, and recovery without exposing private keys to LLMs.
      12 npm
      MIT

    • gatepay-local-mcp

      gate
      A
      license
      A
      quality
      D
      maintenance
      A local MCP server for handling X402 payment-protected HTTP endpoints, offering tools for order placement, signing, and payment submission with multiple signing modes and blockchain networks.
      7
      52 npm
      1
      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.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct blockchain or ecosystem (EVM, Tezos, Kaspa, SVM, Tron, UTXO, XRP), so an agent can easily select the correct signer based on the chain. The only potential confusion is that Kaspa is a UTXO chain but has its own tool, yet the description of utxo_sign explicitly lists its supported chains and excludes Kaspa, making boundaries clear.

    Naming Consistency5/5

    All tool names follow a consistent <ecosystem/chain>_sign pattern in snake_case, with no mixing of conventions. The use of ecosystem names (evm, svm, utxo) alongside chain names (tezos, kaspa, tron, xrp) is a minor variation but still predictable and readable.

    Tool Count5/5

    Seven tools is well-scoped for a multi-chain transaction signer, with each tool covering a distinct ecosystem or chain and earning its place. The count avoids redundancy while providing broad coverage.

    Completeness4/5

    The surface covers signing for seven major ecosystems, with multiple actions (sign-from-details, sign-unsigned-hex, etc.) where relevant, and no dead ends for the stated purpose. However, message signing is only supported for EVM (via typed data), and other chains might lack that capability, leaving a minor gap.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources