io.github.tronsave/mcp

Est-ce que io.github.tronsave/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.tronsave/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 29 outils

• tronsave_cancel_order≈ 450 tokens

  Cancel an open order by `orderId`. Returns the cancelled order payload after the status flip. 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 signature session and `mcp-session-id`. Verify state with `tronsave_get_order` first; prefer `tronsave_update_order` when only price/receiver should change.

  Paramètres, retour & exemple (1)

  Paramètres

  • orderId · string · requis
    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.

  Exemple d'appel

  {"name": "tronsave_cancel_order", "arguments": {"orderId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"code": 1, "message": "texte", "success": true}}

• tronsave_create_order≈ 1378 tokens

  Create a new buy order on the TronSave market. Key inputs: `orderResourceType` (ENERGY|BANDWIDTH), `orderReceiver` (TRON base58), `orderUnitPrice` in SUN (NOT TRX), `orderDurationSec`, `orderResourceAmount`, and `paymentMethod`: (1) `onchain` — requires a signed payment tx in `paymentSignedTx`; (2) `internal` — deducts from internal balance. Side effect: creates a live order matchable by the market. Requires a signature session and `mcp-session-id`. Always derive `orderUnitPrice` and `paymentPaymentAmount` from the latest `tronsave_estimate_buy_resource` for the same receiver, amount, and duration to avoid reverts. FRESHNESS: re-quote immediately before submitting — estimates older than a few seconds (one TRON block ≈ 3s) may be stale and cause the order to revert or fill at the wrong price.

  Paramètres, retour & exemple (8)

  Paramètres

  • orderReceiver · string · requis
    TRON base58 address (starts with T) that receives delegated resource. Same as `receiver` passed to `tronsave_estimate_buy_resource`.
  • paymentMethod · string · requis · onchain | internal
    Payment method for this order: `onchain` (wallet signed tx) or `internal` (internal balance).
  • orderUnitPrice · number · requis
    Unit price in SUN. Prefer aligning with `minResourcePrice` or `buyResourcePrice` from the latest `tronsave_estimate_buy_resource` for the same receiver, amount, and duration.
  • paymentSignedTx · object · optionnel
    Required when `paymentMethod=onchain`. TronWeb-shaped signed TRON transaction (`{ txID, raw_data, raw_data_hex, signature[] }`). Must be produced client-side by the user's wallet; never fabricate or hand-edit.
  • orderDurationSec · number · requis
    Delegation duration in seconds. Must match the `durationSec` used in `tronsave_estimate_buy_resource`.
  • orderResourceType · string · requis · ENERGY | BANDWIDTH
    Resource to buy: ENERGY (smart contracts) or BANDWIDTH (transactions). Must match `tronsave_estimate_buy_resource`.
  • orderResourceAmount · number · requis
    Amount of ENERGY or BANDWIDTH units to purchase. Same as `buyResourceAmount` in estimate when applicable.
  • paymentPaymentAmount · number · requis
    Payment amount in SUN. Prefer deriving from `tronsave_estimate_buy_resource`; if converting to TRX, divide SUN by `1e6`.

  Exemple d'appel

  {"name": "tronsave_create_order", "arguments": {"orderReceiver": "texte", "paymentMethod": "onchain", "orderUnitPrice": 1, "orderDurationSec": 1, "orderResourceType": "ENERGY", "orderResourceAmount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"code": 1, "data": "texte", "message": "texte", "success": true}}

• tronsave_delete_auto_buy_setting≈ 396 tokens

  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 signature session and `mcp-session-id`. Use `tronsave_get_user_auto_setting` to list current rules first; prefer disabling/updating instead when reversibility is desired.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Auto-buy setting id (`MObjectId`) to delete.

  Exemple d'appel

  {"name": "tronsave_delete_auto_buy_setting", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"code": 1, "message": "texte", "success": true}}

• tronsave_estimate_buy_resource≈ 612 tokens

  Quote price and availability for buying ENERGY or BANDWIDTH for a receiver address before placing an order. Returns estimated `unitPrice` (SUN per resource unit), `paymentAmount`, and availability fields used to populate `tronsave_create_order` inputs (`orderUnitPrice`, `paymentPaymentAmount`). Read-only and safe to call repeatedly; no session is required, but backend rate limits apply. FRESHNESS: this is live market data — `unitPrice`/availability can change roughly every 3 seconds (one TRON block). Re-run this estimate immediately before `tronsave_create_order` and never reuse a quote more than a few seconds old. For order-book depth use `tronsave_list_order_books`; for the minimum unit price only use `tronsave_get_min_price`.

  Paramètres, retour & exemple (7)

  Paramètres

  • receiver · string · optionnel
    receiver address.
  • unitPrice · number · optionnel
    Unit price in SUN.
  • durationSec · number · optionnel
    Duration of the order in seconds. Default 15 minutes
  • resourceType · string · optionnel · ENERGY | BANDWIDTH
    Resource type to buy. Default ENERGY
  • allowPartialFill · boolean · optionnel
    Allow partial fill of the order.
  • buyResourceAmount · number · optionnel
    Amount of resource to buy. Default 100000 for ENERGY and 1000 for BANDWIDTH
  • minResourceDelegateRequiredAmount · number · optionnel
    Minimum amount of resource to delegate.

  Exemple d'appel

  {"name": "tronsave_estimate_buy_resource", "arguments": {"receiver": "texte", "unitPrice": 1, "durationSec": 1, "resourceType": "ENERGY", "allowPartialFill": true, "buyResourceAmount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"unitPrice": 1, "durationSec": 1, "estimateTrx": 1, "availableResource": 1, "systemDepositAddress": "texte"}}

• tronsave_generate_api_key≈ 455 tokens

  Generate a new internal API key credential for the current user. Returns `data` containing the issued key — store it securely and pass it to `tronsave_login` (`apiKey` mode) for internal-tool access. Side effect: issues secret material; not idempotent — each call mints a fresh key. If a previous key existed, treat it as rotated and stop using the old key once the new one is wired up. Requires a signature session and `mcp-session-id`. Sensitive output — never log raw keys; unauthorized sessions or policy checks may reject issuance.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "tronsave_generate_api_key", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"code": 1, "data": "texte", "message": "texte", "success": true}}

• tronsave_get_deposit_address≈ 359 tokens

  Fetches the specific deposit address for the TronSave internal account. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. 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.

  Paramètres, retour & exemple (1)

  Paramètres

  • amountTrx · number · requis
    Amount of TRX to deposit

  Exemple d'appel

  {"name": "tronsave_get_deposit_address", "arguments": {"amountTrx": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"amountTrx": 1, "depositAddress": "texte"}}

• tronsave_get_internal_account≈ 403 tokens

  Retrieve the TronSave internal account profile for the current session: represent address, deposit address, and balance (SUN). Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use when the user needs their linked address, deposit address, or internal balance. This is the api-key internal account, not the on-chain wallet. Read-only; does not submit orders or change chain state. FRESHNESS: balance reflects live state and can change within seconds after deposits/orders.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "tronsave_get_internal_account", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "balance": "texte", "depositAddress": "texte", "representAddress": "texte"}}

• tronsave_get_min_price≈ 532 tokens

  Quote the minimum unit price for a buy. Returns `{ minPrice }` (SUN per resource unit) from GraphQL `market.estimateMinPrice` for the given `resourceType`, `buyAmount`, and `durationSec`. Optional `address` scopes context when the API supports it. No login required; an optional session forwards auth like `tronsave_list_order_books`. Read-only and idempotent. FRESHNESS: live market data — `minPrice` can change roughly every 3 seconds; re-fetch right before placing an order and do not reuse a stale value. Pair with `tronsave_estimate_buy_resource` for full buy quotes and `tronsave_list_order_books` for depth buckets.

  Paramètres, retour & exemple (4)

  Paramètres

  • address · string · optionnel
    Optional TRON base58 address (`TronAddress`). When omitted, the server uses anonymous/global market context.
  • buyAmount · number · optionnel
    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 · optionnel
    Delegation window in seconds; must match the duration you plan to use on a real order for comparable quotes. Default 15 minutes
  • resourceType · string · optionnel · ENERGY | BANDWIDTH
    Market leg: `ENERGY` or `BANDWIDTH`. Default ENERGY

  Exemple d'appel

  {"name": "tronsave_get_min_price", "arguments": {"address": "texte", "buyAmount": 1, "durationSec": 1, "resourceType": "ENERGY"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"minPrice": 1}}

• tronsave_get_order≈ 851 tokens

  Read one order by `id` and return its full snapshot for NORMAL, FAST, or EXTEND order types. 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. FRESHNESS: order state can change within seconds as the market matches — re-read immediately before each mutation instead of reusing an earlier snapshot. Requires a signature session and `mcp-session-id`. Read-only and idempotent.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis
    Target order id (`MObjectId`) to inspect. Use this to confirm current status/price before update, sell, or cancel actions.

  Exemple d'appel

  {"name": "tronsave_get_order", "arguments": {"id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"order": "texte"}}

• tronsave_get_sign_message≈ 366 tokens

  Issue a wallet-signable timestamp message helper for signature login. Returns `{ message, timestamp }`: sign `message` exactly client-side, then submit `<signature>_<timestamp>` to `tronsave_login` (signature mode). Optional helper only — clients may also sign their own timestamp payload directly as long as it matches the `signature_timestamp` format expected by `tronsave_login`.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "tronsave_get_sign_message", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"message": "texte", "timestamp": 1}}

• tronsave_get_user_auto_setting≈ 1242 tokens

  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 signature session and `mcp-session-id`. Read-only and idempotent.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "tronsave_get_user_auto_setting", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"vote": "texte", "energy": "texte", "bandwidth": "texte", "suggestSell": "texte", "withdrawVote": "texte", "permitOperations": "texte", "reclaimOnlyTronSave": "texte"}}

