MCP servers observed by Lowdown
io.github.tronsave/mcp MCP server: daily status and tool changes
On the latest check (2026-11-18) its remotes differed: 2 answered tools/list, 1 required authentication. (Lowdown checks this server every 3 days) MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-15 after 6 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.tronsave/mcp
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.tronsave/mcp?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server its remotes gave different results.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 0
- Required authentication: 0
- No response: 0
- Remotes differed: 4
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-15: input or output schemas changed, server version changed
- 2026-11-15: input or output schemas changed, server version changed
What tools does it list?
53 tools on 2026-11-18:
tronsave_bulk_create_internal_orderstronsave_cancel_ordertronsave_create_auto_buy_settingtronsave_create_ordertronsave_delete_auto_buy_settingtronsave_estimate_buy_resourcetronsave_estimate_flash_unstaketronsave_generate_api_keytronsave_get_account_resourcestronsave_get_agency_bottronsave_get_deposit_addresstronsave_get_flash_unstake_requesttronsave_get_internal_accounttronsave_get_market_overviewtronsave_get_min_pricetronsave_get_ordertronsave_get_price_tabletronsave_get_referraltronsave_get_seller_statstronsave_get_session_statustronsave_get_sign_messagetronsave_get_system_infotronsave_get_telegram_notify_settingtronsave_get_user_auto_settingtronsave_get_user_infotronsave_get_user_permissionstronsave_internal_create_extend_requesttronsave_internal_extend_delegatestronsave_internal_order_booktronsave_internal_order_createtronsave_internal_order_detailstronsave_internal_order_estimatetronsave_internal_order_historytronsave_list_auto_buy_settingstronsave_list_delegationstronsave_list_extendable_delegatestronsave_list_extendable_receiverstronsave_list_flash_unstake_orderstronsave_list_internal_transactionstronsave_list_notificationstronsave_list_order_bookstronsave_list_orderstronsave_logintronsave_logouttronsave_mark_notifications_readtronsave_register_auto_selltronsave_revoke_api_keytronsave_sell_order_manualtronsave_suggest_create_ordertronsave_update_auto_buy_settingtronsave_update_auto_sell_settingtronsave_update_ordertronsave_update_telegram_notify_setting
MCP Registry declaration
- Registry name:
io.github.tronsave/mcp - Declared version: 1.5.2
- Status: active
- Declared hosts:
mcp.tronsave.io
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:io.github.tronsave/mcp", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:io.github.tronsave/mcp?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).