Skip to content

TronSave MCP server

io.github.tronsave/mcptronsavestreamable-httpv1.5.2Scanned

Buy, sell and extend TRON Energy/Bandwidth on the TronSave market. Quotes need no login.

53 tools: 6 can delete or cancel things, 1 do something that can't be undone, 15 change things and 31 only read.

Tools: 6 delete, 1 irreversible, 15 write, 31 read.
  • Reads private data · 2
  • Reads text others write · 51
  • Can send data out · 0
  • 5 findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here can delete or cancel things and 1 does something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the TronSave MCP server can do

The TronSave MCP server is published by the GitHub account tronsave. It has 53 tools. It can delete or cancel things (6 tools: tronsave_logout, tronsave_sell_order_manual, tronsave_cancel_order, tronsave_generate_api_key and 2 more), do things that cannot be undone, such as sending, paying or publishing (tronsave_update_telegram_notify_setting) and create or change data (15 tools: tronsave_internal_order_estimate, tronsave_internal_order_create, tronsave_internal_create_extend_request, tronsave_login and 11 more). 31 tools only read.

2 tools read private data (tronsave_get_sign_message and tronsave_get_price_table); 51 tools bring in text other people can write (tronsave_get_internal_account, tronsave_get_deposit_address, tronsave_internal_order_history and 48 more).

The fixed checks matched 5 findings (annotation-conflict and credentials-mention). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 4 times since Anlyon Radar first saw them.

Last scanned Nov 13, 2026, version 1.5.2.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

53 tools