• tronsave_get_user_info≈ 976 tokens

  Read the current authenticated user's profile and linked TronSave internal account. 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. Requires a signature session from `tronsave_login` and `mcp-session-id`. 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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "tronsave_get_user_info", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"info": "texte", "caller": "texte", "address": "texte", "balance": "texte", "internalAccount": "texte"}}

• tronsave_get_user_permissions≈ 427 tokens

  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 signature session and `mcp-session-id`. Read-only and idempotent.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "tronsave_get_user_permissions", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"permitOperations": []}}

• tronsave_internal_create_extend_request≈ 588 tokens

  Submit an extension request for existing delegated resources on TronSave, paid from the internal account. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Side effect: SPENDS internal TRX and creates an extension order; not idempotent. Use as STEP 2 after `tronsave_internal_extend_delegates` — pass its `extendData` rows unchanged. Returns `{ orderId }` for the new extension order.

  Paramètres, retour & exemple (3)

  Paramètres

  • receiver · string · requis
    TRON base58 address of the account that receives the delegated resource.
  • extendData · array · requis
    Rows copied from `extendData` returned by `tronsave_internal_extend_delegates`.
  • resourceType · string · optionnel · ENERGY | BANDWIDTH
    Resource type. Default ENERGY when omitted.

  Exemple d'appel

  {"name": "tronsave_internal_create_extend_request", "arguments": {"receiver": "texte", "extendData": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"orderId": "texte"}}

