Labsco
MCP SERVER

PowerSun

by Hovsteder

Register as a TRON energy seller and hand over the permission transaction for signing — no key ever leaves your wallet.

Wallets, Signing & Transaction Execution
Summary
The seller side is the part that had no automation.

Renting energy is a purchase anyone can make in a browser. Running a pool means delegating permissions correctly and proving it stuck, which is where mistakes cost real TRX. Splitting that into build, broadcast and verify keeps the signature in your wallet and gives you a check at the end.

What it is

The server for PowerSun.vip, a TRON Energy and Bandwidth marketplace and SunSwap DEX aggregator. Buyers rent energy instead of burning TRX; sellers register a resource pool and earn on it. The tools captured here are the seller path: build the permission transaction, broadcast it once signed, and confirm the registration took.

What you get
  • A permission transaction built for you to sign, which is how a resource pool is delegated without surrendering a key
  • The signed permission transaction broadcast to the TRON network
  • Registration verified afterwards, so you know the pool is actually live
  • The wider platform behind the same endpoint: energy and bandwidth rented for anything from a few minutes to a month, and token swaps through SunSwap V2 Smart Router
  • Commission stated up front at 10%
Requirements

A client that accepts a remote streamable-HTTP endpoint, pointed at https://powersun.vip/mcp — no installation. An X-API-Key header is optional and the public tools work without it; there is also an HTTP 402 pay-per-use path and x402 with USDC on Base, neither of which needs an account. Signing happens in your own wallet.

Setup effort

One command — npx -y mcp-remote https://powersun.vip/mcp