Skip to main content
Glama

Related Servers

Alternatives to mcp-server-tron

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server for AI agents to interact with the JustLend DAO lending protocol on TRON, plus general TRON chain utilities like balances, transfers, and staking.
      37
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Multi-chain wallet MCP server that enables AI agents to manage Bitcoin, Ethereum, Solana, and Tron wallets via tools for addresses, balances, transactions, and token operations.
      123 npm
      CC BY-4.0

    TDQS

    B3/5.0

    Scored across 97 tools

    Disambiguation2/5

    Many tools overlap heavily, especially block retrieval (get_block, get_latest_block, get_block_by_num, get_block_by_id, get_block_by_latest_num, get_block_by_limit_next, get_now_block) and transaction lookup (get_transaction, get_transaction_by_id, get_transaction_info, get_transaction_info_by_id). Account and contract metadata tools also blur together (get_account/get_account_info/get_account_balance/get_balance; get_contract/get_contract_info/fetch_contract_abi).

    Naming Consistency3/5

    Most names use snake_case, but conventions are not fully predictable: noun_verb forms like account_permission_update coexist with verb_noun forms like update_account, and similar operations use different suffixes (_by_id, _by_num, _v2). Redundant aliases such as get_now_block and get_latest_block further reduce naming clarity.

    Tool Count1/5

    97 tools is far beyond a well-scoped surface for this server, and many are near-duplicates or thin aliases for the same underlying node endpoint. The large count increases selection burden without adding proportional capability.

    Completeness5/5

    The surface covers a very broad TRON domain: accounts, blocks, transactions, contracts, events, staking, delegation, governance, Super Representatives, wallet management, and indexed history. Core read and write workflows appear fully represented with no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data