Model Context Protocol (MCP) server for freee API integration
TronEnergyFrog is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Live TRON Energy prices and rental for USDT TRC-20 transfers, paid by x402 USDC or API key.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user tronenergyfrog-mcp '--' npx -y tronenergyfrog-mcp
# 2 — ask your agent for something these tools do
# get_energy_prices, create_x402_quote, pay_x402_quote and 5 more
TronEnergyFrog costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts TronEnergyFrog as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user tronenergyfrog-mcp '--' npx -y tronenergyfrog-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take TRONENERGYFROG_API_KEY (Optional account API key from @tron_energy_frog_bot. Enables balance, fee check and rent_energy.), TRONENERGYFROG_EVM_PRIVATE_KEY (Optional Base wallet key that pays x402 quotes in USDC. Use a dedicated low-balance wallet.), TRONENERGYFROG_MAX_PAYMENT_USD (Per-payment USDC cap for pay_x402_quote. Default 5.) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
8 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Live TronEnergyFrog prices for 65,000 and 130,000 TRON Energy, for 1 hour or 1 day, compared with the TRX the network would burn without Energy. No API key needed.
No parameter schema on file.
Locks a TRON Energy rental price for 10 minutes, payable in USDC on Base (or Solana) through x402. No account or API key. Energy is delegated to target_address, which must be the wallet that will SEND the USDT. Creating a quote costs nothing.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target_address | yes | — | |
| energy_amount | integer | no | Energy to rent. 65,000 fits a USDT transfer to a wallet that already holds USDT; use 130,000 for a wallet with no USDT. |
| duration_seconds | no | Rental length in seconds: 3600 (1 hour) or 86400 (1 day). |
Pays an unexpired quote from create_x402_quote with USDC on Base from the configured wallet, then submits the rental. Spends real money: confirm the quote's price_usdc and target_address with the user first. Payments above … are refused.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | quote_id returned by create_x402_quote. |
Payment and delivery status of an x402 quote: payment_required, settling, fulfillment_pending, succeeded, failed or expired.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| quote_id | string | yes | quote_id returned by create_x402_quote. |
Account balance in TRX, discount and API-key status for the configured API key.
No parameter schema on file.
Checks whether the USDT RECIPIENT already holds USDT and estimates the Energy (65K or 130K) and TRX burn for sending USDT to it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| recipient_address | yes | — |
Rents TRON Energy at the live price and pays from the account's TRX balance. Spends real money: confirm the address, amount and price with the user first. Reuse the same idempotency_key when retrying so the order is not placed twice.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| target_address | yes | — | |
| energy_amount | integer | no | Energy to rent. 65,000 fits a USDT transfer to a wallet that already holds USDT; use 130,000 for a wallet with no USDT. |
| duration_seconds | no | Rental length in seconds: 3600 (1 hour) or 86400 (1 day). | |
| project_id | string | no | Optional order reference of your own, for later lookup. |
| idempotency_key | string | no | Retry key. Omit for a new order; repeat it to retry the same order safely. |
Status of a rental placed with rent_energy, by its operation id.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| operation_id | string | yes | id returned by rent_energy. |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install TronEnergyFrog or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (8 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
1 of the 8 recovered tools are registered only when settings.payingFetch holds (dist/tools.js:88) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 3.
4 of the 8 recovered tools are registered only when !settings.apiKey is false (dist/tools.js:120) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 3.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
3 tools are registered unconditionally · (1) 1 more only when settings.payingFetch holds (dist/tools.js:88) · (2) 4 more only when !settings.apiKey is false (dist/tools.js:120) — typically when a key or option is configured. All 8 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| get_energy_prices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| create_x402_quote | external-sink | external-sink: declares readOnlyHint: false, openWorldHint: true |
| pay_x402_quote conditional (1) | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_x402_rental | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_account conditional (2) | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| check_transfer_energy conditional (2) | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| rent_energy conditional (2) | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| get_rental conditional (2) | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish TronEnergyFrog can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.