TRON Tools

io.github.hhh7666Published by GitHub account hhh7666v0.1.0Updated Oct 24, 2026

Free TRON utilities: validate addresses, check balances, assess risk, estimate fees.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint offering free TRON utilities: validate addresses, check balances, assess risk and estimate fees.

What you can do
Validate TRON addresses for correctness and format checks. Check TRON account balances. Assess risk for addresses or activity. Estimate transaction fees before sending. The manifest lists no individual tools, so exact tool names and parameters are not documented.
When to use it
Useful when an assistant needs quick TRON blockchain lookups — confirming an address is valid, checking a balance, gauging risk, or estimating fees — without setting up a local package.
Requirements
A remote streamable HTTP endpoint; no local runtime, package, API key, environment variable or header is declared. Network access to the provider's endpoint is required.
Before you install
The server is operated by a third party and no authentication is declared, so requests and any addresses queried go to that operator. Fee estimates and risk assessments are informational and should not be treated as financial advice. No source code or README is available to verify behavior.

Installation

In SourceWeft

  1. Open TRON Tools in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.hhh7666%2Ftron-tools/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "tron-tools": {
      "type": "http",
      "url": "https://validator.lifari777.workers.dev/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 25, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.