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 (15 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.
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97.
- 7 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_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
- 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
- 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_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
- “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
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/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/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tronsave.io/mcp | HTTPS enforced | 301 | https://mcp.tronsave.io/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_bulk_create_internal_orders Bulk Buy For Many Receivers ~247
Buy the SAME amount of ENERGY or BANDWIDTH for several receiver addresses in one call, paid from the TronSave internal balance; returns one order id per receiver. Side effect: SPENDS `paymentAmount` SUN of the internal balance; not idempotent (a repeat buys again). Estimate one receiver with `tronsave_estimate_buy_resource` first and show the user receivers, amount and total cost before calling. Requires a wallet signature identity.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSec | number | yes | Delegation duration in seconds. |
| paymentAmount | number | yes | Total SUN for the whole batch = unitPrice x resourceAmount x number of receivers x ceil(durationSec / 86400) (so any rental under 1 day is charged as one full day), within 2%; a mismatch is rejected… |
| receivers | array | yes | Receiver addresses (1 to 50). |
| resourceAmount | number | yes | Resource units bought for EACH receiver. |
| resourceType | string | yes | Resource bought for every receiver. |
| sponsor | string | – | Optional sponsor or referral code. |
| unitPrice | number | yes | Unit price in SUN per resource unit, per receiver. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | – |
| data | – | – | – |
| message | – | – | – |
| success | – | – | – |
No examples provided.
tronsave_cancel_order Cancel Order ~163
Cancel an open order by `orderId`. Returns `{ success, message, code }`. Side effect: marks the order non-matchable and refunds locked balance per backend rules; effectively destructive on the live order. Idempotent — cancelling an already-cancelled order is a no-op success. Fails for fulfilled orders or unauthorized callers. Requires a wallet signature identity (the order's owner). Verify state with `tronsave_get_order` first; prefer `tronsave_update_order` when only price/receiver should change.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | Target order id (`MObjectId`) to cancel. Must be an active order owned/authorized by the current session; already-fulfilled or already-cancelled orders are expected to fail. |
| 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_create_auto_buy_setting Create Auto-Buy Rule ~317
Create a rule that automatically buys `resourceAmount` for `receiver` whenever its remaining resource falls below `thresholdResourceAmount`, paying up to `unitPrice` SUN per unit from the TronSave internal balance. Side effect: SPENDS internal TRX every time the rule fires until a budget/order limit or `endActiveAt` stops it; not idempotent (each call adds a rule). Confirm receiver, amounts, price cap and limits with the user first; prefer setting `limitBudgetInSun`. Requires a wallet signature identity.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSec | number | yes | Delegation duration of each purchase, in seconds. |
| endActiveAt | integer | – | Optional Unix time in seconds when the rule stops. |
| 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 | yes | TRON base58 address that receives each delegation. |
| resourceAmount | number | yes | Resource units bought each time the rule fires. |
| resourceType | string | yes | ENERGY or BANDWIDTH. |
| startActiveAt | integer | – | Optional Unix time in seconds when the rule starts. |
| thresholdResourceAmount | number | yes | Rule fires when the receiver's remaining resource drops below this many units (TronSave requires at least 100000). |
| unitPrice | string | yes | Maximum unit price in SUN, as a decimal string. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | – |
| message | – | – | – |
| success | – | – | – |
No examples provided.
tronsave_create_order Create Order ~587
Create a buy order for ENERGY/BANDWIDTH delegated to `orderReceiver`. SPENDS FUNDS — confirm the plan with the user first. API-key integrations paying from the internal balance can instead use `tronsave_internal_order_create` (FAST/MEDIUM/SLOW pricing, fill guards). Inputs: `orderResourceType`, `orderReceiver`, `orderUnitPrice` (SUN, not TRX), `orderDurationSec`, `orderResourceAmount`, `paymentPaymentAmount` (SUN), and `paymentMethod`: `internal` — debits the TronSave internal balance (needs an api-key login/header or a signature login whose wallet has an internal account); `onchain` — no login needed, but `paymentSignedTx` must be the user's wallet-signed TRX transfer to `systemDepositAddress`. Take price/amount/duration values from the latest `tronsave_estimate_buy_resource`. Returns `{ success, message, code, data.orderId }` — check `success`; verify with `tronsave_get_order` or `tronsave_list_orders`. Not idempotent: on a timeout, verify before retrying to avoid duplicate orders.
| Name | Type | Req | Description |
|---|---|---|---|
| orderDurationSec | integer | yes | Delegation duration in seconds. Must match the `durationSec` used in `tronsave_estimate_buy_resource`. |
| orderReceiver | string | yes | TRON base58 address (starts with T) that receives delegated resource. Same as `receiver` passed to `tronsave_estimate_buy_resource`. |
| orderResourceAmount | integer | yes | Amount of ENERGY or BANDWIDTH units to purchase. Same as `buyResourceAmount` in estimate when applicable. |
| orderResourceType | string | yes | Resource to buy: ENERGY (smart contracts) or BANDWIDTH (transactions). Must match `tronsave_estimate_buy_resource`. |
| orderUnitPrice | number | yes | Unit price in SUN per resource unit (NOT TRX). Use `unitPrice` from the latest `tronsave_estimate_buy_resource` for the same receiver, amount, and duration. |
| paymentMethod | string | yes | Payment method for this order: `onchain` (wallet signed tx) or `internal` (internal balance). |
| paymentPaymentAmount | number | yes | Total payment in SUN (1 TRX = 1e6 SUN). Use `estimateTrx` (SUN) from the latest `tronsave_estimate_buy_resource`. |
| paymentSignedTx | object | – | Required when `paymentMethod=onchain`: the user's wallet-signed TRX transfer of `paymentPaymentAmount` SUN to `systemDepositAddress` (from `tronsave_estimate_buy_resource`), TronWeb shape `{ txID, ra… |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing. |
| data | – | – | – |
| 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_delete_auto_buy_setting Delete Auto Buy Setting ~113
Permanently delete one auto-buy rule by `id` (`MObjectId`). Side effect: stops all future executions matching that rule; the rule cannot be restored. Idempotent — deleting a non-existent or already-removed id returns success. Requires a wallet signature identity. Use `tronsave_get_user_auto_setting` to list current rules first; prefer disabling/updating instead when reversibility is desired.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Auto-buy setting id (`MObjectId`) to delete. |
| 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_estimate_buy_resource Estimate Buy Resource ~338
Quote price and availability for buying ENERGY or BANDWIDTH for a receiver address before placing an order. This quote feeds `tronsave_create_order`; for `tronsave_internal_order_create` (API key) quote with `tronsave_internal_order_estimate`. Returns `{ unitPrice (SUN/unit), durationSec, estimateTrx (total cost in SUN), availableResource, systemDepositAddress }` — map them to `tronsave_create_order` as `orderUnitPrice`, `orderDurationSec`, `paymentPaymentAmount`. Defaults: ENERGY, 100000 units (1000 for BANDWIDTH), 900 s. Read-only and safe to call repeatedly; no session is required, but backend rate limits apply. For order-book depth use `tronsave_list_order_books`; for the minimum unit price only use `tronsave_get_min_price`.
| Name | Type | Req | Description |
|---|---|---|---|
| allowPartialFill | boolean | – | Allow partial fill of the order. |
| buyResourceAmount | integer | – | Resource units to buy. Default 100000 for ENERGY and 1000 for BANDWIDTH. |
| durationSec | integer | – | Delegation duration in seconds. Default 900 (15 minutes). |
| minResourceDelegateRequiredAmount | number | – | Minimum resource amount per matching provider. |
| receiver | string | – | TRON address that will receive the resource. Strongly recommended: quotes depend on it. |
| resourceType | string | – | Resource type to buy. Default ENERGY. |
| unitPrice | number | – | Desired unit price in SUN. Values below the market minimum are raised to the minimum. Omit for the MEDIUM market price. |
| Name | Type | Req | Description |
|---|---|---|---|
| availableResource | – | – | Resource units currently available at this price; if lower than requested, the order may fill partially. |
| durationSec | – | – | Delegation duration in seconds → `orderDurationSec`. |
| estimateTrx | – | – | Estimated total cost in SUN (despite the name; TRX = value / 1e6) → `paymentPaymentAmount`. |
| systemDepositAddress | – | – | TronSave deposit address; destination of the signed TRX transfer for `paymentMethod=onchain`. |
| unitPrice | – | – | Quoted unit price in SUN per resource unit → `orderUnitPrice`. |
No examples provided.
tronsave_estimate_flash_unstake Estimate Flash Unstake ~117
Estimate what an address would receive by flash-unstaking all its staked TRX now: total staked, fee percentage, payout, delegations to reclaim and the minimum unstake amount. Nothing is submitted. Use before requesting a flash unstake; check an existing request with `tronsave_get_flash_unstake_request`. Public (any address), read-only. Fails with 404 when the address has nothing staked.
| Name | Type | Req | Description |
|---|---|---|---|
| requester | string | yes | TRON base58 address that owns the stake. |
| Name | Type | Req | Description |
|---|---|---|---|
| feePercentage | – | – | – |
| payoutAmount | – | – | – |
No examples provided.
tronsave_generate_api_key Generate API Key ~107
Generate a new internal API key credential for the current user. Returns `data` containing the issued key — show it to the user once and tell them to store it securely; do not repeat it in later messages. Side effect: issues secret material; not idempotent — each call mints a fresh key and may invalidate the previous one per backend policy. Requires a wallet signature identity. Sensitive output — never log raw keys; unauthorized sessions or policy checks may reject issuance.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing. |
| data | – | – | For `generateApiKey`: the freshly issued internal API key — treat as SECRET, store securely. For `revokeApiKey`: server-defined confirmation string (no key material). |
| 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_get_account_resources Account Resources ~84
Read the on-chain staked and delegatable ENERGY/BANDWIDTH of a TRON address, plus its TRX balance (SUN string). Use to check whether a wallet can sell, or how much resource it holds. Public (any address), read-only; does not need a login.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | TRON base58 address to inspect. |
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | – |
| balance | – | – | – |
| resourcesV2 | – | – | – |
No examples provided.
tronsave_get_agency_bot Agency Bot ~96
Read the logged-in user's Telegram agency bot (resale bot): name, username, status (PENDING, ACTIVE, INACTIVE, BLOCKED, REJECTED), rewards (total and unpaid) and order / resource statistics. `bot` is null when none is registered. The bot token is never returned. Requires a wallet signature identity. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| timeFilterBy | string | – | Statistics window. |
| Name | Type | Req | Description |
|---|---|---|---|
| bot | – | – | – |
No examples provided.
tronsave_get_deposit_address Get Deposit Address ~163
Fetches the specific deposit address for the TronSave internal account. Requires an internal API key: `tronsave_login` (api-key mode, or signature mode for a wallet with an internal account) or an `Authorization: ApiKey <key>` client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. Trigger this tool if the user asks for a deposit address or needs to top up their TronSave TRX balance. Constraints: 1) TRX only; 2) Minimum deposit amount is 10 TRX; 3) Read-only operation.
| Name | Type | Req | Description |
|---|---|---|---|
| amountTrx | number | yes | Amount of TRX the user intends to deposit (minimum 10 TRX). |
| Name | Type | Req | Description |
|---|---|---|---|
| amountTrx | – | – | Amount of TRX the user intends to deposit (echoed back). |
| depositAddress | – | – | TRON base58 deposit address; send TRX here to top up the TronSave internal balance. |
| minimumDepositTrx | – | – | Minimum accepted deposit in TRX. |
No examples provided.
tronsave_get_flash_unstake_request My Flash Unstake Request ~104
Read the logged-in user's flash-unstake request (selling staked TRX early for an immediate payout): state, payout state, amounts and release progress. `request` is null when there is none. Use for the user's own request; to preview a payout before requesting use `tronsave_estimate_flash_unstake`, to browse everyone's orders use `tronsave_list_flash_unstake_orders`. Requires a wallet signature identity. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| request | – | – | – |
No examples provided.
tronsave_get_internal_account Internal Account Information ~167
Retrieve the Tronsave internal account profile for the current logged-in session (wallet/represent address, balances, deposit address). Requires an internal API key: `tronsave_login` (api-key mode, or signature mode for a wallet with an internal account) or an `Authorization: ApiKey <key>` client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. Use when the user needs their linked address or balance; for the full wallet profile use `tronsave_get_user_info`, for the ledger of deposits and payments `tronsave_list_internal_transactions`. Returns `{ id, balance (SUN string), representAddress, depositAddress }`; any API key in the payload is masked. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | – | – | MASKED internal API key; the full key is never returned. |
| balance | – | – | Internal balance in SUN as a decimal string (TRX = SUN / 1e6). |
| depositAddress | – | – | TRON base58 deposit address; send TRX here to top up the internal balance (min 10 TRX). |
| id | – | – | Internal account id. |
| representAddress | – | – | TRON base58 address that represents (owns) the internal account. |
No examples provided.
tronsave_get_market_overview Market Overview ~116
Read the TronSave market summary: resource currently available and total listed for ENERGY and BANDWIDTH, number of pooled sellers, and seller APY (percent). Use for a quick 'how is the market' answer before pricing; for prices use `tronsave_get_price_table` (grid) or `tronsave_estimate_buy_resource` (one quote), for depth by price use `tronsave_list_order_books`. Public, read-only. Data refreshes about every TRON block (3 s).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| apy | – | – | – |
| resources | – | – | – |
| totalPool | – | – | Number of sellers in the pool. |
No examples provided.
tronsave_get_min_price Get Minimum Unit Price ~284
Quote the minimum unit price for a buy. Use when only the floor price matters; for a full purchase quote use `tronsave_estimate_buy_resource`, for a grid across amounts and durations `tronsave_get_price_table`. Returns `{ minPrice }` (SUN per resource unit; per day when `durationSec` >= 86400) from GraphQL `market.estimateMinPrice` for the given `resourceType`, `buyAmount`, and `durationSec`. Optional `address` scopes context when the API supports it. No login required. Read-only and idempotent. Pair with `tronsave_estimate_buy_resource` for full buy quotes and `tronsave_list_order_books` for depth buckets.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional TRON base58 address (`TronAddress`). When omitted, the server uses anonymous/global market context. |
| buyAmount | number | – | Resource amount to price (same units as order book / delegate amounts for that resource type). Default 100000 for ENERGY and 1000 for BANDWIDTH |
| durationSec | number | – | Delegation window in seconds; must match the duration you plan to use on a real order for comparable quotes. Default 15 minutes |
| resourceType | string | – | Market leg: `ENERGY` or `BANDWIDTH`. Default ENERGY |
| Name | Type | Req | Description |
|---|---|---|---|
| minPrice | – | – | Estimated minimum unit price in SUN for the given `resourceType`, `buyAmount`, and `durationSec`; align with `tronsave_estimate_buy_resource` and order `unitPrice` conventions (same as GraphQL `marke… |
No examples provided.
tronsave_get_order Order Detail ~136
Read one order by `id` and return its full snapshot for NORMAL, FAST, or EXTEND order types. With only an API key, use `tronsave_internal_order_details` instead. Use this as the source of truth before `tronsave_update_order`, `tronsave_sell_order_manual`, or `tronsave_cancel_order` to avoid acting on stale state. Requires a wallet signature identity. Read-only and idempotent.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Target order id (`MObjectId`) to inspect. Use this to confirm current status/price before update, sell, or cancel actions. |
| Name | Type | Req | Description |
|---|---|---|---|
| order | – | – | – |
No examples provided.
tronsave_get_price_table Resource Price Table ~186
Read the price grid for ENERGY or BANDWIDTH: `prices[i][j]` is the unit price in SUN for `amounts[i]` resource units rented for `durations[j]` (e.g. '15m', '1h', '1d'). Durations of 1 day or longer are priced per day: '30d' at 40 SUN costs 40 x 30 SUN per unit in total. Use to compare cost across amounts and durations in one call. For an exact quote on one purchase use `tronsave_estimate_buy_resource`; for only the floor price use `tronsave_get_min_price`. Public, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional receiver address; prices can depend on the account. |
| resourceType | string | yes | ENERGY (smart-contract calls) or BANDWIDTH (plain transfers). |
| Name | Type | Req | Description |
|---|---|---|---|
| amounts | – | – | – |
| durations | – | – | – |
| prices | – | – | – |
No examples provided.
tronsave_get_referral Referral Program ~156
Read the logged-in user's referral status: own referral code, sponsor, referral counts, bonus earned and remaining (SUN strings), rank, the referral list (PENDING/ACTIVE) and recent commission payouts. Use for referral questions only; account profile is `tronsave_get_user_info`. `offset`/`limit` page the referral list and the payout list together. Requires a wallet signature identity. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| filterBy | string | – | Only referrals in this status. |
| limit | integer | – | Rows per list (default 10, max 50). |
| offset | integer | – | Number of rows of each list to skip for pagination (default 0); add `limit` to page forward. |
| Name | Type | Req | Description |
|---|---|---|---|
| totalRef | – | – | – |
| userRefCode | – | – | – |
No examples provided.
tronsave_get_seller_stats Seller Statistics ~120
Read the logged-in seller's lifetime totals (delegations, resource delegated, TRX earned, average price per resource) and a daily earnings chart split into auto, manual, exclusive and extend delegations. Use for 'how much did I earn' totals; for the individual delegations behind them use `tronsave_list_delegations`. Requires a wallet signature identity. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| resourceType | string | – | Resource the chart is drawn for. |
| timeFilterBy | string | – | Chart window; default D30. |
| Name | Type | Req | Description |
|---|---|---|---|
| chart | – | – | – |
| stats | – | – | – |
No examples provided.
tronsave_get_session_status Session Status ~90
Report the current authentication state without calling TronSave: `authMode` (none | api-key | signature), `source` (login | header), `walletAddress`, `hasInternalApiKey`, `expiresAt`, network, and which tool groups are available now. Call this first when unsure whether to log in, and after `SESSION_REQUIRED` / `INVALID_SESSION_TYPE` errors.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| authMode | – | – | `signature` unlocks wallet tools; `api-key` unlocks internal-account tools. |
| authenticated | – | – | Whether any credential is active for this request. |
| availableNow | – | – | Tool groups callable with the current auth. |
| expiresAt | – | – | Login expiry for `source=login`. |
| hasInternalApiKey | – | – | Whether an internal API key is available for api-key tools. |
| headerAuthError | – | – | Present when header credentials were sent but rejected. |
| network | – | – | Network served by this endpoint. |
| source | – | – | `login` = `tronsave_login` session, `header` = static Authorization header, `oauth` = OAuth sign-in by the client app. |
| walletAddress | – | – | Wallet of the signature identity, if any. |
No examples provided.
tronsave_get_sign_message Get Signature Message ~96
Step 1 of wallet login. Returns `{ message, timestamp }`: ask the user to sign `message` with their TRON wallet (TronWeb `signMessageV2`, TronLink, etc.), then call `tronsave_login` with `signature: "<signature>_<timestamp>"`. Signing the plain decimal `timestamp` text is also accepted. No auth needed; no side effects on the account.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| message | – | – | Hex-encoded nonce message to sign client-side with the user's TRON wallet. The signature must be produced over THIS exact message (case-sensitive). |
| timestamp | – | – | Unix epoch seconds corresponding to `message`. Pair it with the wallet signature in `<signature>_<timestamp>` form when calling `tronsave_login` (signature mode). This endpoint is a convenience helpe… |
No examples provided.
tronsave_get_system_info Protocol Parameters ~118
Read TronSave and TRON protocol parameters: latest block, minimum buy amounts, TRX burn rates per unit, dynamic buy/lowest prices, the system deposit address, max lock period and the energy cost of a USDT transfer. Use to size purchases (minimums) and to compare renting with burning TRX. For market prices use `tronsave_get_price_table` or `tronsave_estimate_buy_resource`; for supply and APY use `tronsave_get_market_overview`. Public, read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| burningBandwidthRate | – | – | – |
| burningEnergyRate | – | – | SUN burned per energy unit when none is rented. |
| lastBlock | – | – | – |
| minBuyBandwidthAmount | – | – | – |
| minBuyEnergyAmount | – | – | – |
| systemDepositAddress | – | – | – |
| usdtTransferEnergyValue | – | – | – |
No examples provided.
tronsave_get_telegram_notify_setting Telegram Notification Settings ~112
Read the Telegram alert filters of the logged-in user: seller alerts (remaining amount, duration, price and APY ranges, unlocked-only) and buyer alerts (reclaim warning time, low energy / bandwidth thresholds). `setting` is null when Telegram is not linked. Read these before changing them with `tronsave_update_telegram_notify_setting` (which replaces whole filter objects). For in-app alerts use `tronsave_list_notifications`. Requires a wallet signature identity. Read-only.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| setting | – | – | – |
No examples provided.
tronsave_get_user_auto_setting User Auto Setting ~80
Read the current user's auto-sell configuration (`autoSettings`). Returns the full `autoSettings` object — call this before `tronsave_register_auto_sell` or `tronsave_update_auto_sell_setting` to avoid overwriting fields you do not intend to change. Requires a wallet signature identity. Read-only and idempotent.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| bandwidth | – | – | Bandwidth auto-sell pool snapshot; null when bandwidth automation is disabled. |
| energy | – | – | Energy auto-sell pool snapshot; null when energy automation is disabled. |
| permitOperations | – | – | Permission rows enabled for this user; null/empty when no automation has been configured. |
| reclaimOnlyTronSave | – | – | Reclaim flag — when `true`, only TronSave-managed delegations are reclaimed automatically. |
| suggestSell | – | – | Whether suggest-sell UX hints are enabled. |
| vote | – | – | Whether vote-related automation is enabled for the wallet. |
| withdrawVote | – | – | Withdraw-vote configuration as a backend-defined string; semantics from TronSave docs. |
No examples provided.
tronsave_get_user_info User Information ~157
Read the current authenticated user's profile and linked TronSave internal account. For the internal balance alone use `tronsave_get_internal_account`; for referral data `tronsave_get_referral`. Returns `{ caller, address, balance (SUN string), info, internalAccount }` — `info` carries referral/contact metadata and may be null; `internalAccount` is null when the wallet has not provisioned a TronSave internal balance yet. `internalAccount.apiKey` is masked. Requires a wallet signature identity. Read-only and idempotent. Use `tronsave_get_user_auto_setting` for the auto-sell config or `tronsave_get_user_permissions` for permission flags when the full profile is unnecessary.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| address | – | – | TRON base58 address |
| balance | – | – | Amount in SUN, onchain balance of the address |
| caller | – | – | TRON base58 address of the caller |
| info | – | – | – |
| internalAccount | – | – | – |
No examples provided.
tronsave_get_user_permissions User Permissions ~74
Read the enabled permission operations (`autoSettings.permitOperations`) for the authenticated user. Returns `{ permitOperations: string[] }` — use it before mutating auto-sell or auto-buy rules to confirm the action is allowed for the wallet. Requires a wallet signature identity. Read-only and idempotent.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| permitOperations | – | – | Permission rows enabled for this user; defaults to `[]` when nothing is configured. |
No examples provided.
tronsave_internal_create_extend_request Submit Delegation Extension ~314
Submit an extension request for existing delegated resources on TronSave via authenticated REST `POST /v2/extend-request`. Requires an internal API key: `tronsave_login` (api-key mode, or signature mode for a wallet with an internal account) or an `Authorization: ApiKey <key>` client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. Side effect: creates an extension order and may commit TRX from the internal account. `extendData` must follow the REST contract (see schema on each row). Get `extendData` from `tronsave_internal_extend_delegates` (STEP 1) and pass the rows unchanged. Do not copy rows from `tronsave_list_extendable_delegates` (GraphQL); that payload shape differs and is for market discovery only.
| Name | Type | Req | Description |
|---|---|---|---|
| extendData | array | yes | Delegator-level rows for `POST /v2/extend-request`. Each row matches TronSave's REST extend contract (delegator, isExtend, extraAmount, extendTo in Unix seconds)—typically taken from `extendData` ret… |
| receiver | string | yes | TRON base58 address of the account that receives the delegated resource. |
| resourceType | string | – | Resource type. Default ENERGY when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | – | – | New extension order id (hex string). |
No examples provided.
tronsave_internal_extend_delegates List Extendable Delegations ~328
Return extendable delegations for a receiver plus an `extendData` payload for the extension flow. Requires an internal API key: `tronsave_login` (api-key mode, or signature mode for a wallet with an internal account) or an `Authorization: ApiKey <key>` client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. Use as STEP 1 before `tronsave_internal_create_extend_request` when the user wants to extend existing delegation time. This is the only source of submittable `extendData`; `tronsave_list_extendable_delegates` is a public market view, and `tronsave_list_extendable_receivers` finds which receiver to extend. Read-only; does not submit anything. FRESHNESS: pricing/availability change within seconds — run immediately before extending and pass the returned `extendData` unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| extendTo | integer | yes | Target end time as Unix epoch SECONDS (UTC) for the extended delegation, e.g. now + 86400 for one more day. Milliseconds are rejected by TronSave (INVALID_EXTEND_TIME). |
| maxPriceAccepted | number | – | Maximum unit price in SUN you are willing to pay for the extension. |
| receiver | string | yes | TRON base58 address of the account that receives the delegated resource. |
| requester | string | – | TRON base58 requester; defaults to the API key account when omitted. |
| resourceType | string | – | Resource type. Default ENERGY when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| extendData | – | – | Delegations to extend; pass unchanged into internal_create_extend_request `extendData`. |
| extendOrderBook | – | – | Order book for extend. |
| isAbleToExtend | – | – | Whether balance is sufficient to extend. |
| totalAvailableExtendAmount | – | – | Total available amount to extend. |
| totalDelegateAmount | – | – | Total delegated resource amount. |
| totalEstimateTrx | – | – | Total estimated TRX cost in SUN. |
| yourBalance | – | – | Current account balance in SUN. |
No examples provided.
tronsave_internal_order_book Internal Market Order Book ~264
Return the current TronSave market depth/price tiers for ENERGY or BANDWIDTH via the api-key REST endpoint. Requires an internal API key: `tronsave_login` (api-key mode, or signature mode for a wallet with an internal account) or an `Authorization: ApiKey <key>` client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. Use before `tronsave_internal_order_create` or `tronsave_internal_order_estimate` when the user needs live prices or liquidity. Same depth as the public `tronsave_list_order_books`, plus SLOW/MEDIUM/FAST price tiers; use the public tool when there is no API key. Read-only. FRESHNESS: live market depth can change roughly every 3 seconds (one TRON block) — re-read immediately before placing an order.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional TRON base58 address filter for the receiver. |
| durationSec | integer | – | Delegation duration window in seconds for the quote. |
| minDelegateAmount | number | – | Minimum resource amount per offer level to include (resource units, not SUN). |
| resourceType | string | – | Resource type. Default ENERGY when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| availableResource | – | – | Available resource at the quoted tiers. |
| data | – | – | Order book entries sorted by price. |
| fast | – | – | FAST price tier (SUN). |
| medium | – | – | MEDIUM price tier (SUN). |
| slow | – | – | SLOW price tier (SUN). |
No examples provided.
tronsave_internal_order_create Create Energy or Bandwidth Order (Internal) ~317
Place a new buy order for ENERGY or BANDWIDTH on TronSave, paid from the internal account balance. Requires an internal API key: `tronsave_login` (api-key mode, or signature mode for a wallet with an internal account) or an `Authorization: ApiKey <key>` client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. Side effect: SPENDS internal TRX balance and creates a live order; not idempotent — each call places a new order. This is the api-key/internal path; for the signature-session market path use `tronsave_create_order`. Always derive `unitPrice` from the latest `tronsave_internal_order_estimate` (re-estimate immediately before submitting — quotes older than a few seconds may be stale and revert). Returns `{ orderId }`.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSec | integer | – | Delegation duration in seconds. Default 259200 (3 days) when omitted. |
| options | object | – | Optional execution guards and fill behavior. |
| receiver | string | yes | TRON base58 address that will receive the resource. |
| resourceAmount | number | yes | Amount of resource to purchase (resource units). |
| resourceType | string | – | Resource type. Default ENERGY when omitted. |
| sponsor | string | – | Optional sponsor or referral code. |
| unitPrice | – | – | Pricing: FAST | MEDIUM | SLOW strategy, or exact unit price in SUN per resource unit. Default MEDIUM when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | – | – | New extension order id (hex string). |
No examples provided.
tronsave_internal_order_details Internal Order Details ~184
Fetch full details for one internal-account order by order ID. Requires an internal API key: `tronsave_login` (api-key mode, or signature mode for a wallet with an internal account) or an `Authorization: ApiKey <key>` client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. Use when monitoring fulfillment after `tronsave_internal_order_create`, or when the user asks for status on a specific order id. API-key path; with a wallet signature `tronsave_get_order` returns the same order. Read-only. FRESHNESS: order state changes within seconds as the market matches — re-read immediately before acting.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | TronSave order ID (hex string), e.g. value returned in internal.order.create response data.orderId. |
| Name | Type | Req | Description |
|---|---|---|---|
| allowPartialFill | – | – | Whether partial fill is allowed. |
| createdAt | – | – | Order created time (Unix epoch ms or ISO-8601, endpoint-dependent). |
| delegates | – | – | Delegations fulfilling this order. |
| durationSec | – | – | Delegated duration in seconds. |
| fulfilledPercent | – | – | 0 = pending, 1-99 = partial, 100 = fully matched. |
| id | – | – | TronSave order ID (hex string). |
| orderType | – | – | Order type (NORMAL | FAST | EXTEND). |
| payoutAmount | – | – | Payout amount in SUN. |
| price | – | – | Unit price in SUN. |
| receiver | – | – | TRON base58 receiver address. |
| remainAmount | – | – | Remaining unfulfilled amount. |
| requester | – | – | TRON base58 requester address. |
| resourceAmount | – | – | Resource amount of order. |
| resourceType | – | – | Resource type. |
| status | – | – | Order status. |
No examples provided.
tronsave_internal_order_estimate Estimate TRX Cost Before Order ~318
Estimate the TRX cost and availability for a buy order before submitting it (api-key internal account). Requires an internal API key: `tronsave_login` (api-key mode, or signature mode for a wallet with an internal account) or an `Authorization: ApiKey <key>` client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. Use when the user wants a quote or price check; feed the result into `tronsave_internal_order_create`. Quotes for `tronsave_create_order` come from `tronsave_estimate_buy_resource` instead. Read-only. FRESHNESS: `unitPrice`/`estimateTrx` are live and can change roughly every 3 seconds — re-estimate immediately before creating the order.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSec | integer | – | Delegation duration in seconds. Default 259200 (3 days) when omitted. |
| options | object | – | Optional flags that affect matching behavior for the estimate. |
| receiver | string | – | TRON base58 address that will receive the resource. |
| requester | string | – | TRON base58 requester; defaults to the API key account when omitted. |
| resourceAmount | number | yes | Amount of resource to purchase (resource units). |
| resourceType | string | – | Resource type. Default ENERGY when omitted. |
| unitPrice | – | – | Pricing: FAST | MEDIUM | SLOW strategy, or exact unit price in SUN per resource unit. Default MEDIUM when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| availableResource | – | – | Available resource amount. |
| durationSec | – | – | Delegated duration in seconds. |
| estimateTrx | – | – | Estimated TRX cost in SUN. |
| unitPrice | – | – | Unit price in SUN. |
No examples provided.
tronsave_internal_order_history Internal Account Order History ~208
List paginated order history for the internal account linked to the API key, newest first. Requires an internal API key: `tronsave_login` (api-key mode, or signature mode for a wallet with an internal account) or an `Authorization: ApiKey <key>` client header. Never pass API keys as tool arguments; the server forwards the key from the session/header to TronSave. Use when the user asks about past purchases, fulfillment, payouts, or delegates on their internal account. This is the API-key path; wallet-signature sessions can also use `tronsave_list_orders` with `isOnlyMyOrder`. Read-only. Pair with `tronsave_internal_order_details` for a single order's full snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page index, 0-based. Omit for first page (default 0). |
| pageSize | integer | – | Orders per page. Default 10 when omitted. Typical range 1–100. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | – | – | Orders on this page, newest first. |
| total | – | – | Total orders matching the query (for pagination). |
No examples provided.
tronsave_list_auto_buy_settings Auto-Buy Rules ~134
List the logged-in user's auto-buy rules: receiver, resource, unit price cap, threshold, budget/order limits, totals bought and active state. Use before `tronsave_update_auto_buy_setting` or `tronsave_delete_auto_buy_setting` to get rule ids. Requires a wallet signature identity. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| filterBy | string | – | Only rules for this resource. |
| limit | integer | – | Rows to return (default 10, max 10). |
| offset | integer | – | Number of rules to skip for pagination (default 0); add `limit` to page forward. |
| Name | Type | Req | Description |
|---|---|---|---|
| settings | – | – | – |
No examples provided.
tronsave_list_delegations Delegation History ~266
List the logged-in seller's delegations (resource sent to buyers): amount, TRX amount, duration, unit price, type (AUTO, MANUAL, EXTEND, FAST), status and payout. Newest first; page with `offset`/`limit`. Use for a seller's per-delegation history; for earnings totals use `tronsave_get_seller_stats`, for orders the user bought use `tronsave_list_orders` (`isOnlyMyOrder`). Requires a wallet signature identity. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| filterByResourceType | string | – | Only ENERGY or only BANDWIDTH delegations; omit for both. |
| filterByTypeDelegate | string | – | Only this delegation type: AUTO (auto-sell pool), MANUAL (`tronsave_sell_order_manual`), EXTEND (extensions), FAST (fast orders). Omit for all. |
| limit | integer | – | Rows to return (default 20, max 50). |
| offset | integer | – | Number of delegations to skip for pagination (default 0); add `limit` to page forward. |
| timeFilterBy | string | – | Time window: All, last 7 days (D7) or last 30 days (D30). Default All. |
| Name | Type | Req | Description |
|---|---|---|---|
| delegations | – | – | – |
No examples provided.
tronsave_list_extendable_delegates Extendable Delegates ~319
List extendable delegate candidates for a `receiver` and `resourceType` (ENERGY|BANDWIDTH). Optional `suggestData` scores an extend-and-buy scenario for planning purposes. Read-only; does NOT create orders or change on-chain state. No login required. NOTE: this is GraphQL market data for discovery only. To actually submit an extension, use `tronsave_internal_create_extend_request` with `extendData` from the authenticated REST `POST /v2/get-extendable-delegates` (payload shape differs from this GraphQL response).
| Name | Type | Req | Description |
|---|---|---|---|
| receiver | string | yes | TRON base58 address (typically starts with `T`) that currently receives or will receive the delegated resource. This is the primary filter: the response describes delegates relevant to extending that… |
| requester | string | – | Optional TRON base58 address of the viewing/requesting party. When an MCP session is active, the server may still derive identity from auth headers; use this when the API expects an explicit requeste… |
| resourceType | string | yes | Which resource market leg to query: `ENERGY` for contract execution headroom, `BANDWIDTH` for transaction bandwidth. Must match how you plan to extend or buy. |
| suggestData | object | – | Optional nested scenario for extend-and-buy suggestion scoring. If omitted, the query returns delegate rows without that hypothetical. If provided, supply all four fields together; partial objects ar… |
| Name | Type | Req | Description |
|---|---|---|---|
| extendableDelegates | – | – | Null when the market has no payload or GraphQL returned no branch; check tool-level errors for hard failures. |
No examples provided.
tronsave_list_extendable_receivers Extendable Receivers ~148
List the receiver addresses that have delegations bought by `requester` which can still be extended, with expiry time (Unix seconds), delegation count and total amount. Use as the first step of an extension flow to find which receiver to extend, then `tronsave_list_extendable_delegates` (market view) or `tronsave_internal_extend_delegates` (API-key path, returns the `extendData` to submit). Public (any requester address), read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| requester | string | yes | TRON base58 address that bought the delegations. |
| resourceType | string | – | Only delegations of this resource; omit for both. |
| Name | Type | Req | Description |
|---|---|---|---|
| receivers | – | – | – |
No examples provided.
tronsave_list_flash_unstake_orders Flash Unstake Market ~166
Browse the flash-unstake market: `available` (open orders buyers can take), `ongoing` (being paid out) or `completed`. Amounts are SUN-scaled numbers; `estimateCompletionTime` is seconds. Use to browse the whole market; the user's own request is `tronsave_get_flash_unstake_request` and a payout preview is `tronsave_estimate_flash_unstake`. Public, read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Which orders to list: available (default), ongoing or completed. |
| limit | integer | – | Orders to return (default 10, max 50). |
| offset | integer | – | Number of orders to skip for pagination (default 0); add `limit` to page forward. |
| Name | Type | Req | Description |
|---|---|---|---|
| kind | – | – | – |
| orders | – | – | – |
No examples provided.
tronsave_list_internal_transactions Internal Account Transactions ~167
List the TRX ledger of the logged-in user's internal account (deposits, order payments, refunds), newest first, with the current balance and deposit address. Amounts are SUN strings. Use to reconcile spending after orders. For the orders themselves use `tronsave_internal_order_history` (API key) or `tronsave_list_orders` (`isOnlyMyOrder`); for the balance alone, `tronsave_get_internal_account`. Page with `offset`/`limit`. Requires a wallet signature identity. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Ledger entries to return (default 20, max 50). |
| offset | integer | – | Number of ledger entries to skip for pagination (default 0); add `limit` to page forward. |
| Name | Type | Req | Description |
|---|---|---|---|
| transactions | – | – | – |
No examples provided.
tronsave_list_notifications Notifications ~142
List the logged-in user's notifications (order created / filled / cancelled / reclaimed, referral payouts) newest first, with the unread count. Use to follow up on an order after creating it; page with `offset`/`limit`, and mark items read with `tronsave_mark_notifications_read`. Requires a wallet signature identity. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Notifications to return (default 20, max 100). |
| offset | integer | – | Number of notifications to skip for pagination (default 0); add `limit` to page forward. |
| unreadOnly | boolean | – | true returns only unread notifications; default false returns all. |
| Name | Type | Req | Description |
|---|---|---|---|
| notifications | – | – | – |
| total | – | – | – |
| unreadCount | – | – | – |
No examples provided.
tronsave_list_order_books Order Book ~196
Read market depth buckets for `ENERGY` or `BANDWIDTH`. Public view; with an API key, `tronsave_internal_order_book` adds SLOW/MEDIUM/FAST price tiers. Returns price buckets `{ min, max, value }` optionally scoped by viewer address, minimum delegate amount, and duration. No login required; read-only and idempotent. Use this to estimate market ranges before create/update decisions; pair with `tronsave_estimate_buy_resource` for quote-style buy estimation and `tronsave_get_order` for one concrete order.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | – | Optional viewer/requester wallet context. |
| durationSec | number | – | Optional delegation duration filter in seconds. |
| minDelegateAmount | number | – | Optional minimum delegate amount floor for bucket filtering. |
| resourceType | string | yes | Order-book side to query (`ENERGY` or `BANDWIDTH`). |
| Name | Type | Req | Description |
|---|---|---|---|
| orderBook | – | – | – |
No examples provided.
tronsave_list_orders List Orders ~326
Query the market order list with paging (`offset`, `limit` ≤ 10). For an API-key account's own purchases use `tronsave_internal_order_history`. Returns `{ orders: [{ id, requester?.address, receiver.address, resourceType, resourceAmount, remainAmount, durationSec, unitPrice (SUN), isOwner, isMatching, apy, createdAt, typeOrder (NORMAL|FAST|EXTEND) }] }`. `status`: `ACTIVE` = still matching, `COMPLETED` = no longer matching. Set `isOnlyMyOrder=true` (requires a wallet signature identity) to list orders requested by the caller's wallet. Use `tronsave_get_order` with an `id` for one snapshot before mutating an order.
| Name | Type | Req | Description |
|---|---|---|---|
| isOnlyMyOrder | boolean | – | When `true`, only orders requested by the wallet of the current signature identity (signature login or `Signature` header). Api-key-only sessions cannot use this filter. |
| limit | integer | – | Maximum rows to return in one call. Prefer modest limits to avoid huge payloads; page with `offset`. |
| offset | integer | – | Zero-based row offset for page N (skip first `offset` matches). Omit when starting from the first page. |
| resourceType | string | – | Restrict to `ENERGY` or `BANDWIDTH` orders; omit for both. |
| status | string | – | Lifecycle filter: `ACTIVE` = still matching/open, `COMPLETED` = no longer matching. Omit for both. |
| Name | Type | Req | Description |
|---|---|---|---|
| orders | – | – | Matching orders for this page; may be large—use pagination inputs to chunk. |
No examples provided.
tronsave_login Login Session ~244
Log in to TronSave for the rest of this MCP connection. Provide EXACTLY ONE of: `signature` = `<signature>_<timestamp>` produced by the user's wallet over the `message` from `tronsave_get_sign_message` (unlocks wallet tools; also loads the wallet's internal API key if it has one), or `apiKey` = raw TronSave internal API key (unlocks internal-account tools and `paymentMethod=internal`). The login is bound to the current `mcp-session-id` automatically — do not pass session ids in later tool arguments. Returns `{ sessionId, authMode, walletAddress?, hasInternalApiKey, expiresAt, unlocked }`. Signed timestamps older than the server limit (default 24h) are rejected with `SIGNATURE_EXPIRED`. Never ask the user for private keys or seed phrases.
| Name | Type | Req | Description |
|---|---|---|---|
| apiKey | string | – | Raw API key for internal-tools login. Provide EXACTLY ONE of `apiKey` or `signature`. |
| signature | string | – | Signature token in `signature_timestamp` format (timestamp is the signed message). Provide EXACTLY ONE of `apiKey` or `signature`. |
| Name | Type | Req | Description |
|---|---|---|---|
| authMode | – | – | Which credential type the session holds. |
| expiresAt | – | – | Session expiry (ISO-8601). |
| hasInternalApiKey | – | – | Whether internal-account tools and `paymentMethod=internal` are usable in this session. |
| sessionId | – | – | The MCP session (`mcp-session-id`) the login is bound to. MCP clients resend it automatically; never pass it as a tool argument. |
| unlocked | – | – | Human-readable summary of the tool groups now available. |
| walletAddress | – | – | Wallet recovered from the signature (signature mode only). |
| warnings | – | – | Non-fatal issues (e.g. internal API key could not be loaded). |
No examples provided.
tronsave_logout Logout ~48
Remove the TronSave login bound to this MCP connection (api-key or signature). Returns `{ loggedOut: true }`; idempotent. Header credentials configured on the client are not affected.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| loggedOut | – | – | Always true; the login bound to this MCP session was removed (idempotent). |
No examples provided.
tronsave_mark_notifications_read Mark Notifications Read ~78
Mark one notification (by `id`) or, when `id` is omitted, ALL of the user's notifications as read. Get ids from `tronsave_list_notifications`. Only changes the read flag; idempotent. Requires a wallet signature identity.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | – | Notification id; omit to mark everything read. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | – |
| message | – | – | – |
| modifiedCount | – | – | – |
| success | – | – | – |
No examples provided.
tronsave_register_auto_sell Register Auto Sell ~207
Create the initial auto-sell configuration for the authenticated user. Returns the persisted `autoSettings` payload. Side effect: persists automation settings that affect future delegation/sell behavior; not idempotent — calling twice may reset fields. Requires a wallet signature identity. Use for FIRST-TIME setup only; for subsequent edits use `tronsave_update_auto_sell_setting`, and always read the current state with `tronsave_get_user_auto_setting` first to avoid overwriting unknown fields. Fails for invalid config combinations, unauthorized sessions, or backend policy restrictions.
| 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_revoke_api_key Revoke API Key ~110
Revoke the caller's current internal API key. Side effect: any future request using the previous key is rejected. Existing in-flight sessions cached by the server may continue serving until their TTL expires — treat the effect as 'best-effort immediate' rather than guaranteed instantaneous cutoff. Idempotent — revoking an already-revoked key returns success. Requires a wallet signature identity. Call `tronsave_generate_api_key` afterwards to mint a replacement when continued internal access is needed.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing. |
| data | – | – | For `generateApiKey`: the freshly issued internal API key — treat as SECRET, store securely. For `revokeApiKey`: server-defined confirmation string (no key material). |
| 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_sell_order_manual Sell Order Manual ~192
Manually execute seller-side fulfillment of an existing order with a wallet `signedTx`. Returns `{ success, message, code, delegatedId }`. Side effect: broadcasts a market/delegation transaction and may consume balances/resources; not idempotent — each call re-executes. Requires a wallet signature identity. Use only when explicit manual sell is intended; call `tronsave_get_order` first to verify order state before signing.
| Name | Type | Req | Description |
|---|---|---|---|
| orderId | string | yes | Target order id (`MObjectId`) to manually fulfill. Should be an order eligible for seller-side manual execution. |
| paymentAddress | string | – | Optional payout/payment address override when settlement flow requires it. |
| signedTx | object | yes | Required wallet-signed transaction payload (TronWeb shape: `{ txID, raw_data, raw_data_hex, signature[] }`). Must come from client-side signing; never fabricate. |
| Name | Type | Req | Description |
|---|---|---|---|
| code | – | – | GraphQL mutation status code (HTTP-like; `0`/`200` indicates success). Always pair with `success` for routing. |
| delegatedId | – | – | On-chain delegate id created by the manual sell when the underlying transaction is confirmed; null until confirmation lands. |
| 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_suggest_create_order Suggest Order Strategy ~211
Ask the market how a buy would be filled: a plain new order, buying more only, or extending existing delegations (optionally plus extra). Returns each option with `readyToFill` (percent), `payout` (SUN) and the `extendData` rows. Use before `tronsave_create_order` when the receiver may already have delegations that can be extended cheaper. Public, read-only. Prices move every ~3 s: re-run right before ordering.
| Name | Type | Req | Description |
|---|---|---|---|
| durationSec | number | yes | Delegation duration in seconds. |
| receiver | string | yes | TRON base58 address that will receive the resource. |
| requester | string | – | TRON base58 address that pays; defaults to the logged-in wallet. |
| resourceAmount | number | yes | Resource units to buy. |
| resourceType | string | yes | ENERGY (smart-contract calls) or BANDWIDTH (plain transfers). |
| unitPrice | number | yes | Unit price in SUN you are willing to pay. |
| Name | Type | Req | Description |
|---|---|---|---|
| suggestions | – | – | – |
No examples provided.
How do I install the TronSave MCP server?
TronSave is a hosted endpoint at https://mcp.tronsave.io/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/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/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.