Skip to main content
Glama
Hovsteder

TRON infrastructure for AI agents.

by Hovsteder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to TRON infrastructure for AI agents.

Related Servers

  • 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
    22 npm
    MIT

  • aipaygen-mcp

    Damien829
    A
    license
    Not graded
    quality
    C
    maintenance
    250+ AI-powered MCP tools: research, write, code, translate, scrape, sentiment, vision, RAG, agent memory, marketplace, trading signals, and more. 15 models across 7 providers. Pay-per-use via API key or x402 USDC micropayments.
    2
    MIT

  • maxia-mcp

    majorelalexis-stack
    A
    license
    Not graded
    quality
    D
    maintenance
    AI-to-AI marketplace MCP server with 46 tools — swap 65+ crypto tokens on 7 chains, rent GPUs, trade 25 tokenized stocks, on-chain escrow (Solana + Base), DeFi yields, sentiment analysis, wallet monitoring, and image generation. Supports USDC payments across 14 blockchains.
    MIT

  • mcp-services

    san-npm
    A
    license
    Not graded
    quality
    D
    maintenance
    Multi-tool MCP server for AI agents with 29 tools across web scraping, SEO analysis, screenshot and PDF generation, domain intelligence, content extraction, multi-chain EVM blockchain queries, and security toolkit. Free tier available with no auth required.
    12 npm
    1
    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

B3.3/5.0

Scored across 53 tools

Disambiguation4/5

Most tools are clearly distinct, but there are a few close pairs like get_trx_balance vs get_account_info, and get_prices vs get_best_price vs compare_providers vs analyze_prices. Descriptions mostly clarify the differences, so agents should rarely misselect, but some overlap remains.

Naming Consistency3/5

The naming is mostly verb_noun (e.g., transfer_trx, create_order, get_balance), but there are inconsistencies: plural vs singular (get_prices vs get_token_price, list_orders vs get_order), and some tools use different verbs (check_address_resources vs get_account_info). While readable, the pattern is not perfectly uniform.

Tool Count2/5

With 53 tools, this server is overwhelming. Even for a broad infrastructure purpose, this exceeds typical agent-friendly ranges. The high count increases selection complexity and maintenance overhead, making it less usable.

Completeness5/5

The server covers a comprehensive set of TRON operations: on-chain queries, transfers, contract interactions, resource management, price analysis, account management, and automation. It includes explicit tools for simulation, estimation, and standing orders, leaving no obvious gaps in its domain.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources