LABSCO 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. Its 27 tools cover both sides: prices, energy purchases and SunSwap swaps for buyers; for sellers, registering a pool — build the permission transaction, broadcast it once signed, confirm the registration took — and then running it.

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

Paste a URL — add the endpoint to your client

See installation options

USE CASES

01

Putting idle staked TRX to work

Build the permission transaction for the pool you want to register, and read it before signing anything.

build_permission_transaction

02

Completing a delegation from an agent

Broadcast the transaction you signed locally, so the private key never reaches the service.

broadcast_signed_permission_tx

03

Making sure the pool is really live

Verify the registration after broadcasting, rather than assuming a successful send means a working pool.

verify_registration

27 tools

Listed in project docs. Your client may show a different list.

register

verify_registration

build_permission_transaction

broadcast_signed_permission_tx

get_prices

estimate_cost

get_available_resources

get_market_overview

buy_energy

get_balance

get_orders

get_order_status

get_deposit_info

broadcast_transaction

get_swap_quote

BEFORE YOU INSTALL

What to know first

Tools you get

27 tools named in the project's documentation.

Requires

A client that can reach a remote MCP server over HTTP

Where it runs

Both documented clients connect to a hosted endpoint.

INSTALLATION

Connect your client

Add the endpoint to your client.

Server setup

ENDPOINT URL

https://powersun.vip/mcp

MCP Clients

Cursor

CURSOR · JSON

{
  "mcpServers": {
    "powersun": {
      "url": "https://powersun.vip/mcp"
    }
  }
}

Any MCP client — API key

ANY MCP CLIENT — API KEY · JSON

{
  "mcpServers": {
    "powersun": {
      "url": "https://powersun.vip/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

PowerSun