Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.nedim1511/unclaimed-sol

NPM · @UNCLAIMED-SOL/MCP

The first Vibe Claiming MCP: AI agents scan and reclaim dormant SOL on Solana. Signs locally.

Available components

0 this week 83 Trust /100

Last scanned (20 hours ago)

Scores higher than 77% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security89
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects uuid 8.3.2, reached via @solana/web3.js > jayson > uuid. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 49 of 176 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 105 tokens (~105/item across 1 items; 1 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
Changelog

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.

  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: 0.97 → pass security
    • Package version: 1.3.1 → 2.0.0 functional
  • 29 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 28 Oct 26 0
    • Package version: 1.2.4 → 1.3.1 functional
  • 23 Oct 26 +1
    • Stability: 0.97 → pass security
  • 22 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 16 Oct 26 +1
    • Stability: 0.97 → pass security
  • 14 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

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 4 Nov 2026 · Analysed npm/@unclaimed-sol/mcp@2.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 4 findings
ID CVE Severity Vector Fix available
GHSA-528h-pc64-c93x CVE-2026-71429 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-hqr4-qq8f-hg3x CVE-2026-104182 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mjw6-4jj6-33hc CVE-2026-104183 medium CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L yes
GHSA-w5hq-g745-h8pq CVE-2026-41907 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 176 packages
Packages resolved 176
Deprecated 1
Stale 48
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~105 tokens

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 →

Tool Tokens
scan_claimable_sol ~105

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_KEYPAIR_PATH) or visit unclaimedsol.com.

NameTypeReqDescription
wallet_addressstringyesSolana wallet address (base58 public key)

No output schema declared.

No examples provided.

Install

How do I install the io.github.nedim1511/unclaimed-sol MCP server?

io.github.nedim1511/unclaimed-sol runs locally as an npm package, launched with npx -y @unclaimed-sol/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @unclaimed-sol/mcp

# add to Claude Code
claude mcp add nedim1511-unclaimed-sol -- npx -y @unclaimed-sol/mcp
Common questions

What is the io.github.nedim1511/unclaimed-sol MCP server?

io.github.nedim1511/unclaimed-sol is an MCP server listed in the public MCP registry as io.github.nedim1511/unclaimed-sol. The first Vibe Claiming MCP: AI agents scan and reclaim dormant SOL on Solana. Signs locally. This page covers its npm package (@unclaimed-sol/mcp).

Is the io.github.nedim1511/unclaimed-sol MCP server safe to use?

io.github.nedim1511/unclaimed-sol scores 83 out of 100 on VerifyMCP. We recorded 4 known advisories against it as of 4 November 2026. It declares no install or post-install scripts. 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 io.github.nedim1511/unclaimed-sol MCP server expose?

io.github.nedim1511/unclaimed-sol exposes 1 tool: scan_claimable_sol. Their descriptions and schemas cost roughly 105 tokens of context every time the server is loaded.

Is the io.github.nedim1511/unclaimed-sol MCP server still maintained?

io.github.nedim1511/unclaimed-sol is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.nedim1511/unclaimed-sol MCP server under?

io.github.nedim1511/unclaimed-sol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.