• tronsave_internal_extend_delegates≈ 888 tokens

  Return extendable delegations for a receiver plus an `extendData` payload for the extension flow. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use as STEP 1 before `tronsave_internal_create_extend_request` when the user wants to extend existing delegation time. Read-only; does not submit anything. FRESHNESS: pricing/availability change within seconds — run immediately before extending and pass the returned `extendData` unchanged.

  Paramètres, retour & exemple (5)

  Paramètres

  • extendTo · integer · requis
    Target end time as Unix epoch milliseconds (UTC) for the extended delegation.
  • receiver · string · requis
    TRON base58 address of the account that receives the delegated resource.
  • requester · string · optionnel
    TRON base58 requester; defaults to the API key account when omitted.
  • resourceType · string · optionnel · ENERGY | BANDWIDTH
    Resource type. Default ENERGY when omitted.
  • maxPriceAccepted · number · optionnel
    Maximum unit price in SUN you are willing to pay for the extension.

  Exemple d'appel

  {"name": "tronsave_internal_extend_delegates", "arguments": {"extendTo": 1, "receiver": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"extendData": "texte", "yourBalance": 1, "isAbleToExtend": true, "extendOrderBook": [], "totalEstimateTrx": 1, "totalDelegateAmount": 1, "totalAvailableExtendAmount": 1}}

• tronsave_internal_order_book≈ 591 tokens

  Return the current TronSave market depth/price tiers for ENERGY or BANDWIDTH via the api-key REST endpoint. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use before `tronsave_internal_order_create` or `tronsave_internal_order_estimate` when the user needs live prices or liquidity. Read-only. FRESHNESS: live market depth can change roughly every 3 seconds (one TRON block) — re-read immediately before placing an order.

  Paramètres, retour & exemple (4)

  Paramètres

  • address · string · optionnel
    Optional TRON base58 address filter for the receiver.
  • durationSec · integer · optionnel
    Delegation duration window in seconds for the quote.
  • resourceType · string · optionnel · ENERGY | BANDWIDTH
    Resource type. Default ENERGY when omitted.
  • minDelegateAmount · number · optionnel
    Minimum resource amount per offer level to include (resource units, not SUN).

  Exemple d'appel

  {"name": "tronsave_internal_order_book", "arguments": {"address": "texte", "durationSec": 1, "resourceType": "ENERGY", "minDelegateAmount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": [], "fast": 1, "slow": 1, "medium": 1, "availableResource": 1}}

