TronOrb — TRON analytics
REMOTE · TRONORB.COM
Live TRON data: USDT TRC-20 fees, address checks, Tether freezes, dApp and exchange rankings.
Available components
Last scanned (21 hours ago)
Scores higher than 88% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1236 tokens (~176/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Nov 26 +1
- Stability: 0.97 → pass security
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://tronorb.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tronorb.com | CN=WE1,O=Google Trust Services,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d3f1ddad720b09ee13c8d51b6618ce3c |
| SANs: tronorb.com, www.tronorb.com, *.www.tronorb.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tronorb.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| tronorb.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| content-security-policy | frame-ancestors 'none' |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tronorb.com/mcp | Verified | 200 | |
| http (plaintext) | http://tronorb.com/mcp | HTTPS enforced | 301 | https://tronorb.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_address Check a TRON address ~204
Check a TRON address before sending USDT: whether Tether froze it (read from the USDT contract), fraud and risk flags from TRONSCAN, whether it is activated, TRX/USDT balances, age and activity, token approvals, and what a USDT transfer to it would cost. A clean result does not guarantee the recipient is safe. Use it when the user gives a specific T… address; for network-wide freeze statistics use get_usdt_freezes. Returns one JSON object with a source page. Live on-chain read, cached for 60 seconds; limited to 10 checks per minute per IP. Errors on an invalid address.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | TRON address to check, in base58 (starts with T, 34 characters), e.g. TNiq9AXBp9EjUqhDhrwrfvAA8U3GUQZH81. Hex (41…) and EVM 0x addresses are rejected. |
No output schema declared.
No examples provided.
compare_usdt_networks USDT on TRON vs other networks ~126
Compare USDT across TRON, Ethereum, BNB Chain, Polygon and Solana: USDT supply on each network, live cost of one USDT transfer in USD (TRON: TRX burned without energy), extra cost for a first-time recipient, and block time. Use it when the user asks which network is cheapest or compares TRC-20 with ERC-20/BEP-20; for a detailed TRON-only breakdown (with and without energy) use get_usdt_fee. Returns one row per network. Fees refresh every few minutes; supply daily.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_network_stats TRON network stats ~127
TRON network overview: TRX price and market cap, DeFi TVL, daily active accounts, transactions and USDT transfers (latest complete day with 30-day change), current block height and TPS, energy and bandwidth prices, and Stake 2.0 energy per staked TRX. Use it for general "how is TRON doing" questions; for the cost of a USDT transfer prefer get_usdt_fee, which gives the full breakdown. Daily metrics update once a day (the last complete UTC day); price, block height and energy price refresh every few minutes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usdt_fee USDT TRC-20 transfer fee ~166
Live cost of one USDT (TRC-20) transfer on TRON: TRX burned when the sender has no energy (to an address that already holds USDT and to a new one), what it costs with enough staked or rented energy, the current energy and bandwidth prices, address activation cost and how much TRX must be staked to cover one transfer a day. Includes why the fee changes between days and wallets. Use it for "how much does it cost to send USDT" questions on TRON; for the fee to one specific recipient use check_address, and for other networks use compare_usdt_networks. Returns USD and TRX amounts plus a source page. Energy price refreshes every few minutes; results are cached for about a minute.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_usdt_freezes USDT freezes on TRON ~142
Addresses frozen (blacklisted) by Tether and other stablecoin issuers on TRON: total count, freezes in the last 30 and 365 days, stablecoins locked on frozen addresses, and the most recent and largest frozen addresses. Use it for questions about Tether blacklisting trends or recent freezes; to check whether one particular address is frozen use check_address instead. Each listed freeze has address, stablecoin, frozen_at date and the balance locked; the response includes updated_at.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many of the most recent and of the largest freezes to return (each list gets this many). Totals are always included. |
No output schema declared.
No examples provided.
list_projects TRON dApps, exchanges, wallets and services ~226
Ranked TronOrb directory: dApps by TVL on TRON, centralized exchanges by TRON reserves, wallets, and services (energy rental, exchangers, payment gateways, bots, explorers). Optionally filter by category (e.g. "DEX", "Lending", "Energy Rental"). Use it to browse or rank a whole section; to find one project by name use search_tronorb. Each entry has name, category, tagline, website and its TronOrb page; dapps and exchanges also get TVL or reserves with 7- and 30-day change (wallets and services have no metric and are ordered by listing date). Rankings refresh hourly. Returns an empty list for an unknown category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category name, e.g. "DEX", "Lending", "Energy Rental", "Payment Gateway" |
| limit | integer | – | Maximum number of entries to return, highest ranked first |
| type | string | yes | Directory section: dapps (ranked by TVL), exchanges (by TRON reserves), wallets or services |
No output schema declared.
No examples provided.
search_tronorb Search TronOrb ~123
Search TronOrb for TRON dApps, tokens, exchanges, wallets, services and guides by name. Returns up to 12 matching pages with kind, name, a short detail and a key number (TVL or market cap). Use it when the user names a specific project, token or topic; to rank a whole section use list_projects. An empty results array means nothing on TronOrb matches — try a shorter or different name.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Name or keyword, e.g. "SunSwap", "USDD", "energy rental" |
No output schema declared.
No examples provided.
How do I install the TronOrb — TRON analytics MCP server?
TronOrb — TRON analytics is a hosted endpoint at https://tronorb.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · tronorb.com
claude mcp add --transport http com-tronorb-mcp 'https://tronorb.com/mcp'
What is the TronOrb — TRON analytics MCP server?
TronOrb — TRON analytics is an MCP server listed in the public MCP registry as com.tronorb/mcp. Live TRON data: USDT TRC-20 fees, address checks, Tether freezes, dApp and exchange rankings. This page covers its hosted endpoint (https://tronorb.com/mcp).
Is the TronOrb — TRON analytics MCP server safe to use?
TronOrb — TRON analytics scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the TronOrb — TRON analytics MCP server expose?
TronOrb — TRON analytics exposes 7 tools: get_usdt_fee, check_address, get_usdt_freezes, list_projects, get_network_stats, and 2 more. Their descriptions and schemas cost roughly 1,114 tokens of context every time the server is loaded.
Does the TronOrb — TRON analytics MCP server require authentication?
No. We connected to TronOrb — TRON analytics without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TronOrb — TRON analytics MCP server still maintained?
TronOrb — TRON analytics is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the TronOrb — TRON analytics MCP server?
VerifyMCP ran 13 checks on TronOrb — TRON analytics, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.