tronsave_internal_order_history — TronSave MCP Tool
tronsave_internal_order_history
(tronsave internal order history) is one of 53 tools on the
TronSave
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call tronsave_internal_order_history from your client
- Claude Code TronSave tronsave_internal_order_history run in your project directory
- Claude Desktop TronSave tronsave_internal_order_history ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor TronSave tronsave_internal_order_history ~/.cursor/mcp.json
- VS Code TronSave tronsave_internal_order_history .vscode/mcp.json
- Zed TronSave tronsave_internal_order_history ~/.config/zed/settings.json
- Windsurf TronSave tronsave_internal_order_history ~/.codeium/windsurf/mcp_config.json
- Cline TronSave tronsave_internal_order_history ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI TronSave tronsave_internal_order_history ~/.gemini/settings.json
- Grok TronSave tronsave_internal_order_history .mcp.json (in your project root)
- ChatGPT TronSave tronsave_internal_order_history Settings → Connectors → Advanced → Developer mode
- Claude.ai TronSave tronsave_internal_order_history Settings → Connectors → Add custom connector
- LangChain TronSave tronsave_internal_order_history pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.tronsave.io/mcpOther tools on this server
- tronsave_get_internal_account
- tronsave_get_deposit_address
- 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
- tronsave_get_session_status
- tronsave_get_user_info
- tronsave_get_user_auto_setting
- tronsave_get_user_permissions
- tronsave_estimate_buy_resource
- tronsave_get_order
- tronsave_list_orders
- tronsave_list_order_books
- tronsave_get_min_price
- tronsave_list_extendable_delegates
- tronsave_create_order
- tronsave_sell_order_manual
- tronsave_cancel_order
- tronsave_update_order
- tronsave_register_auto_sell
- tronsave_update_auto_sell_setting
- tronsave_generate_api_key
- tronsave_revoke_api_key
- tronsave_delete_auto_buy_setting
- tronsave_get_market_overview
- tronsave_get_price_table
- tronsave_get_system_info
- tronsave_get_account_resources
- tronsave_suggest_create_order
- tronsave_list_extendable_receivers
- tronsave_get_seller_stats
- tronsave_list_delegations
- tronsave_list_auto_buy_settings
- tronsave_create_auto_buy_setting
- tronsave_update_auto_buy_setting
- tronsave_list_notifications
- tronsave_mark_notifications_read
- tronsave_get_referral
- tronsave_get_telegram_notify_setting
- tronsave_update_telegram_notify_setting
- tronsave_get_agency_bot
- tronsave_list_internal_transactions
- tronsave_get_flash_unstake_request
- tronsave_list_flash_unstake_orders
- tronsave_estimate_flash_unstake
- tronsave_bulk_create_internal_orders
This list was read from the server itself, by connecting to it and calling tools/list on 14 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.