io.github.tronrental-com/tronrental
NPM · @TRONRENTAL-COM/MCP-SERVER · 2 COMPONENTS
Rent TRON energy and bandwidth so USDT transfers cost less TRX: quotes, orders, balance.
Available components
Last scanned (22 hours ago)
Scores higher than 53% of npm servers
Category Crypto and Web3
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 92 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 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 839 tokens (~104/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
- Stability check failed: the tool surface changed between 1.0.4 and 2.0.0: 5 tool removals, 0 breaking changes, 3 additions. See how to fix → Fail
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 20 Nov 26 −23
- Malware scan: pass → unverified ▼ security
- Stability: pass → fail ▼ security
- Tool coverage: 100% → 73% ▼ functional
- Schema quality: fail → pass ▲ functional
- Schema quality: excellent → good functional
- Package version: 1.0.4 → 2.0.0 functional
- 16 Nov 26 0
- Stability: 0.97 → pass security
- 15 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Nov 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.
- 4 Nov 26 −3
- Stability: pass → 0.83 functional
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 21 Nov 2026 · Analysed npm/@tronrental-com/mcp-server@2.0.0
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 92 packages
| Packages resolved | 92 |
|---|---|
| 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 →
create_api_key ~106
Create the API key that unlocks the full tool set in this session and keeps access afterwards (the user saves it as TRONRENTAL_API_KEY). Needs the sign-in token. Issued only once the account's top-ups reach the bar (100 TRX on tronrental.com); below it the call reports how much more to top up. The key is shown only once — tell the user to save it.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | Name of the key |
No output schema declared.
No examples provided.
get_balance ~21
The signed-in account's balance in TRX. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_deposit_address ~48
The TRX/USDT deposit address of the signed-in account. Show it to the user and ask them to top up; deposits are detected within about 30 seconds. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_energy_prices ~22
Current TronRental energy prices. No account needed. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
login ~62
Sign in to an existing TronRental account (the token is valid 1 hour). For an email with no account yet this starts registration instead: a code is mailed and verify_email_code creates the account.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| password | string | yes | – |
No output schema declared.
No examples provided.
register ~127
Start registration of a new TronRental account. Requires the user's REAL email — ask the user, never invent one: TronRental mails a 6-digit code there and the account is created only when that code is passed to verify_email_code. If the email already has an account, use login.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The user's own email: they will read the code from it | |
| language | string | – | Language of the email (en, ru, zh, ko, …) |
| password | string | yes | Min 8 chars with an uppercase, a lowercase letter and a digit |
No output schema declared.
No examples provided.
resend_email_code ~70
Mail a new confirmation code to the email given to register (expired or not received). The previous code stops working. At most 3 emails per hour per address.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | – | |
| language | string | – | Language of the email (en, ru, zh, ko, …) |
No output schema declared.
No examples provided.
verify_email_code ~107
Finish registration with the 6-digit code from the confirmation email. Creates the account with the password given to register and signs in. Ask the user for the code — do not guess: each address allows only 5 attempts per code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | 6-digit code from the email |
| string | yes | The same email that was passed to register | |
| password | string | – | Only if this MCP server restarted after register: the same password given to register |
No output schema declared.
No examples provided.
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
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. Rent TRON energy and bandwidth so USDT transfers cost less TRX: quotes, orders, balance. 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 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 8 tools: get_energy_prices, register, verify_email_code, resend_email_code, login, and 3 more. Their descriptions and schemas cost roughly 563 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 21 November 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.
What did VerifyMCP test on the io.github.tronrental-com/tronrental MCP server?
VerifyMCP ran 16 checks on io.github.tronrental-com/tronrental, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.