A
licenseC
qualityD
maintenanceMCP server for TRON blockchain integration, enabling AI assistants to check balances, manage transactions, interact with smart contracts, and access real-time blockchain data.
33
1
MIT
mcp-server-tron
by BofAI
Related Servers
Alternatives to mcp-server-tron
No user-submitted related servers found.
Related Servers
- 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.377 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
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.9812 npm2MIT- AlicenseBqualityCmaintenanceAn MCP server that enables AI agents to interact with the Solana blockchain through 20 tools for wallet management, SPL token operations, blockchain exploration, and DeFi integration via Jupiter.21MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes blockchain data as native tools for AI agents, enabling read-only queries like wallet balances and token holdings on Ethereum, Polygon, and Base.MIT
TDQS
B3.2/5.0
Scored across 97 tools
Disambiguation2/5
Many tools have overlapping purposes, especially block queries (get_block, get_latest_block, get_block_by_num, get_block_by_id, get_block_by_latest_num, get_block_by_limit_next) and transaction queries (get_transaction, get_transaction_info, get_transaction_by_id, get_transaction_info_by_id). While descriptions attempt to differentiate, the sheer number of similar functions makes it difficult for an agent to reliably choose the correct one.
Naming Consistency3/5
The naming largely follows a snake_case verb_noun pattern (e.g., get_balance, list_witnesses, create_proposal), but there are inconsistencies such as get_now_block vs get_latest_block vs get_block_by_latest_num, broadcast_hex vs broadcast_transaction, and inconsistent use of 'v2' suffixes (get_delegated_resource vs get_delegated_resource_v2). Mixed prepositional phrases and varying noun forms reduce predictability.
Tool Count1/5
With 97 tools, the server is extremely over-scoped. The calibration indicates that 50+ tools is an extreme mismatch, and this server far exceeds that. Many tools appear redundant or overly granular, making the set unwieldy for an agent to navigate effectively.
Completeness4/5
The tool set covers an extensive range of TRON functionalities: wallet management, blocks, transactions, contracts, staking, delegation, accounts, witnesses, proposals, events, and indexed data. It is nearly comprehensive, though minor gaps exist such as a full transaction simulation tool (only energy estimation is provided) and some potential missing governance features.
Maintenance
ActivityInactive
ResponsivenessNo issues