io.github.tronrental-com/tronrental
NPM · @TRONRENTAL-COM/MCP-SERVER · SCANNED SEP 22
Buy TRON energy to reduce USDT transfer fees by 80%. Full API for AI agents.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 191 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1134 tokens (~113/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.tronrental-com/tronrental MCP server?
io.github.tronrental-com/tronrental runs locally as an npm package, launched with npx -y @tronrental-com/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @tronrental-com/mcp-server
claude mcp add tronrental-com-tronrental -- npx -y @tronrental-com/mcp-server
{
"mcpServers": {
"tronrental-com-tronrental": {
"command": "npx",
"args": [
"-y",
"@tronrental-com/mcp-server"
]
}
}
} {
"servers": {
"tronrental-com-tronrental": {
"command": "npx",
"args": [
"-y",
"@tronrental-com/mcp-server"
]
}
}
} codex mcp add tronrental-com-tronrental -- npx -y @tronrental-com/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"tronrental-com-tronrental": {
"type": "local",
"command": [
"npx",
"-y",
"@tronrental-com/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add tronrental-com-tronrental --command npx --arg -y --arg @tronrental-com/mcp-server
mcp_servers:
tronrental-com-tronrental:
command: "npx"
args: ["-y", "@tronrental-com/mcp-server"] {
"McpServers": {
"tronrental-com-tronrental": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@tronrental-com/mcp-server"
]
}
}
} assistant mcp add tronrental-com-tronrental -t stdio -c npx -a -y @tronrental-com/mcp-server
{
"mcpServers": {
"tronrental-com-tronrental": {
"command": "npx",
"args": [
"-y",
"@tronrental-com/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 17 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Sept 2026 · Analysed npm/@tronrental-com/mcp-server@1.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
buy_energy ~162
Buy TRON energy for a target address. This is the core action — energy eliminates USDT transfer fees. Use 65,000 for addresses that already hold USDT, or 131,000 for addresses that have never held USDT. Minimum: 60,000. Maximum: 5,000,000. Duration is always "1h". After purchase, call get_order to confirm the energy was delegated.
| Name | Type | Req | Description |
|---|---|---|---|
| duration | string | – | Rental duration — always use 1h |
| target_address | string | yes | TRON address to receive energy (starts with T, 34 chars) |
| volume | integer | yes | Energy amount: 65000 for 1 transfer (recipient has USDT), 131000 (recipient has no USDT) |
No output schema declared.
No examples provided.
calculate_savings ~95
Calculate TRX savings from renting energy vs burning TRX for USDT transfers. Returns burn_cost (what the user pays without energy) and rental_cost (what they pay with TronRental). The rental_cost is the TOTAL cost — there are no hidden or additional fees. After showing results, ask the user if they want to proceed with buying energy.
| Name | Type | Req | Description |
|---|---|---|---|
| monthly_transfers | integer | yes | Number of USDT transfers per month |
No output schema declared.
No examples provided.
create_api_key ~63
Create an API key for authenticated operations. Requires a valid access token from register or login. The key is shown only once — tell the user to save it. After creating, proceed to get_deposit_address.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Name for the API key |
No output schema declared.
No examples provided.
get_balance ~35
Check current TronRental account balance in TRX. Use after deposit to verify funds arrived, or before buy_energy to check sufficient balance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_deposit_address ~50
Get the TRX/USDT deposit address for funding the TronRental balance. Show this address to the user and ask them to send TRX. After they send, use get_balance to verify.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_order ~47
Check the status of an energy purchase order. Call after buy_energy to confirm the energy was successfully delegated to the target address.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | integer | yes | Order ID returned from buy_energy |
No output schema declared.
No examples provided.
get_prices ~40
Get current TronRental energy and bandwidth prices, TRX/USD rate, and volume limits. No authentication required. Use this to show the user current market rates.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
login ~38
Log in to an existing TronRental account. Returns access token.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Account email | |
| password | string | yes | Account password |
No output schema declared.
No examples provided.
regenerate_deposit_address ~41
Generate a new deposit address, replacing the current one. Use only if the user explicitly asks for a new address. Rate limited to 1 per minute.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
register ~94
Register a new TronRental account. Returns access token. Ask the user for their email, or suggest generating a temporary one. After registration, proceed to create_api_key.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | Email address for the account | |
| language | string | – | Language code (en, ru, zh, ko, etc.) |
| password | string | yes | Password (min 8 chars, must contain uppercase, lowercase, and digit) |
No output schema declared.
No examples provided.
What is the io.github.tronrental-com/tronrental MCP server?
io.github.tronrental-com/tronrental is an MCP server listed in the public MCP registry as io.github.tronrental-com/tronrental. Buy TRON energy to reduce USDT transfer fees by 80%. Full API for AI agents. This page covers its npm package (@tronrental-com/mcp-server).
Is the io.github.tronrental-com/tronrental MCP server safe to use?
io.github.tronrental-com/tronrental scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.tronrental-com/tronrental MCP server expose?
io.github.tronrental-com/tronrental exposes 10 tools: get_prices, calculate_savings, register, login, create_api_key, and 5 more. Their descriptions and schemas cost roughly 665 tokens of context every time the server is loaded.
Is the io.github.tronrental-com/tronrental MCP server still maintained?
io.github.tronrental-com/tronrental is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.tronrental-com/tronrental MCP server under?
io.github.tronrental-com/tronrental declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.