Deletes or cancels 6Claude Code: deny
  • tronsave_cancel_orderCancel an open order by `orderId`.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_cancel_order" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Cancel Order
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_delete_auto_buy_settingPermanently delete one auto-buy rule by `id` (`MObjectId`).Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_delete_auto_buy_setting" says "delete": a word for removing or ending something.
    • The description says "Permanently delete".
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Delete Auto Buy Setting
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_generate_api_keyGenerate a new internal API key credential for the current user.Reads text others write1 finding

    Why it is in this group

    • The name "tronsave_generate_api_key" says "generate": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "Generate a new internal API key credential for the current user. Returns `data` co..."

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Generate API Key
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • tronsave_logoutRemove the TronSave login bound to this MCP connection (api-key or signature).2 findings

    Why it is in this group

    • The description's first verb is "remove": a word for removing or ending something.
    • The server marks it not destructive (destructiveHint: false), but an annotation never lowers a class.

    Findings

    • Info

      The description mentions "credentials".

      Matched text

      description: "...loggedOut: true }`; idempotent. Header credentials configured on the client are not affect..."

      What this check looks for
    • Warn

      The server marks "tronsave_logout" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "remove": a word for removing or ending something.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Logout
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • tronsave_revoke_api_keyRevoke the caller's current internal API key.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_revoke_api_key" says "revoke": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Revoke API Key
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_sell_order_manualManually execute seller-side fulfillment of an existing order with a wallet `signedTx`.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Sell Order Manual
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Can't be undone 1Claude Code: ask
  • tronsave_update_telegram_notify_settingReplace the Telegram alert filters.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_update_telegram_notify_setting" says "update": a word for a change.
    • The input addresses people (input.sellerFilter.remainAmount.to): what it sends cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update Telegram Notification Settings
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Changes things 15Claude Code: ask
  • tronsave_bulk_create_internal_ordersBuy 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.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_bulk_create_internal_orders" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Bulk Buy For Many Receivers
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • tronsave_create_auto_buy_settingCreate a rule that automatically buys `resourceAmount` for `receiver` whenever its remaining resource falls below `thresholdResourceAmount`, paying up to `unitPrice` SUN per unit f…Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_create_auto_buy_setting" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create Auto-Buy Rule
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • tronsave_create_orderCreate a buy order for ENERGY/BANDWIDTH delegated to `orderReceiver`.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_create_order" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create Order
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • tronsave_estimate_buy_resourceQuote price and availability for buying ENERGY or BANDWIDTH for a receiver address before placing an order.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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`.

    Annotations the server declares

    • title: Estimate Buy Resource
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_estimate_flash_unstakeEstimate 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Estimate Flash Unstake
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_internal_create_extend_requestSubmit an extension request for existing delegated resources on TronSave via authenticated REST `POST /v2/extend-request`.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_internal_create_extend_request" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Submit Delegation Extension
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • tronsave_internal_order_createPlace a new buy order for ENERGY or BANDWIDTH on TronSave, paid from the internal account balance.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_internal_order_create" says "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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 }`.

    Annotations the server declares

    • title: Create Energy or Bandwidth Order (Internal)
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • tronsave_internal_order_estimateEstimate the TRX cost and availability for a buy order before submitting it (api-key internal account).Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Estimate TRX Cost Before Order
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_loginLog in to TronSave for the rest of this MCP connection.Reads text others write1 finding

    Why it is in this group

    • The description's first verb is "log": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "tronsave_login" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "log": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Login Session
    • readOnlyHint: false
    • idempotentHint: false
    • openWorldHint: true
  • tronsave_mark_notifications_readMark one notification (by `id`) or, when `id` is omitted, ALL of the user's notifications as read.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_mark_notifications_read" says "mark": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Mark Notifications Read
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_register_auto_sellCreate the initial auto-sell configuration for the authenticated user.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "create": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Register Auto Sell
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • tronsave_suggest_create_orderAsk the market how a buy would be filled: a plain new order, buying more only, or extending existing delegations (optionally plus extra).Reads text others write1 finding

    Why it is in this group

    • The name "tronsave_suggest_create_order" says "create": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.

    Findings

    • Warn

      The server marks "tronsave_suggest_create_order" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The name "tronsave_suggest_create_order" says "create": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Suggest Order Strategy
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_update_auto_buy_settingChange 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).Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_update_auto_buy_setting" says "update": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update Auto-Buy Rule
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_update_auto_sell_settingUpdate the existing auto-sell configuration with partial fields.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_update_auto_sell_setting" says "update": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update Auto Sell Setting
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • tronsave_update_orderUpdate an open order by `orderId` with partial fields (`receiver`, `newPrice`).Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_update_order" says "update": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Update Order
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Only reads 31Show 31 read-only tools
  • tronsave_get_account_resourcesRead the on-chain staked and delegatable ENERGY/BANDWIDTH of a TRON address, plus its TRX balance (SUN string).Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_account_resources" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Account Resources
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_agency_botRead 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 s…Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_agency_bot" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Agency Bot
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_deposit_addressFetches the specific deposit address for the TronSave internal account.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_deposit_address" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Deposit Address
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_flash_unstake_requestRead the logged-in user's flash-unstake request (selling staked TRX early for an immediate payout): state, payout state, amounts and release progress.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_flash_unstake_request" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: My Flash Unstake Request
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_internal_accountRetrieve the Tronsave internal account profile for the current logged-in session (wallet/represent address, balances, deposit address).Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_internal_account" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Internal Account Information
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_market_overviewRead the TronSave market summary: resource currently available and total listed for ENERGY and BANDWIDTH, number of pooled sellers, and seller APY (percent).Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_market_overview" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Market Overview
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_min_priceQuote the minimum unit price for a buy.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_min_price" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Minimum Unit Price
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_orderRead one order by `id` and return its full snapshot for NORMAL, FAST, or EXTEND order types.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_order" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Order Detail
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_price_tableRead 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_price_table" says "get": a word for reading.

    What it can reach

    • private-dataThe name "tronsave_get_price_table" says "get" and "table": it reads databases.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Resource Price Table
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_referralRead 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 recen…Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_referral" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Referral Program
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_seller_statsRead 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_seller_stats" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Seller Statistics
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_session_statusReport the current authentication state without calling TronSave: `authMode` (none | api-key | signature), `source` (login | header), `walletAddress`, `hasInternalApiKey`, `expires…No findings

    Why it is in this group

    • The name "tronsave_get_session_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Session Status
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • tronsave_get_sign_messageStep 1 of wallet login.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_sign_message" says "get": a word for reading.

    What it can reach

    • private-dataThe name "tronsave_get_sign_message" says "get" and "message": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe name "tronsave_get_sign_message" says "get" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get Signature Message
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_system_infoRead 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 t…Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_system_info" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Protocol Parameters
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_telegram_notify_settingRead 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 e…Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_telegram_notify_setting" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Telegram Notification Settings
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_user_auto_settingRead the current user's auto-sell configuration (`autoSettings`).Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_user_auto_setting" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: User Auto Setting
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_user_infoRead the current authenticated user's profile and linked TronSave internal account.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_user_info" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: User Information
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_get_user_permissionsRead the enabled permission operations (`autoSettings.permitOperations`) for the authenticated user.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_get_user_permissions" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: User Permissions
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_internal_extend_delegatesReturn extendable delegations for a receiver plus an `extendData` payload for the extension flow.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Extendable Delegations
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_internal_order_bookReturn the current TronSave market depth/price tiers for ENERGY or BANDWIDTH via the api-key REST endpoint.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Internal Market Order Book
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_internal_order_detailsFetch full details for one internal-account order by order ID.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "fetch": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Internal Order Details
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_internal_order_historyList paginated order history for the internal account linked to the API key, newest first.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Internal Account Order History
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_list_auto_buy_settingsList the logged-in user's auto-buy rules: receiver, resource, unit price cap, threshold, budget/order limits, totals bought and active state.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_list_auto_buy_settings" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Auto-Buy Rules
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_list_delegationsList the logged-in seller's delegations (resource sent to buyers): amount, TRX amount, duration, unit price, type (AUTO, MANUAL, EXTEND, FAST), status and payout.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_list_delegations" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Delegation History
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_list_extendable_delegatesList extendable delegate candidates for a `receiver` and `resourceType` (ENERGY|BANDWIDTH).Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_list_extendable_delegates" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Extendable Delegates
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_list_extendable_receiversList the receiver addresses that have delegations bought by `requester` which can still be extended, with expiry time (Unix seconds), delegation count and total amount.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_list_extendable_receivers" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Extendable Receivers
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_list_flash_unstake_ordersBrowse the flash-unstake market: `available` (open orders buyers can take), `ongoing` (being paid out) or `completed`.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_list_flash_unstake_orders" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Flash Unstake Market
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_list_internal_transactionsList the TRX ledger of the logged-in user's internal account (deposits, order payments, refunds), newest first, with the current balance and deposit address.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_list_internal_transactions" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Internal Account Transactions
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_list_notificationsList the logged-in user's notifications (order created / filled / cancelled / reclaimed, referral payouts) newest first, with the unread count.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_list_notifications" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Notifications
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_list_order_booksRead market depth buckets for `ENERGY` or `BANDWIDTH`.Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_list_order_books" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Order Book
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • tronsave_list_ordersQuery the market order list with paging (`offset`, `limit` ≤ 10).Reads text others writeNo findings

    Why it is in this group

    • The name "tronsave_list_orders" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List Orders
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:12 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
22
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.tronsave.io/.well-known/oauth-protected-resource/mcp
Authorization servers
https://mcp.tronsave.io/
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 22 tools that change things (6 destructive, 1 irreversible, 15 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.tronsave.io/mcp: tools/list returned 53 tools to an anonymous client, including tronsave_logout (destructive), tronsave_sell_order_manual (destructive), tronsave_cancel_order (destructive), tronsave_generate_api_key (destructive), tronsave_revoke_api_key (destructive) and 17 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • RFC 9728 protected resource metadata: none to https://mcp.tronsave.io/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://mcp.tronsave.io/
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 14 to 22

Findings

Matches of fixed checks, with the text they matched.

3 warn2 info
  • The server marks "tronsave_login" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"idempotentHint":false,"openWorldHint":true}; The description's first verb is "log": a word for reading.

    What this check looks for
  • The server marks "tronsave_logout" not destructive (destructiveHint: false), and its own name, description or input give the class "destructive".

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The description's first verb is "remove": a word for removing or ending something.

    What this check looks for
  • The server marks "tronsave_suggest_create_order" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"idempotentHint":true,"openWorldHint":true}; The name "tronsave_suggest_create_order" says "create": a word for a change.

    What this check looks for
  • The description mentions "credentials".

    Matched text

    description: "...loggedOut: true }`; idempotent. Header credentials configured on the client are not affect..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "Generate a new internal API key credential for the current user. Returns `data` co..."

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff
  2. PostureRemote posture changed. RFC 9728 protected resource metadata: none -> https://mcp.tronsave.io/.well-known/oauth-protected-resource/mcp; Authorization servers: none -> https://mcp.tronsave.io/; Dynamic client registration: not observed -> ye…View diff
    • RFC 9728 protected resource metadata: none to https://mcp.tronsave.io/.well-known/oauth-protected-resource/mcp
    • Authorization servers: none to https://mcp.tronsave.io/
    • Dynamic client registration: not observed to yes
    • Client ID metadata documents: not observed to no
  3. Tools33 changed.~33 changedView diff
  4. Tools2 changed.~2 changedView diff
  5. PostureRemote posture changed. Tools that change things, listed without credentials: 14 -> 22.View diff
    • Tools that change things, listed without credentials: 14 to 22
  6. Tools24 added, 29 changed.+24 added~29 changedView diff

