Is the Hovsteder Powersun Tron MCP server down?

mcp-registry/io.github.hovsteder/powersun-tron-mcp · v2.0.0

Also listed as awesome/hovsteder/powersun-tron-mcp

healthy
Last checked 2026-10-22 13:07 UTC · handshake 575ms

As of 2026-10-22 13:07 UTC, the Hovsteder Powersun Tron MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.

uptime (30d checks)
99.8%
checks observed
4,139
outages (90d)
4
tools
27

TRON Energy marketplace + DEX swap aggregator for AI agents. 27 MCP tools.

Install Hovsteder Powersun Tron MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http hovsteder-powersun-tron-mcp-server https://powersun.vip/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "hovsteder-powersun-tron-mcp-server": {
      "type": "http",
      "url": "https://powersun.vip/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (80/100)

B (80/100): 0 error(s), 2 warning(s) across 27 tool(s); ~5,603 tokens of tool definitions.
Scores higher than 33% of 15,512 MCP servers Glimind has audited.
Its tool list costs an agent ~5,603 tokens per session — more than 60% of servers.
79 → 81 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions100
Safety hints8
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability68

What to fix (4)

27 of 27 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: broadcast_signed_permission_tx, broadcast_transaction, build_permission_transaction, buy_energy, check_pool_permissions and 22 more

4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: buy_energy, configure_auto_selling, execute_swap, register_pool

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

In the last 30 days: 0 tool(s) removed and 8 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 20 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.hovsteder%2Fpowersun-tron-mcp/fixes

buy_energy 1 change
{
  "name": "buy_energy",
  "description": "Purchase TRON Energy for a target address. Creates a MARKET order that will be filled by available pools. Deducts cost from your balance.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "targetAddress",
      "txCount"
    ],
    "properties": {
      "txType": {
        "enum": [
          "trc20_transfer",
          "trc20_transfer_new",
          "trc10_transfer",
          "contract_call"
        ],
        "type": "string",
        "description": "Transaction type (default: trc20_transfer)"
      },
      "txCount": {
        "type": "integer",
        "description": "Number of transactions you need energy for",
        "exclusiveMinimum": 0
      },
      "resourceType": {
        "enum": [
          "ENERGY",
          "BANDWIDTH"
        ],
        "type": "string",
        "description": "Resource type (default: ENERGY)"
      },
      "targetAddress": {
        "type": "string",
        "maxLength": 34,
        "description": "TRON address to delegate energy to (T-address format)"
      },
      "durationMinutes": {
        "type": "number",
        "description": "Duration in minutes. Allowed: 2, 5, 10, 15, 30, 60, 180, 360, 1440, 10080, 43200. Default: 60."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Buy Energy"
}
check_pool_permissions 1 change
{
  "name": "check_pool_permissions",
  "description": "Verify that the platform has the required active permissions on your pool address. Required: DelegateResource (to sell energy), UnDelegateResource (to reclaim). Optional: VoteWitness (to vote for SRs and earn rewards). Run this after granting permissions to confirm the platform can operate your pool. Requires API key.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {
      "poolAddress": {
        "type": "string",
        "maxLength": 34,
        "description": "Pool address to check. If omitted, uses your first registered pool."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  },
  "title": "Check Pool Permissions"
}
configure_auto_selling 1 change
{
  "name": "configure_auto_selling",
  "description": "Update auto-selling configuration for a pool. Toggle energy/bandwidth selling, set reserves, duration constraints. Pass the configId from get_auto_selling_config.",
  "inputSchema": {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "configId"
    ],
    "properties": {
      "active": {
        "type": "boolean",
        "description": "Enable/disable auto-selling"
      },
      "configId": {
        "type": "string",
        "maxLength": 36,
        "description": "Configuration ID to update (from get_auto_selling_config)"
      },
      "sellEnergy": {
        "type": "boolean",
        "description": "Enable/disable energy selling"
      },
      "maxDuration": {
        "type": "string",
        "maxLength": 10,
        "description": "Maximum rental duration"
      },
      "minDuration": {
        "type": "string",
        "maxLength": 10,
        "description": "Minimum rental duration (e.g., \"5min\", \"1h\", \"1d\")"
      },
      "allowRenewals": {
        "type": "boolean",
        "description": "Allow order renewals"
      },
      "sellBandwidth": {
        "type": "boolean",
        "description": "Enable/disable bandwidth selling"
      },
      "reservedEnergy": {
        "type": "integer",
        "minimum": 0,
        "description": "Energy to keep reserved (not sold)"
      },
      "reservedBandwidth": {
        "type": "integer",
        "minimum": 0,
        "description": "Bandwidth to keep reserved (not sold)"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  },
  "title": "Configure Auto-Selling"
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.hovsteder/powersun-tron-mcp"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.hovsteder/powersun-tron-mcp"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hovsteder%2Fpowersun-tron-mcp.svg)](https://glimind.com/server/mcp-registry%2Fio.github.hovsteder%2Fpowersun-tron-mcp?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fio.github.hovsteder%2Fpowersun-tron-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hovsteder%2Fpowersun-tron-mcp.svg" alt="MCP agent-readiness"></a>
reStructuredText
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.hovsteder%2Fpowersun-tron-mcp.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.hovsteder%2Fpowersun-tron-mcp?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:dc4151fa58687127…, first seen 2026-10-22, included at leaf 45668 of 46,070. Version history · verify what your client received.

Tools (27)

Compare: most reliable blockchain servers · most reliable finance servers · most reliable security servers · most reliable data servers · most reliable other servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Hovsteder Powersun Tron MCP server down right now?

As of 2026-10-22 13:07 UTC, the Hovsteder Powersun Tron MCP server is up with a Glimind reliability score of 85/100 (grade B). Over the last 30 days it answered 99.8% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 7 minutes.

How many tools does Hovsteder Powersun Tron MCP server provide?

Hovsteder Powersun Tron MCP server advertises 27 tools, including broadcast_signed_permission_tx, broadcast_transaction, build_permission_transaction, buy_energy, check_pool_permissions.

How do I install Hovsteder Powersun Tron MCP server?

Point your MCP client at this streamable-http endpoint: https://powersun.vip/mcp

Is the Hovsteder Powersun Tron MCP server safe to connect to an AI agent?

Glimind scanned all 27 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Hovsteder Powersun Tron MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve