Solana Cleanup
REMOTE · RECOVERSOLRENT.COM
Read-only Solana and crypto reserve-recovery scans, pricing, chain facts, and methodology.
Available components
Last scanned (4 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 178 tokens (~44/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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.
- 2 Oct 26 0
- Stability: fail → pass ▲ security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Sept 26 0
- Tool “recoversolrent.get_pricing” rewrote its description, which is the text the model reads security
- 2 Sept 26 0
- Stability: unverified → fail ▼ security
- Tool “recoversolrent.scan_reserves” was removed ▼ security
- Tool “recoversolrent.get_pricing” rewrote its description, which is the text the model reads security
- Tool “recoversolrent.get_supported_chains” rewrote its description, which is the text the model reads security
- Tool coverage: 75% → 100% ▲ functional
- Schema quality: 60 → 45 ▲ functional
- Server version: 1.0.0 → 1.1.0 functional
- Tool “recoversolrent.get_supported_chains” changed its title: List supported recovery chains → Get supported Solana network cosmetic
- 1 Sept 26 0
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 5 Nov 2026 · Probed https://recoversolrent.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=recoversolrent.com | CN=YR2,O=Let's Encrypt,C=US | 1 Nov 2026 | 30 Jan 2027 | RSA 2048 | SHA256-RSA | 5c9fa0df496dcc295d7840f4ac2d9e75354 |
| SANs: recoversolrent.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of recoversolrent.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| recoversolrent.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=63072000 |
| content-security-policy | default-src 'self'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self' data:; connect-src 'self' https://api.mainnet.solana.com https://*.helius-rpc.com https://*.quiknode.pro wss:; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recoversolrent.com/mcp | Verified | 200 | |
| http (plaintext) | http://recoversolrent.com/mcp | HTTPS enforced | 308 | https://recoversolrent.com/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 →
recoversolrent.get_methodology Get recovery methodology ~31
Return the product safety boundary, exact-versus-estimate policy, and canonical documentation links.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recoversolrent.get_pricing Get Recover SOL Rent pricing ~32
Return the disclosed success fee, atomic on-chain referral split, and whether fee collection is configured.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recoversolrent.get_supported_chains Get supported Solana network ~25
Return the single supported recovery network and its execution boundary.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
recoversolrent.scan_solana Scan Solana token accounts ~63
Read public Solana account state and identify empty token accounts, possible dust balances, possible NFTs, and current rent held by each account. This never creates or signs a transaction.
| Name | Type | Req | Description |
|---|---|---|---|
| wallet | string | yes | A base58 Solana public wallet address. |
No output schema declared.
No examples provided.
How do I install the Solana Cleanup MCP server?
Solana Cleanup is a hosted endpoint at https://recoversolrent.com/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 · recoversolrent.com
claude mcp add --transport http com-recoversolrent-solana-cleanup 'https://recoversolrent.com/mcp'
What is the Solana Cleanup MCP server?
Solana Cleanup is an MCP server listed in the public MCP registry as com.recoversolrent/solana-cleanup. Read-only Solana and crypto reserve-recovery scans, pricing, chain facts, and methodology. This page covers its hosted endpoint (https://recoversolrent.com/mcp).
Is the Solana Cleanup MCP server safe to use?
Solana Cleanup scores 88 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 Solana Cleanup MCP server expose?
Solana Cleanup exposes 4 tools: recoversolrent.scan_solana, recoversolrent.get_pricing, recoversolrent.get_supported_chains, recoversolrent.get_methodology. Their descriptions and schemas cost roughly 151 tokens of context every time the server is loaded.
Does the Solana Cleanup MCP server require authentication?
No. We connected to Solana Cleanup without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Solana Cleanup MCP server still maintained?
Solana Cleanup is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.