Skip to main content
Glama
erhnysr

thru-mcp-server

by erhnysr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to thru-mcp-server

No user-submitted related servers found.

    Related Servers

    • SVM-MCP

      rkmonarch
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that connects Claude AI with SOON and other SVM-based blockchains, allowing users to check account balances, fetch recent transactions, and view token holdings on SOON's testnet and mainnet.
      6
      3
      -

    • algorand-mcp

      T-WREKX
      A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol (MCP) server providing 50+ tools for Algorand blockchain development, including account management, asset operations, smart contracts, API integration, swap functionality, and advanced transaction capabilities.
      5 npm
      MIT

    • UluCoreMCP

      NautilusOSS
      A
      license
      Not graded
      quality
      D
      maintenance
      Low-level blockchain interface MCP server for Algorand and Voi networks, providing account/asset/app inspection, transaction search, block retrieval, TEAL compilation, and transaction simulation.
      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.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct resource: name resolution, account, transaction, faucet, network, and events. No overlapping purposes; even the two status tools (faucet and network) are clearly separated by domain.

    Naming Consistency4/5

    Five tools use the 'get_' prefix, but 'resolve_name' and 'query_events' deviate from that pattern. All follow a verb_noun structure with consistent lowercase styling, so the inconsistency is minor.

    Tool Count5/5

    Six tools is well-scoped for a blockchain read-only server. Each tool covers a distinct domain area without unnecessary redundancy.

    Completeness4/5

    The set covers core read operations: accounts, transactions, names, network health, faucet state, and event queries. It lacks block-level queries and any transaction submission, but those may be intentionally excluded since withdrawal requires the CLI.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources