A
licenseB
qualityC
maintenanceA comprehensive MCP server that enables AI agents to interact with the TRON blockchain, including tools for blockchain data, token transfers, smart contracts, staking, and wallet management.
97
15 npm
21
MIT
tron_mcp_server
Related Servers
Alternatives to tron_mcp_server
No user-submitted related servers found.
Related Servers
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.9811 npm2MIT- 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.3722 npmMIT
- AlicenseNot gradedqualityBmaintenanceMulti-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.91 npmCC BY-4.0
Armor Crypto MCPofficial
AlicenseCqualityCmaintenanceAn MCP server providing unified access to blockchain operations, bridging, swapping, and crypto trading strategies for AI agents.37179GPL 3.0- AlicenseAqualityDmaintenanceAn MCP server enabling AI agents to interact with the 0G blockchain, including balance checks, transaction details, block info, and network statistics.51MIT
TDQS
C2.6/5.0
Scored across 33 tools
Disambiguation3/5
Multiple tools overlap in purpose: estimate_energy and estimate_contract_energy both estimate energy costs; get_block and get_trongrid_block both retrieve block info; several java-tron tools could be consolidated. Some distinctions are clear, but an agent might struggle to choose between similar tools.
Naming Consistency3/5
Most tools follow a verb_noun pattern (e.g., get_balance, send_trx), but there are inconsistencies like contract_call, trongrid_api_call, and analyze_contract_gas (verb_noun but with underscore). The pattern is generally readable but not uniform.
Tool Count3/5
33 tools is high for a single server, but many are justified by covering different aspects of TRON. However, the inclusion of 7 java-tron-specific tools and two wrapper API calls (trongrid_api_call, tronscan_api_call) makes the set feel bloated for the core blockchain domain.
Completeness2/5
The server lacks fundamental TRON operations like token management (TRC10/TRC20), contract deployment, and account creation. It over-emphasizes java-tron repository access, which is tangential. Agents would struggle to perform common tasks without the missing operations.
Maintenance
ActivityInactive
ResponsivenessNo issues