Index / MCP servers / Tronsave

Tronsave MCP server

Tronsave is an MCP server with 29 tools an agent can call, among them tronsave_cancel_order, tronsave_create_order, tronsave_delete_auto_buy_setting. It answers at https://mcp.tronsave.io/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 24 October 2026, succeeded.

Status
Answering
Tools
29
Reliability
6 of 6 checks
Response time
438 ms
Transport
streamable HTTP
Last checked
24 October 2026

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

Description as the publisher wrote it.

The 29 tools Tronsave offers

ToolWhat it does
tronsave_cancel_orderCancel 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 — c
Inputs: orderId
tronsave_create_orderCreate 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) `onchai
Inputs: orderResourceType, orderReceiver, orderUnitPrice, orderDurationSec, orderResourceAmount, paymentMethod
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 success. Requires a sig
Inputs: id
tronsave_estimate_buy_resourceQuote 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_or
Inputs: resourceType, receiver, buyResourceAmount, unitPrice, durationSec, allowPartialFill
tronsave_generate_api_keyGenerate 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
tronsave_get_deposit_addressFetches 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. In
Inputs: amountTrx
tronsave_get_internal_accountRetrieve 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>` retu
tronsave_get_min_priceQuote 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 suppo
Inputs: address, resourceType, buyAmount, durationSec
tronsave_get_orderRead 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 s
Inputs: id
tronsave_get_sign_messageIssue 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 — c
tronsave_get_user_auto_settingRead 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 t
tronsave_get_user_infoRead 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
tronsave_get_user_permissionsRead 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 wall
tronsave_internal_create_extend_requestSubmit 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_log
Inputs: receiver, extendData, resourceType
tronsave_internal_extend_delegatesReturn 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 s
Inputs: receiver, extendTo, resourceType, maxPriceAccepted, requester
tronsave_internal_order_bookReturn 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_l
Inputs: address, resourceType, minDelegateAmount, durationSec
tronsave_internal_order_createPlace 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
Inputs: resourceType, resourceAmount, receiver, durationSec, unitPrice, sponsor
tronsave_internal_order_detailsFetch 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 to
Inputs: orderId
tronsave_internal_order_estimateEstimate 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
Inputs: resourceType, resourceAmount, receiver, requester, durationSec, unitPrice
tronsave_internal_order_historyList 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 subseque
Inputs: page, pageSize
tronsave_list_extendable_delegatesList 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 wi
Inputs: requester, receiver, resourceType, suggestData
tronsave_list_order_booksRead 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 mark
Inputs: address, resourceType, minDelegateAmount, durationSec
tronsave_list_ordersQuery 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)
Inputs: offset, limit, status, resourceType, isOnlyMyOrder
tronsave_loginAuthenticate 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 log
Inputs: apiKey, signature
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 — calling twice may r
Inputs: paymentConfig, poolSetting, addOnFeature
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 effect as 'best-effo
tronsave_sell_order_manualManually 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
Inputs: orderId, signedTx, paymentAddress
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 sets. Requires a sig
Inputs: paymentConfig, poolSetting, addOnFeature
tronsave_update_orderUpdate 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. B
Inputs: orderId, receiver, newPrice

Add Tronsave to your AI client

Every block below points at https://mcp.tronsave.io/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http tronsave https://mcp.tronsave.io/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "tronsave": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.tronsave.io/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "tronsave": {
      "url": "https://mcp.tronsave.io/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "tronsave": {
      "type": "http",
      "url": "https://mcp.tronsave.io/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "tronsave": {
      "url": "https://mcp.tronsave.io/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "tronsave": {
      "serverUrl": "https://mcp.tronsave.io/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "tronsave": {
      "url": "https://mcp.tronsave.io/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Tronsave
version: 0.0.1
schema: v1
mcpServers:
  - name: Tronsave
    type: streamable-http
    url: https://mcp.tronsave.io/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "tronsave": {
      "httpUrl": "https://mcp.tronsave.io/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "tronsave": {
      "type": "http",
      "url": "https://mcp.tronsave.io/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "tronsave": {
      "url": "https://mcp.tronsave.io/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fmcp.tronsave.io%2Fmcp&type=streamable_http&id=tronsave&name=Tronsave

Is Tronsave up right now?

It answered our last check on 24 October 2026 in 438 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Tronsave

Questions about Tronsave

How many tools does Tronsave have?

29, as returned by the server's own tools/list on 22 September 2026: tronsave_cancel_order, tronsave_create_order, tronsave_delete_auto_buy_setting, tronsave_estimate_buy_resource, tronsave_generate_api_key, tronsave_get_deposit_address, tronsave_get_internal_account, tronsave_get_min_price, and 21 more.

Is Tronsave down?

It answered our last check on 24 October 2026 in 438 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Tronsave to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.tronsave.io/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Tronsave need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.tronsave. Endpoint host: mcp.tronsave.io. ARD identifier: urn:air:io.github.tronsave:mcp:mcp. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.