A
licenseA
qualityD
maintenanceTRON Energy & Bandwidth marketplace for AI agents — 27 MCP tools for buying/selling resources, DEX swaps, and automated energy management via Streamable HTTP.
27
2
MIT
TronSave MCP Server
Officialby tronsave
Related Servers
Alternatives to TronSave MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to check TRON energy prices, estimate the energy a USDT transfer needs, and rent energy for a receiver under a configurable spending cap, without ever handling wallet keys. It also exposes address resource lookups, held quotes, and order status so agents can watch a delegation land on chain.1114 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables 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 npmMIT
mcp-server-justlendofficial
AlicenseBqualityAmaintenanceAn MCP server enabling AI agents to interact with JustLend DAO on TRON for lending, borrowing, and portfolio management, plus general TRON chain utilities.98201 npm3MIT- AlicenseAqualityDmaintenanceAn 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.375 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants such as Claude and Cursor to discover and verify agents, negotiate offers, execute conditional settlements, and verify receipts and complete multi-agent workflows through eight MCP tools.1MIT
TDQS
A3.6/5.0
Scored across 53 tools
Disambiguation2/5
The surface has heavy, function-level duplication between an api-key/internal path and a signature/market path: `tronsave_internal_order_create` vs `tronsave_create_order`, `tronsave_internal_order_estimate` vs `tronsave_estimate_buy_resource`, `tronsave_internal_order_book` vs `tronsave_list_order_books`, and `tronsave_internal_extend_delegates` vs `tronsave_list_extendable_delegates`. There are also three separate extend-discovery tools (`list_extendable_delegates`, `list_extendable_receivers`, `internal_extend_delegates`) plus overlapping quote/depth tools (`estimate_buy_resource`, `get_min_price`, `list_order_books`, `get_price_table`). Descriptions explain the differences, but at 53 tools an agent can easily misselect the wrong auth path or quote tool.
Naming Consistency3/5
Most names use the `tronsave_` prefix with snake_case, which is readable and mostly consistent. However, several tools drop the leading verb (`tronsave_internal_order_create`, `tronsave_internal_order_book`, `tronsave_internal_order_history`, `tronsave_internal_order_details`) while others follow verb_noun (`tronsave_list_orders`, `tronsave_get_order`, `tronsave_create_order`), creating mixed conventions within the same order domain. Additions like `tronsave_sell_order_manual` further blur the pattern.
Tool Count2/5
53 tools is well above a comfortable surface size, even for a broad server covering market data, orders, automation, notifications, referral, Telegram, and flash unstake. Much of the count comes from duplicating the same operations across internal/api-key and signature paths rather than adding genuinely distinct capabilities. This makes the surface heavy and increases selection risk.
Completeness4/5
Coverage is broad: authentication/session tools, market quotes and depth, full order lifecycle (estimate, create, get, list, update, cancel), extend flows, auto-sell and auto-buy configuration, notifications, referral, Telegram alert settings, agency bot, internal ledger, and flash unstake. Minor gaps exist, such as no explicit reclaim/withdraw tool for expired delegations and no dedicated auto-sell delete/disable tool, but most workflows can be completed. Agents can work around these gaps with the existing update and order tools.
Maintenance
ActivityMaintained
ResponsivenessNo issues