@unclaimed-sol/mcp

MCPcommunity
v1.3.1UnclaimedSOLMITUpdated 6d agonpmGitHub

The first Vibe Claiming MCP server: let AI agents scan and reclaim dormant SOL on Solana — rent from token accounts and spam NFTs, program buffers, deactivated stakes, and DeFi rewards. Dry-run + execution-token safety, local signing, keypair never leaves

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
247Downloads/wk
6d agoLast update
Reads these credentials
  • SOLANA_KEYPAIR_PATHAPI keyoptional

    Path to a Solana keypair JSON file. Enables Vibe Claiming (claim tools).

  • SOLANA_PRIVATE_KEYAPI keyoptional

    Alternative to SOLANA_KEYPAIR_PATH (base58 or JSON byte array). Prefer the keypair path.

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorUnclaimedSOL
LicenseMIT
Version1.3.1
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
Listed in Forge index+10/10
Publisher identity verified+0/20
Publisher: run `forge publish` from the package repo to claim ownership
Ed25519 publish signature+0/5
Included automatically when the publisher runs `forge publish`
Domain verification+0/5
Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
npm Trusted Publishing (Sigstore)+0/5
Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
npm maintainer match+0/5
Earned once your identity is verified above and that login is an npm maintainer of this package
CVE scan · clean+30/30
Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain
Provenance
Dependencies60 resolved · 1 with advisories
Tool surface4 tools · none privileged
Security scan✓ Cleanv1.3.1 · todayHow well does this scan work?
EvalsNone
IndexedAug 28, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

4 tools · none privileged
Statically extracted from the published packagev1.3.1 · 20h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

claim_rewardsClaim uncollected DeFi rewards (cashback, creator fees, and more) for a Solana wallet.

Claim uncollected DeFi rewards (cashback, creator fees, and more) for a Solana wallet.

No input schema was published for this tool.

claim_stakesClaim SOL from deactivated stake accounts.

Claim SOL from deactivated stake accounts.

No input schema was published for this tool.

claim_solClaim reclaimable SOL from dormant token and buffer accounts.

Claim reclaimable SOL from dormant token and buffer accounts.

No input schema was published for this tool.

scan_claimable_solScan a Solana wallet for SOL locked in dormant token accounts (incl. Token-2022) and program buffer accounts. Read-only — no transactions, no keypair needed. DeFi rewards and deactivated stakes are discovered via the claim_rewards and claim_stakes dry runs. To claim, enable Vibe Claiming (SOLANA_KE…

Scan a Solana wallet for SOL locked in dormant token accounts (incl. Token-2022) and program buffer accounts. Read-only — no transactions, no keypair needed. DeFi rewards and deactivated stakes are discovered via the claim_rewards and claim_stakes dry runs. To claim, enable Vibe Claiming (SOLANA_KE…

No input schema was published for this tool.

4 of 4 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

The first Vibe Claiming MCP server: let AI agents scan and reclaim dormant SOL on Solana — rent from token accounts and spam NFTs, program buffers, deactivated stakes, and DeFi rewards. Dry-run + execution-token safety, local signing, keypair never leaves

Keywords
mcpmcp-servermodel-context-protocolsolanasolweb3ai-agentagentagent-toolsclaudeclaude-codecursorsolana-rentrent-reclaimreclaim-solclose-token-accountsstake-accountsdefi-rewardswallet-cleanupvibe-claimingunclaimed-sol
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-02 — observed resolution, not a publisher declaration.

60 packages resolved · 5 direct · 1 carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

58 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+46 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in crypto & web3