# UNRENT (remote · unrent.xyz)

Reclaim overpaid rent from Solana token accounts (SIMD-0437). Non-custodial, no API key.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `unrent.xyz`: 69/100 (this document), [markdown](https://verifymcp.io/servers/xyz-unrent-unrent/unrent.md), [page](https://verifymcp.io/servers/xyz-unrent-unrent/unrent)

## Channel facts

- Endpoint: `https://unrent.xyz/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 66/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (submit_reclaim).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http xyz-unrent-unrent 'https://unrent.xyz/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "xyz-unrent-unrent": {
      "url": "https://unrent.xyz/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "xyz-unrent-unrent": {
      "type": "http",
      "url": "https://unrent.xyz/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.xyz-unrent-unrent]
url = "https://unrent.xyz/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-unrent-unrent": {
      "type": "remote",
      "url": "https://unrent.xyz/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-unrent-unrent --url 'https://unrent.xyz/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-unrent-unrent:
    url: "https://unrent.xyz/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "xyz-unrent-unrent": {
      "Transport": "http",
      "Url": "https://unrent.xyz/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add xyz-unrent-unrent -t streamable-http -u 'https://unrent.xyz/mcp'
```

### Other

```json
{
  "mcpServers": {
    "xyz-unrent-unrent": {
      "type": "http",
      "url": "https://unrent.xyz/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 69, +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.

### 2026-10-15 (score 68, +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.

### 2026-10-13 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-12 (score 66)

First indexed and scored.

## MCP tools (4)

### `get_rent_status` (~66 tokens)

Solana rent reduction status (SIMD-0437)

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.

### `scan_wallet` (~180 tokens)

Scan a wallet for reclaimable rent

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.

Input parameters:

- `ref` (string): Optional UNRENT referral code. The referrer gets a share of the service fee; the wallet pays the same.
- `wallet` (string, required): Solana wallet address (base58).

### `build_reclaim` (~245 tokens)

Build the reclaim transactions

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.

Input parameters:

- `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, required): Solana wallet address (base58).

### `submit_reclaim` (~98 tokens)

Send the signed reclaim

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.

Input parameters:

- `claimId` (string, required): claimId from the build.
- `signed` (array, required): The signed transactions, base64, in the order the build returned them.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-unrent-unrent/unrent#diagnostics

## Score history

- 2026-10-17: 69
- 2026-10-16: 68
- 2026-10-15: 68
- 2026-10-14: 67
- 2026-10-13: 67
- 2026-10-12: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://unrent.xyz/mcp
- Website: https://unrent.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-unrent-unrent/unrent.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-unrent-unrent/unrent.json
- HTML version of this page: https://verifymcp.io/servers/xyz-unrent-unrent/unrent