• tronsave_internal_order_create≈ 798 tokens

  Place a new buy order for ENERGY or BANDWIDTH on TronSave, paid from the internal account balance. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. 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 }`.

  Paramètres, retour & exemple (7)

  Paramètres

  • options · object · optionnel
    Optional execution guards and fill behavior.
  • sponsor · string · optionnel
    Optional sponsor or referral code.
  • receiver · string · requis
    TRON base58 address that will receive the resource.
  • unitPrice · ? · optionnel
    Pricing: FAST | MEDIUM | SLOW strategy, or exact unit price in SUN per resource unit. Default MEDIUM when omitted.
  • durationSec · integer · optionnel
    Delegation duration in seconds. Default 259200 (3 days) when omitted.
  • resourceType · string · optionnel · ENERGY | BANDWIDTH
    Resource type. Default ENERGY when omitted.
  • resourceAmount · number · requis
    Amount of resource to purchase (resource units).

  Exemple d'appel

  {"name": "tronsave_internal_order_create", "arguments": {"receiver": "texte", "resourceAmount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"orderId": "texte"}}

• tronsave_internal_order_details≈ 733 tokens

  Fetch full details for one internal-account order by order ID. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use when monitoring fulfillment after `tronsave_internal_order_create`, or when the user asks for status on a specific order id. Read-only. FRESHNESS: order state changes within seconds as the market matches — re-read immediately before acting.

  Paramètres, retour & exemple (1)

  Paramètres

  • orderId · string · requis
    TronSave order ID (hex string), e.g. value returned in internal.order.create response data.orderId.

  Exemple d'appel

  {"name": "tronsave_internal_order_details", "arguments": {"orderId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "price": 1, "status": "texte", "receiver": "texte", "createdAt": "texte", "delegates": [], "orderType": "texte", "requester": "texte", "durationSec": 1, "payoutAmount": 1, "remainAmount": 1, "resourceType": "ENERGY"}}

• tronsave_internal_order_estimate≈ 672 tokens

  Estimate the TRX cost and availability for a buy order before submitting it (api-key internal account). Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use when the user wants a quote or price check; feed the result into `tronsave_internal_order_create`. Read-only. FRESHNESS: `unitPrice`/`estimateTrx` are live and can change roughly every 3 seconds — re-estimate immediately before creating the order.

  Paramètres, retour & exemple (7)

  Paramètres

  • options · object · optionnel
    Optional flags that affect matching behavior for the estimate.
  • receiver · string · optionnel
    TRON base58 address that will receive the resource.
  • requester · string · optionnel
    TRON base58 requester; defaults to the API key account when omitted.
  • unitPrice · ? · optionnel
    Pricing: FAST | MEDIUM | SLOW strategy, or exact unit price in SUN per resource unit. Default MEDIUM when omitted.
  • durationSec · integer · optionnel
    Delegation duration in seconds. Default 259200 (3 days) when omitted.
  • resourceType · string · optionnel · ENERGY | BANDWIDTH
    Resource type. Default ENERGY when omitted.
  • resourceAmount · number · requis
    Amount of resource to purchase (resource units).

  Exemple d'appel

  {"name": "tronsave_internal_order_estimate", "arguments": {"resourceAmount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"unitPrice": 1, "durationSec": 1, "estimateTrx": 1, "availableResource": 1}}

• tronsave_internal_order_history≈ 822 tokens

  List paginated order history for the internal account linked to the API key, newest first. Requires a logged-in MCP session created by the `tronsave_login` tool: include `mcp-session-id: <sessionId>` returned by `tronsave_login` on subsequent MCP requests. Internal tools never accept API keys via tool arguments; signature sessions resolve the latest internal API key on demand, while api-key sessions reuse the validated key from login. Use when the user asks about past purchases, fulfillment, payouts, or delegates on their internal account. Read-only. Pair with `tronsave_internal_order_details` for a single order's full snapshot.

  Paramètres, retour & exemple (2)

  Paramètres

  • page · integer · optionnel
    Page index, 0-based. Omit for first page (default 0).
  • pageSize · integer · optionnel
    Orders per page. Default 10 when omitted. Typical range 1–100.

  Exemple d'appel

  {"name": "tronsave_internal_order_history", "arguments": {"page": 1, "pageSize": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"data": [], "total": 1}}

• tronsave_list_extendable_delegates≈ 1510 tokens

  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. Works without `mcp-session-id`; when a session is present, auth is forwarded so results can reflect the logged-in account where supported. NOTE: this is GraphQL market data for discovery only. To actually submit an extension, call the authenticated REST `POST /v2/get-extendable-delegates` with `extendData` (payload shape differs from this GraphQL response).

  Paramètres, retour & exemple (4)

  Paramètres

  • receiver · string · requis
    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 account's delegation.
  • requester · string · optionnel
    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 requester string distinct from the receiver.
  • suggestData · object · optionnel
    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 are invalid for typical GraphQL input shapes.
  • resourceType · string · requis · ENERGY | BANDWIDTH
    Which resource market leg to query: `ENERGY` for contract execution headroom, `BANDWIDTH` for transaction bandwidth. Must match how you plan to extend or buy.

  Exemple d'appel

  {"name": "tronsave_list_extendable_delegates", "arguments": {"receiver": "texte", "resourceType": "ENERGY"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"extendableDelegates": "texte"}}

• tronsave_list_order_books≈ 424 tokens

  Read market depth buckets for `ENERGY` or `BANDWIDTH`. Returns price buckets `{ min, max, value }` optionally scoped by viewer address, minimum delegate amount, and duration. No login required; read-only and idempotent. FRESHNESS: live market depth — buckets can shift roughly every 3 seconds; re-read immediately before acting on a price. 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.

  Paramètres, retour & exemple (4)

  Paramètres

  • address · string · optionnel
    Optional viewer/requester wallet context.
  • durationSec · number · optionnel
    Optional delegation duration filter in seconds.
  • resourceType · string · requis · ENERGY | BANDWIDTH
    Order-book side to query (`ENERGY` or `BANDWIDTH`).
  • minDelegateAmount · number · optionnel
    Optional minimum delegate amount floor for bucket filtering.

  Exemple d'appel

  {"name": "tronsave_list_order_books", "arguments": {"resourceType": "ENERGY"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"orderBook": []}}

• tronsave_list_orders≈ 1107 tokens

  Query the order list with paging. Returns `{ orders: [{ id, requester?.address, receiver.address, resourceType, resourceAmount, remainAmount, durationSec, unitPrice (SUN), isOwner, isMatching, apy, createdAt, typeOrder (NORMAL|FAST|EXTEND) }] }`. Filter `status` maps to GraphQL `isFulfilled`: `ACTIVE` → `UNFULFILLED`, `COMPLETED` → `FULFILLED`. Set `onlyMyOrder=true` (requires signature login + `mcp-session-id`) to scope to the caller's wallet as requester. Paging uses `offset`/`limit`. Use `tronsave_get_order` with an `id` for one full snapshot before mutating an order.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · integer · optionnel
    Maximum rows to return in one call. Prefer modest limits to avoid huge payloads; page with `offset`.
  • offset · integer · optionnel
    Zero-based row offset for page N (skip first `offset` matches). Omit when starting from the first page.
  • status · string · optionnel · ACTIVE | COMPLETED
    Lifecycle filter mapped to GraphQL `isFulfilled`: `ACTIVE` → `UNFULFILLED` (not yet fulfilled), `COMPLETED` → `FULFILLED`.
  • resourceType · string · optionnel · ENERGY | BANDWIDTH
    Restrict to `ENERGY` or `BANDWIDTH` orders; omit for both.
  • isOnlyMyOrder · boolean · optionnel
    When `true`, only orders whose `requester` is the wallet from the signature session; include `mcp-session-id`. Api-key-only sessions have no wallet address and cannot use this filter. When `false` or omitted, return all orders on the market (no requester filter).

  Exemple d'appel

  {"name": "tronsave_list_orders", "arguments": {"limit": 1, "offset": 1, "status": "ACTIVE", "resourceType": "ENERGY", "isOnlyMyOrder": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"orders": []}}

• tronsave_login≈ 518 tokens

  Authenticate with TronSave and create a server session. Returns `{ sessionId, walletAddress?, expiresAt }` — pass `sessionId` as the `mcp-session-id` header on every subsequent MCP request. `walletAddress` is set only for signature-mode logins. Two modes: (1) wallet signature (preferred for platform tools) — call this tool with `signature_timestamp` formatted as `<signature>_<timestamp>`, where `<signature>` must be produced client-side by signing the timestamp message; you may optionally call `tronsave_get_sign_message` to obtain a helper message/timestamp pair; (2) API key (internal tools) — pass `apiKey` (raw key, no prefix). Side effect: creates a new session on the server. Wallet signing must happen client-side; never send private keys to the server.

  Paramètres, retour & exemple (2)

  Paramètres

  • apiKey · string · optionnel
    Raw API key for internal-tools login. Provide EXACTLY ONE of `apiKey` or `signature`.
  • signature · string · optionnel
    Signature token in `signature_timestamp` format (timestamp is the signed message). Provide EXACTLY ONE of `apiKey` or `signature`.

  Exemple d'appel

  {"name": "tronsave_login", "arguments": {"apiKey": "texte", "signature": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"expiresAt": "texte", "sessionId": "texte", "walletAddress": "texte"}}

• tronsave_register_auto_sell≈ 1442 tokens

  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 signature session and `mcp-session-id`. 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • poolSetting · object · optionnel
  • addOnFeature · object · optionnel
  • paymentConfig · object · optionnel

  Exemple d'appel

  {"name": "tronsave_register_auto_sell", "arguments": {"poolSetting": {}, "addOnFeature": {}, "paymentConfig": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"code": 1, "data": "texte", "message": "texte", "success": true}}

• tronsave_revoke_api_key≈ 449 tokens

  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 signature session and `mcp-session-id`. Call `tronsave_generate_api_key` afterwards to mint a replacement when continued internal access is needed.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "tronsave_revoke_api_key", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"code": 1, "data": "texte", "message": "texte", "success": true}}

• tronsave_sell_order_manual≈ 986 tokens

  Manually execute seller-side fulfillment of an existing order with a wallet `signedTx`. Returns the updated order payload after sell. Side effect: broadcasts a market/delegation transaction and may consume balances/resources; not idempotent — each call re-executes. Backend requires a signature session and `mcp-session-id`; the MCP gate is `public` to allow anonymous read-fallthrough, but the GraphQL helper rejects api-key-only sessions. Use only when explicit manual sell is intended; call `tronsave_get_order` first to verify order state before signing.

  Paramètres, retour & exemple (3)

  Paramètres

  • orderId · string · requis
    Target order id (`MObjectId`) to manually fulfill. Should be an order eligible for seller-side manual execution.
  • signedTx · object · requis
    Required wallet-signed transaction payload (TronWeb shape: `{ txID, raw_data, raw_data_hex, signature[] }`). Must come from client-side signing; never fabricate.
  • paymentAddress · string · optionnel
    Optional payout/payment address override when settlement flow requires it.

  Exemple d'appel

  {"name": "tronsave_sell_order_manual", "arguments": {"orderId": "texte", "signedTx": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"code": 1, "message": "texte", "success": true, "delegatedId": "texte"}}

• tronsave_update_auto_sell_setting≈ 1435 tokens

  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 signature session and `mcp-session-id`. 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • poolSetting · object · optionnel
  • addOnFeature · object · optionnel
  • paymentConfig · object · optionnel

  Exemple d'appel

  {"name": "tronsave_update_auto_sell_setting", "arguments": {"poolSetting": {}, "addOnFeature": {}, "paymentConfig": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"code": 1, "data": "texte", "message": "texte", "success": true}}

• tronsave_update_order≈ 494 tokens

  Update an open order by `orderId` with partial fields (`receiver`, `newPrice`). Returns the updated order payload. Side effect: overwrites live order parameters; not idempotent — each call with a different `newPrice` produces a new state. Backend requires a signature session and `mcp-session-id`; the MCP gate is `public` to allow anonymous read-fallthrough, but the GraphQL helper rejects api-key-only sessions. 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.

  Paramètres, retour & exemple (3)

  Paramètres

  • orderId · string · requis
    Target order id (`MObjectId`) to update. Order must still be open and editable.
  • newPrice · number · optionnel
    Optional replacement unit price in SUN.
  • receiver · string · optionnel
    Optional replacement receiver TRON address.

  Exemple d'appel

  {"name": "tronsave_update_order", "arguments": {"orderId": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"code": 1, "message": "texte", "success": true}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.tronsave.io/mcp