Agents Index

TronSave

Online

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

Visit publisherConnectJSON

What it can do: 53 tools

  • tronsave_get_internal_account read-onlyRetrieve 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
  • tronsave_get_deposit_address read-onlyFetches 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
  • tronsave_internal_order_history read-onlyList 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 `Aut
  • tronsave_internal_order_details read-onlyFetch 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>` cl
  • tronsave_internal_order_book read-onlyReturn 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 ac
  • tronsave_internal_order_estimate read-onlyEstimate 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 accoun
  • tronsave_internal_order_createPlace 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
  • tronsave_internal_extend_delegates read-onlyReturn 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
  • tronsave_internal_create_extend_requestSubmit 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
  • tronsave_get_sign_message read-onlyStep 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>_<timesta
  • tronsave_loginLog 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 to
  • tronsave_logoutRemove 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.
  • tronsave_get_session_status read-onlyReport the current authentication state without calling TronSave: `authMode` (none | api-key | signature), `source` (login | header), `walletAddress`, `hasInternalApiKey`, `expiresAt`, network, and which tool groups are
  • tronsave_get_user_info read-onlyRead 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, addres
  • tronsave_get_user_auto_setting read-onlyRead 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
  • tronsave_get_user_permissions read-onlyRead 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
  • tronsave_estimate_buy_resource read-onlyQuote 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_in
  • tronsave_get_order read-onlyRead 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_or
  • tronsave_list_orders read-onlyQuery 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
  • tronsave_list_order_books read-onlyRead 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 view
  • tronsave_get_min_price read-onlyQuote 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 `
  • tronsave_list_extendable_delegates read-onlyList 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-c
  • tronsave_create_orderCreate 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_cr
  • tronsave_sell_order_manualManually 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/
  • tronsave_cancel_orderCancel 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 — ca
  • tronsave_update_orderUpdate 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`
  • tronsave_register_auto_sellCreate 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 —
  • tronsave_update_auto_sell_settingUpdate 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
  • tronsave_generate_api_keyGenerate 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: is
  • tronsave_revoke_api_keyRevoke 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
  • tronsave_delete_auto_buy_settingPermanently 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 suc
  • tronsave_get_market_overview read-onlyRead 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
  • tronsave_get_price_table read-onlyRead 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: '3
  • tronsave_get_system_info read-onlyRead 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 t
  • tronsave_get_account_resources read-onlyRead 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
  • tronsave_suggest_create_order read-onlyAsk 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 `extendDa
  • tronsave_list_extendable_receivers read-onlyList 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
  • tronsave_get_seller_stats read-onlyRead 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 muc
  • tronsave_list_delegations read-onlyList 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 selle
  • tronsave_list_auto_buy_settings read-onlyList 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_set

…and 13 more.

Connect it

Claude Code
claude mcp add --transport http tronsave https://mcp.tronsave.io/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://mcp.tronsave.io/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "tronsave": {
      "url": "https://mcp.tronsave.io/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "tronsave": {
      "type": "http",
      "url": "https://mcp.tronsave.io/mcp"
    }
  }
}

Questions

What does TronSave do?

Buy, sell and extend TRON Energy/Bandwidth on the TronSave market. Quotes need no login. It exposes 53 tools to AI assistants.

What tools does TronSave provide?

53 tools, including tronsave_get_internal_account, tronsave_get_deposit_address, tronsave_internal_order_history, tronsave_internal_order_details, tronsave_internal_order_book, tronsave_internal_order_estimate, tronsave_internal_order_create, tronsave_internal_extend_delegates, tronsave_internal_create_extend_request, tronsave_get_sign_message, tronsave_login, tronsave_logout….

How do I connect TronSave to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://mcp.tronsave.io/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does TronSave require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is TronSave online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes TronSave?

@tronsave on GitHub. The official MCP Registry verified that the publisher controls this GitHub account before accepting the listing.

Similar in E-commerce & Shopping