Skip to main content
Glama

Related Servers

Alternatives to SolidRPC

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with Kaspa blockchain nodes via RPC, providing tools for querying node info, block data, addresses, balances, UTXOs, and mempool transactions.
      1
      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
      10 npm
      1
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI agents and developer tools read access to a blockchain network's blocks, transactions, accounts, validators, staking tiers, contract reads and fee estimates, plus post-quantum signature status checks and unsigned transfers for the user's own wallet to sign. It never signs, holds keys, or broadcasts.
      Apache 2.0

    TDQS

    B3.3/5.0

    Scored across 9 tools

    Disambiguation3/5

    Most tools target clear, distinct resources (networks, keys, billing, usage, support). However, solidrpc_manage is a catch-all whose description mentions funding, key creation, and support content, so it overlaps with solidrpc_top_up, solidrpc_create_key, and solidrpc_support, leaving uncertain boundaries between it and the specific tools.

    Naming Consistency3/5

    Names are consistently prefixed with solidrpc_, but the convention is mixed: several are bare resource nouns implying list (networks, keys, billing, usage, support) while others use verb_noun (create_key, revoke_key, top_up) and one uses a vague verb (manage). Still readable, but not a single predictable pattern.

    Tool Count5/5

    Nine tools is well within the ideal 3-15 range and each appears to earn its place for an RPC account-management domain (networks, keys, billing, usage, top-up, support). No bloat or obvious redundancy in count.

    Completeness4/5

    Key lifecycle (list/create/revoke), billing, usage, top-up, networks, and support are covered, giving a fairly complete surface. Minor gaps remain: support can be opened but not listed/read, and there is no way to inspect a single key's detail or update key scope, which could create dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues