TronSave
REMOTE · MCP.TRONSAVE.IO · 3 COMPONENTS
Buy, sell and extend TRON Energy/Bandwidth on the TronSave market. Quotes need no login.
Available components
Last scanned (17 hours ago)
Scores higher than 81% 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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (tronsave_sell_order_manual). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 10580 tokens (~195/item across 54 items; 53 tools + 1 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 Management97
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 2 breaking changes, 0 auth/transport breaks, 24 additions. See how to fix → Fail
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 55 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 18 Nov 26 +2
- HSTS header: fail → pass ▲ security
- 13 Nov 26 0
- Server version: 1.5.1 → 1.5.2 functional
- “tronsave_bulk_create_internal_orders” reworded the description of “paymentAmount” cosmetic
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97.
- 10 Nov 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 97 to 93.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97.
- 8 Nov 26 −1
No change was recorded against any check on this day. Stability & Change Management went from 97 to 93.
- 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
- 4 Nov 26 +1
- Tool “tronsave_create_order” rewrote its description, which is the text the model reads security
- Tool “tronsave_estimate_buy_resource” rewrote its description, which is the text the model reads security
- Tool “tronsave_estimate_flash_unstake” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_flash_unstake_request” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_internal_account” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_market_overview” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_min_price” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_order” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_price_table” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_referral” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_seller_stats” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_system_info” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_telegram_notify_setting” rewrote its description, which is the text the model reads security
- Tool “tronsave_get_user_info” rewrote its description, which is the text the model reads security
- Tool “tronsave_internal_extend_delegates” rewrote its description, which is the text the model reads security
- Tool “tronsave_internal_order_book” rewrote its description, which is the text the model reads security
- Tool “tronsave_internal_order_details” rewrote its description, which is the text the model reads security
- Tool “tronsave_internal_order_estimate” rewrote its description, which is the text the model reads security
- Tool “tronsave_internal_order_history” rewrote its description, which is the text the model reads security
- Tool “tronsave_list_delegations” rewrote its description, which is the text the model reads security
- Tool “tronsave_list_extendable_receivers” rewrote its description, which is the text the model reads security
- Tool “tronsave_list_flash_unstake_orders” rewrote its description, which is the text the model reads security
- Tool “tronsave_list_internal_transactions” rewrote its description, which is the text the model reads security
- Tool “tronsave_list_notifications” rewrote its description, which is the text the model reads security
- Tool “tronsave_list_order_books” rewrote its description, which is the text the model reads security
- Tool “tronsave_list_orders” rewrote its description, which is the text the model reads security
- Tool “tronsave_mark_notifications_read” rewrote its description, which is the text the model reads security
- Schema quality: 172 → 195 ▼ functional
- Tool coverage: 86% → 100% ▲ functional
- Server version: 1.4.1 → 1.5.1 functional
- Server version: 1.4.0 → 1.4.1 functional
- “tronsave_list_internal_transactions” reworded the description of “offset” cosmetic
- “tronsave_bulk_create_internal_orders” reworded the description of “resourceType” cosmetic
- “tronsave_get_price_table” reworded the description of “resourceType” cosmetic
- “tronsave_get_referral” reworded the description of “limit” cosmetic
- “tronsave_get_referral” reworded the description of “offset” cosmetic
- “tronsave_list_auto_buy_settings” reworded the description of “offset” cosmetic
- “tronsave_list_delegations” reworded the description of “filterByResourceType” cosmetic
- “tronsave_list_delegations” reworded the description of “filterByTypeDelegate” cosmetic
- “tronsave_list_delegations” reworded the description of “offset” cosmetic
- “tronsave_list_delegations” reworded the description of “timeFilterBy” cosmetic
- “tronsave_list_extendable_receivers” reworded the description of “resourceType” cosmetic
- “tronsave_list_flash_unstake_orders” reworded the description of “kind” cosmetic
- “tronsave_list_flash_unstake_orders” reworded the description of “limit” cosmetic
- “tronsave_list_flash_unstake_orders” reworded the description of “offset” cosmetic
- “tronsave_list_internal_transactions” reworded the description of “limit” cosmetic
- “tronsave_list_notifications” reworded the description of “limit” cosmetic
- “tronsave_list_notifications” reworded the description of “offset” cosmetic
- “tronsave_list_notifications” reworded the description of “unreadOnly” cosmetic
- “tronsave_register_auto_sell” reworded the description of “addOnFeature” cosmetic
- “tronsave_register_auto_sell” reworded the description of “paymentConfig” cosmetic
- “tronsave_register_auto_sell” reworded the description of “poolSetting” cosmetic
- “tronsave_suggest_create_order” reworded the description of “resourceType” cosmetic
- “tronsave_update_auto_sell_setting” reworded the description of “addOnFeature” cosmetic
- “tronsave_update_auto_sell_setting” reworded the description of “paymentConfig” cosmetic
- “tronsave_update_auto_sell_setting” reworded the description of “poolSetting” cosmetic
- “tronsave_update_telegram_notify_setting” reworded the description of “buyerFilter” cosmetic
- “tronsave_update_telegram_notify_setting” reworded the description of “sellerFilter” cosmetic
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://mcp.tronsave.io/testnet/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tronsave.io | CN=WE1,O=Google Trust Services,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 162690863feb41390e2dbe04f240cc9a |
| SANs: tronsave.io, *.tronsave.io | ||||||
| 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 secure
Validation of mcp.tronsave.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| tronsave.io. | DS published | 2371 | 13 | Verified |
| mcp.tronsave.io. | Verified address RRset verified with the apex keys |
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; includeSubDomains; preload |
| content-security-policy | default-src 'self' http: https: ws: wss: data: blob: 'unsafe-inline'; frame-ancestors 'self'; |
| x-content-type-options | nosniff |
| referrer-policy | no-referrer-when-downgrade |
| permissions-policy | interest-cohort=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tronsave.io/testnet/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tronsave.io/testnet/mcp | HTTPS enforced | 301 | https://mcp.tronsave.io/testnet/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 →
tronsave_update_auto_buy_setting Update Auto-Buy Rule ~325
Change an auto-buy rule by id: pause or resume it with `isActive`, or change any of price cap, amount, duration, threshold and limits (only the fields you send change). Side effect: a resumed or loosened rule can start spending internal TRX again. Idempotent for the same arguments. Get ids from `tronsave_list_auto_buy_settings`. Requires a wallet signature identity.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSec | number | – | Delegation duration of each purchase, in seconds. |
| endActiveAt | integer | – | Optional Unix time in seconds when the rule stops. |
| id | string | yes | Rule id from `tronsave_list_auto_buy_settings`. |
| isActive | boolean | – | false pauses the rule, true resumes it. |
| limitBudgetInSun | string | – | Optional total budget cap in SUN (decimal string); must be greater than 10000000 (10 TRX). |
| limitInOrderCount | integer | – | Optional cap on the number of orders. |
| receiver | string | – | TRON base58 address that receives each delegation. |
| resourceAmount | number | – | Resource units bought each time the rule fires. |
| resourceType | string | – | ENERGY or BANDWIDTH. |
| startActiveAt | integer | – | Optional Unix time in seconds when the rule starts. |
| thresholdResourceAmount | number | – | Rule fires when the receiver's remaining resource drops below this many units (TronSave requires at least 100000). |
| unitPrice | string | – | Maximum unit price in SUN, as a decimal string. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | – |
| data | – | – | – |
| message | – | – | – |
| success | – | – | – |
No examples provided.
tronsave_update_auto_sell_setting Update Auto Sell Setting ~201
Update the existing auto-sell configuration with partial fields. Returns the updated `autoSettings` payload. Side effect: overwrites stored automation settings for the current user; not idempotent across different field sets. Requires a wallet signature identity. Use for INCREMENTAL changes after registration; read the baseline via `tronsave_get_user_auto_setting` to avoid accidental resets, and use `tronsave_register_auto_sell` only for first-time setup. Fails for invalid field combinations, unauthorized sessions, or policy constraints.
| Name | Type | Req | Description |
|---|---|---|---|
| addOnFeature | object | – | Optional extras: voting, auto-stake of idle TRX, suggest-sell hints. |
| paymentConfig | object | – | Where and how often seller earnings are paid out (address, DAILY/IMMEDIATE, payout window). |
| poolSetting | object | – | What the wallet sells automatically: per-resource price floor, duration bounds, minimum amount, reserve, and reclaim scope. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing. |
| data | – | – | Opaque server-defined payload (tx id, setting id, or status text). Treat as identifier-or-message; rely on `message` for human routing. |
| message | – | – | Human-readable status text. Populated even on success; localized error messages may appear here on failure. |
| success | – | – | Whether the mutation succeeded at the backend level. Always check this before reading `data`. |
No examples provided.
tronsave_update_order Update Order ~178
Update an open order by `orderId` with partial fields (`receiver`, `newPrice`). Returns `{ success, message, code }`. Side effect: overwrites live order parameters; not idempotent — each call with a different `newPrice` produces a new state. Requires a wallet signature identity (the order's owner). Prefer this over cancel+recreate when only price/receiver should change. Verify state with `tronsave_get_order` first; fails for already-fulfilled, already-cancelled, or non-editable orders.
| Name | Type | Req | Description |
|---|---|---|---|
| newPrice | number | – | Optional replacement unit price in SUN per resource unit. |
| orderId | string | yes | Target order id (`MObjectId`) to update. Order must still be open and editable. |
| receiver | string | – | Optional replacement receiver TRON address. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing. |
| message | – | – | Human-readable status text. Populated even on success; localized error messages may appear here on failure. |
| success | – | – | Whether the mutation succeeded at the backend level. Always check this before reading `data`. |
No examples provided.
tronsave_update_telegram_notify_setting Update Telegram Notification Settings ~132
Replace the Telegram alert filters. Send the COMPLETE `sellerFilter` and/or `buyerFilter` objects (read the current ones with `tronsave_get_telegram_notify_setting`, edit, send back); each range or value has `isEnabled` plus its numbers. Only changes which alerts are sent; no funds move. Idempotent. Requires a wallet signature identity and a linked Telegram account.
| Name | Type | Req | Description |
|---|---|---|---|
| buyerFilter | object | – | Complete buyer alert filter; omit to leave buyer alerts unchanged. |
| sellerFilter | object | – | Complete seller alert filter; omit to leave seller alerts unchanged. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | – |
| message | – | – | – |
| success | – | – | – |
No examples provided.
How do I install the TronSave MCP server?
TronSave is a hosted endpoint at https://mcp.tronsave.io/testnet/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 · mcp.tronsave.io
claude mcp add --transport http tronsave-mcp 'https://mcp.tronsave.io/testnet/mcp'
What is the TronSave MCP server?
TronSave is an MCP server listed in the public MCP registry as io.github.tronsave/mcp. Buy, sell and extend TRON Energy/Bandwidth on the TronSave market. Quotes need no login. This page covers its hosted endpoint (https://mcp.tronsave.io/testnet/mcp).
Is the TronSave MCP server safe to use?
TronSave scores 82 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 TronSave MCP server expose?
TronSave exposes 53 tools: tronsave_get_internal_account, tronsave_get_deposit_address, tronsave_internal_order_history, tronsave_internal_order_details, tronsave_internal_order_book, and 48 more. Their descriptions and schemas cost roughly 10,051 tokens of context every time the server is loaded.
Does the TronSave MCP server require authentication?
No. We connected to TronSave without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TronSave MCP server still maintained?
TronSave 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 TronSave MCP server?
VerifyMCP ran 13 checks on TronSave, 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.