UNRENT
REMOTE · UNRENT.XYZ
Reclaim overpaid rent from Solana token accounts (SIMD-0437). Non-custodial, no API key.
Available components
Last scanned (6 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 17 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_reclaim). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 772 tokens (~193/item across 4 items; 4 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 Management17
- Stability observed for 5 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
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.
- 17 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 12 Oct 26 66
First indexed and scored.
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 17 Oct 2026 · Probed https://unrent.xyz/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=unrent.xyz | CN=YE1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 52667b35f039ee8bd0675bf7a84d2884bd5 |
| SANs: unrent.xyz | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of unrent.xyz. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| xyz. | present | 3599, 18130 | 8, 8 | Verified |
| unrent.xyz. | present | 49090 | 13 | Verified |
| unrent.xyz. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://unrent.xyz/mcp | Verified | 200 | |
| http (plaintext) | http://unrent.xyz/mcp | HTTPS enforced | 301 | https://unrent.xyz/mcp |
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 →
build_reclaim Build the reclaim transactions ~245
Re-scans the wallet on the chain and builds the reclaim as unsigned, simulated Solana transactions (base64, versioned). They withdraw excess rent, close empty accounts and pay the service fee as the last instruction; nothing else leaves the wallet. Tokens are only burned for accounts listed in `burn`. The wallet's owner signs every transaction unchanged (the fee payer is the wallet, compute budget instructions may be added) and passes them to submit_reclaim within about 60 seconds, before the blockhash expires. Do not send them yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| accounts | array | – | Only these account addresses (from a scan). Default: everything reclaimable. |
| burn | array | – | Token accounts to burn and close (from the scan's burn.candidates). Only when the wallet owner explicitly asked for it. |
| burnMaxUsd | number | – | Highest USD value per account that may be burned (capped by burn.cleanupMaxUsd). Dust is burned regardless. |
| ref | string | – | Optional UNRENT referral code. The referrer gets a share of the service fee; the wallet pays the same. |
| wallet | string | yes | Solana wallet address (base58). |
No output schema declared.
No examples provided.
get_rent_status Solana rent reduction status (SIMD-0437) ~66
Where Solana's rent reduction (SIMD-0437) stands: the live lamports_per_byte, which of the five steps are live, and when the next is expected. Older accounts keep their higher deposit until it is withdrawn; each step makes more SOL reclaimable.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
scan_wallet Scan a wallet for reclaimable rent ~180
Reads the token accounts and mints of a Solana wallet and returns the SOL that can be reclaimed now: excess rent (WithdrawExcessLamports, accounts stay open), empty token accounts (CloseAccount) and mint excess, the UNRENT service fee, the net amount, a forecast for the remaining rent steps, and tokens that may optionally be burned and closed (dust). Read-only, needs no signature. Amounts are in SOL. Also returns signUrl: a link to finish the reclaim on unrent.xyz with a browser wallet (Phantom, Solflare, Backpack…), for when you cannot sign for the wallet yourself.
| Name | Type | Req | Description |
|---|---|---|---|
| ref | string | – | Optional UNRENT referral code. The referrer gets a share of the service fee; the wallet pays the same. |
| wallet | string | yes | Solana wallet address (base58). |
No output schema declared.
No examples provided.
submit_reclaim Send the signed reclaim ~98
Checks the signed transactions against the ones build_reclaim made (same instructions, same fee, signed by the wallet) and sends them to Solana. Returns the signature and status of every transaction. A claim can be submitted once; after an expired blockhash, build again.
| Name | Type | Req | Description |
|---|---|---|---|
| claimId | string | yes | claimId from the build. |
| signed | array | yes | The signed transactions, base64, in the order the build returned them. |
No output schema declared.
No examples provided.
How do I install the UNRENT MCP server?
UNRENT is a hosted endpoint at https://unrent.xyz/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · unrent.xyz
claude mcp add --transport http xyz-unrent-unrent 'https://unrent.xyz/mcp'
What is the UNRENT MCP server?
UNRENT is an MCP server listed in the public MCP registry as xyz.unrent/unrent. Reclaim overpaid rent from Solana token accounts (SIMD-0437). Non-custodial, no API key. This page covers its hosted endpoint (https://unrent.xyz/mcp).
Is the UNRENT MCP server safe to use?
UNRENT scores 69 out of 100 on VerifyMCP. 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 UNRENT MCP server expose?
UNRENT exposes 4 tools: get_rent_status, scan_wallet, build_reclaim, submit_reclaim. Their descriptions and schemas cost roughly 589 tokens of context every time the server is loaded.
Does the UNRENT MCP server require authentication?
No. We connected to UNRENT without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the UNRENT MCP server still maintained?
UNRENT is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.