Skip to main content
Glama
Sign In
@tenergy/mcp

@tenergy/mcp

by tenergyme
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to @tenergy/mcp

No user-submitted related servers found.

    Related Servers

    • TronRental MCP Server

      TronRental MCP Serverofficial

      tronrentalcom
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with the TronRental API to register, fund accounts, and purchase TRON energy for reducing USDT transfer fees by up to 80%.
      95 npm
      MIT

    • agent-x402

      rustemmustafingovua-byte
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to check their wallet address and USDC balance, preview the cost of an x402 call, and pay for API requests in USDC on Base without an account or API key. Spend caps, allow-lists and blocked contracts are enforced in code before anything is signed, so a prompt injection cannot bypass them.
      MIT

    • mcp-server-TLD

      bbsyaya
      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
      5 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

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Tools mostly have distinct purposes, but get_prices and get_market both expose current energy prices, and get_price_history and get_market_summary both report market data. The descriptions clarify the differences, so confusion is limited but possible.

    Naming Consistency5/5

    All tool names use snake_case with clear verb_noun patterns such as get_prices, estimate_contract_call, suggest_order_size, calculate_savings, and explain_concept. The convention is consistent and predictable throughout.

    Tool Count5/5

    11 tools is well within the typical 3-15 range and fits the domain of TRON energy data, market info, and estimation. Each tool has a distinct function, though a few read-only queries could theoretically be consolidated.

    Completeness3/5

    The surface covers price data, address resources, chain parameters, estimation, savings, and concepts. However, get_prices explicitly references create_quote for binding prices, but no create_quote or order-placement tool exists, leaving a notable gap for completing a rental transaction.

    Resources