Install

Pinned to version 1.5.2. Values in angle brackets are yours to fill in.

claude mcp add --transport http tronsave https://mcp.tronsave.io/mcp
claude mcp add --transport http tronsave https://mcp.tronsave.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__tronsave__tronsave_get_internal_account",
      "mcp__tronsave__tronsave_get_deposit_address",
      "mcp__tronsave__tronsave_internal_order_history",
      "mcp__tronsave__tronsave_internal_order_details",
      "mcp__tronsave__tronsave_internal_order_book",
      "mcp__tronsave__tronsave_internal_extend_delegates",
      "mcp__tronsave__tronsave_get_sign_message",
      "mcp__tronsave__tronsave_get_session_status",
      "mcp__tronsave__tronsave_get_user_info",
      "mcp__tronsave__tronsave_get_user_auto_setting",
      "mcp__tronsave__tronsave_get_user_permissions",
      "mcp__tronsave__tronsave_get_order",
      "mcp__tronsave__tronsave_list_orders",
      "mcp__tronsave__tronsave_list_order_books",
      "mcp__tronsave__tronsave_get_min_price",
      "mcp__tronsave__tronsave_list_extendable_delegates",
      "mcp__tronsave__tronsave_get_market_overview",
      "mcp__tronsave__tronsave_get_price_table",
      "mcp__tronsave__tronsave_get_system_info",
      "mcp__tronsave__tronsave_get_account_resources",
      "mcp__tronsave__tronsave_list_extendable_receivers",
      "mcp__tronsave__tronsave_get_seller_stats",
      "mcp__tronsave__tronsave_list_delegations",
      "mcp__tronsave__tronsave_list_auto_buy_settings",
      "mcp__tronsave__tronsave_list_notifications",
      "mcp__tronsave__tronsave_get_referral",
      "mcp__tronsave__tronsave_get_telegram_notify_setting",
      "mcp__tronsave__tronsave_get_agency_bot",
      "mcp__tronsave__tronsave_list_internal_transactions",
      "mcp__tronsave__tronsave_get_flash_unstake_request",
      "mcp__tronsave__tronsave_list_flash_unstake_orders"
    ],
    "ask": [
      "mcp__tronsave__tronsave_internal_order_estimate",
      "mcp__tronsave__tronsave_internal_order_create",
      "mcp__tronsave__tronsave_internal_create_extend_request",
      "mcp__tronsave__tronsave_login",
      "mcp__tronsave__tronsave_estimate_buy_resource",
      "mcp__tronsave__tronsave_create_order",
      "mcp__tronsave__tronsave_update_order",
      "mcp__tronsave__tronsave_register_auto_sell",
      "mcp__tronsave__tronsave_update_auto_sell_setting",
      "mcp__tronsave__tronsave_suggest_create_order",
      "mcp__tronsave__tronsave_create_auto_buy_setting",
      "mcp__tronsave__tronsave_update_auto_buy_setting",
      "mcp__tronsave__tronsave_mark_notifications_read",
      "mcp__tronsave__tronsave_update_telegram_notify_setting",
      "mcp__tronsave__tronsave_estimate_flash_unstake",
      "mcp__tronsave__tronsave_bulk_create_internal_orders"
    ],
    "deny": [
      "mcp__tronsave__tronsave_logout",
      "mcp__tronsave__tronsave_sell_order_manual",
      "mcp__tronsave__tronsave_cancel_order",
      "mcp__tronsave__tronsave_generate_api_key",
      "mcp__tronsave__tronsave_revoke_api_key",
      "mcp__tronsave__tronsave_delete_auto_buy_setting"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tronsave. Review it before you use it.

Capability tags behind 51 rules
  • mcp__tronsave__tronsave_get_internal_account untrusted-input
  • mcp__tronsave__tronsave_get_deposit_address untrusted-input
  • mcp__tronsave__tronsave_internal_order_history untrusted-input
  • mcp__tronsave__tronsave_internal_order_details untrusted-input
  • mcp__tronsave__tronsave_internal_order_book untrusted-input
  • mcp__tronsave__tronsave_internal_order_estimate untrusted-input
  • mcp__tronsave__tronsave_internal_order_create untrusted-input
  • mcp__tronsave__tronsave_internal_extend_delegates untrusted-input
  • mcp__tronsave__tronsave_internal_create_extend_request untrusted-input
  • mcp__tronsave__tronsave_get_sign_message private-data, untrusted-input
  • mcp__tronsave__tronsave_login untrusted-input
  • mcp__tronsave__tronsave_get_user_info untrusted-input
  • mcp__tronsave__tronsave_get_user_auto_setting untrusted-input
  • mcp__tronsave__tronsave_get_user_permissions untrusted-input
  • mcp__tronsave__tronsave_estimate_buy_resource untrusted-input
  • mcp__tronsave__tronsave_get_order untrusted-input
  • mcp__tronsave__tronsave_list_orders untrusted-input
  • mcp__tronsave__tronsave_list_order_books untrusted-input
  • mcp__tronsave__tronsave_get_min_price untrusted-input
  • mcp__tronsave__tronsave_list_extendable_delegates untrusted-input
  • mcp__tronsave__tronsave_create_order untrusted-input
  • mcp__tronsave__tronsave_sell_order_manual untrusted-input
  • mcp__tronsave__tronsave_cancel_order untrusted-input
  • mcp__tronsave__tronsave_update_order untrusted-input
  • mcp__tronsave__tronsave_register_auto_sell untrusted-input
  • mcp__tronsave__tronsave_update_auto_sell_setting untrusted-input
  • mcp__tronsave__tronsave_generate_api_key untrusted-input
  • mcp__tronsave__tronsave_revoke_api_key untrusted-input
  • mcp__tronsave__tronsave_delete_auto_buy_setting untrusted-input
  • mcp__tronsave__tronsave_get_market_overview untrusted-input
  • mcp__tronsave__tronsave_get_price_table private-data, untrusted-input
  • mcp__tronsave__tronsave_get_system_info untrusted-input
  • mcp__tronsave__tronsave_get_account_resources untrusted-input
  • mcp__tronsave__tronsave_suggest_create_order untrusted-input
  • mcp__tronsave__tronsave_list_extendable_receivers untrusted-input
  • mcp__tronsave__tronsave_get_seller_stats untrusted-input
  • mcp__tronsave__tronsave_list_delegations untrusted-input
  • mcp__tronsave__tronsave_list_auto_buy_settings untrusted-input
  • mcp__tronsave__tronsave_create_auto_buy_setting untrusted-input
  • mcp__tronsave__tronsave_update_auto_buy_setting untrusted-input
  • mcp__tronsave__tronsave_list_notifications untrusted-input
  • mcp__tronsave__tronsave_mark_notifications_read untrusted-input
  • mcp__tronsave__tronsave_get_referral untrusted-input
  • mcp__tronsave__tronsave_get_telegram_notify_setting untrusted-input
  • mcp__tronsave__tronsave_update_telegram_notify_setting untrusted-input
  • mcp__tronsave__tronsave_get_agency_bot untrusted-input
  • mcp__tronsave__tronsave_list_internal_transactions untrusted-input
  • mcp__tronsave__tronsave_get_flash_unstake_request untrusted-input
  • mcp__tronsave__tronsave_list_flash_unstake_orders untrusted-input
  • mcp__tronsave__tronsave_estimate_flash_unstake untrusted-input
  • mcp__tronsave__tronsave_bulk_create_internal_orders untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.tronsave/mcp/verify?hash=00a95784da43d6f756cb06dd57948dd735315781872c946fb1760dee4e015f12" | jq -e '.changed == false'

Pinned hash 00a95784da43, from Nov 13, 2026, 12:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.tronsave/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.tronsave/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.tronsave/mcp.svg)](https://radar.anlyon.com/servers/io.github.tronsave/mcp)

Source: MCP Registry · repository. Synced Nov 13, 2026, 12:18 UTC.

TronSave MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the TronSave MCP server safe?

No scan can promise that. What its definitions show: 53 tools, 22 of which can change, send or delete something, and 5 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the TronSave MCP server delete data?

Yes. 6 tools can delete, cancel or revoke something: tronsave_logout, tronsave_sell_order_manual, tronsave_cancel_order, tronsave_generate_api_key, tronsave_revoke_api_key and tronsave_delete_auto_buy_setting.

Can the TronSave MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: tronsave_update_telegram_notify_setting.

What tools does the TronSave MCP server have?

53 tools: 6 destructive, 1 irreversible, 15 write, 31 read. tronsave_logout, tronsave_sell_order_manual, tronsave_cancel_order, tronsave_generate_api_key, tronsave_revoke_api_key, tronsave_delete_auto_buy_setting, tronsave_update_telegram_notify_setting, tronsave_internal_order_estimate and 45 more.

Does the TronSave MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the TronSave MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the TronSave MCP server changed its tools?

Yes, 4 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.