Provenancewhere it came from, and what was verified
Published to the official MCP registry by github.com/tronsave, which proved it owns this namespace.
🛡 Permissions & trustwhat this server can touch before you run it
About
Buy, sell & extend TRON ENERGY/BANDWIDTH on the TronSave market via typed MCP tools.
Packages & transports
Computed from the server's own data, not a hidden formula. This measures how much you can depend on it, not how popular it is. Stars are shown separately, on purpose. How it's scored →
▸tronsave_get_internal_account100A
▸tronsave_get_deposit_address100A
▸tronsave_internal_order_history93A
▸tronsave_internal_order_details100A
▸tronsave_internal_order_book93A
▸tronsave_internal_order_estimate100A
▸tronsave_internal_order_create100A
▸tronsave_internal_extend_delegates100A
▸tronsave_internal_create_extend_request100A
▸tronsave_get_sign_message100A
▸tronsave_login93A
▸tronsave_get_user_info100A
▸tronsave_get_user_auto_setting100A
▸tronsave_get_user_permissions100A
▸tronsave_estimate_buy_resource93A
▸tronsave_get_order100A
▸tronsave_list_orders93A
▸tronsave_list_order_books100A
▸tronsave_get_min_price93A
▸tronsave_list_extendable_delegates100A
▸tronsave_create_order100A
▸tronsave_sell_order_manual100A
▸tronsave_cancel_order100A
▸tronsave_update_order100A
▸tronsave_register_auto_sell68C
▸tronsave_update_auto_sell_setting68C
▸tronsave_generate_api_key100A
▸tronsave_revoke_api_key100A
▸tronsave_delete_auto_buy_setting100A
Structural, not an LLM's opinion: each check is a fact about the tool's schema, so it's reproducible. One weak tool drags the score (60% average, 40% worst). How it's scored →
Raise this grade
up to +25 on qualityOwn this server? Here's exactly what to change, biggest wins first. Every number below is a fixed point value, so you can see what each edit is worth before you make it.
Push to the repo or cut a release. Activity within the last 30 days earns the full 45.
With no reviews this sits at a neutral 11. Reviews reporting it works push it toward the full 20.
Add an SPDX license (like MIT or Apache-2.0) to the repo so it's detected.
- 3 of 3 params have no description: `poolSetting`, `addOnFeature`, `paymentConfig`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- 3 of 3 params have no description: `poolSetting`, `addOnFeature`, `paymentConfig`. Describe each one.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
- No `required` array. Declare which params are mandatory so an agent knows what it must provide.
Already earned (3) ▾Already earned (3) ▴
These are structural checks, so the fixes are exact. See the full formula →
Add a badge to your README
[](https://socketcat.com/servers/io.github.tronsave/mcp)Shows your live quality grade and links back here. It updates itself as the grade changes.
Reviews
Sign in to leave a reviewNo reviews yet. Be the first to say whether it worked.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"mcp"
]
}
}
}▶ Try itlive against mcp.tronsave.io
This server has a hosted endpoint, so we can connect and list its actual tools right here. Nothing runs on your machine.