Unclaimed Sol Scanner

Created By
unclaimed-sol4 months ago
Scan and claim reclaimable SOL from dormant Solana wallet accounts. The first Vibe Claiming MCP server.
Overview

Every Solana wallet accumulates locked SOL in dormant token accounts — dead memecoins, old airdrops, empty ATAs. This MCP server lets AI assistants find and reclaim it.

Two tools:

scan_claimable_sol — Check any wallet for reclaimable SOL. Read-only, no keypair needed.

claim_sol — Vibe Claiming. Burns worthless token balances, closes dormant accounts, and reclaims the rent SOL. Transactions are built and signed locally — your private key never leaves your machine.

How it works:

  • You: "scan my wallet for reclaimable SOL"
  • AI: "Found 0.58 SOL across 277 dormant accounts"
  • You: "claim it"
  • AI: builds transactions, signs locally, broadcasts to Solana

No browser. No dApp. No wallet connect. Just ask your AI and it does it.

A 5% service fee is collected on-chain by the UnclaimedSOL program. Stake account claims are available at unclaimedsol.com.

Works with Claude Code, Claude Desktop, Cursor, Windsurf, and any MCP-compatible client.

Server Config

{
  "mcpServers": {
    "unclaimed-sol": {
      "command": "node",
      "args": [
        "/absolute/path/to/unclaimed-sol-mcp/dist/index.js"
      ],
      "env": {
        "SOLANA_KEYPAIR_PATH": "~/.config/solana/id.json",
        "SOLANA_RPC_URL": "https://your-rpc-provider.com"
      }
    }
  }
}
Project Info
Created At
4 months ago
Updated At
4 months ago
Author Name
unclaimed-sol
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

5 hours ago