three.ws Vanity
NPM · @THREE-WS/VANITY-MCP
Read the three.ws vanity-address market: quote difficulty + USDC price, browse the board.
Available components
Last scanned (6 hours ago)
Scores higher than 61% of npm servers
Category Crypto and Web3
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. 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 (Apache-2.0).Pass
- Actively maintained (last published 54 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1140 tokens (~142/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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.
- 4 Nov 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +3
- Stability: 0.80 → pass security
- 16 Oct 26 −3
- Stability: pass → 0.80 functional
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 · Analysed npm/@three-ws/vanity-mcp@0.1.3
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 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
vanity_appraise Appraise the rarity of a Solana address ~136
Appraise how rare a Solana address is: its detected vanity pattern, rarity score, rarity bits, tier, and expected grind attempts. Pure math on the Base58 address — nothing is stored. If the address has been published to the proof-of-grind gallery, the public entry is returned too. Read-only, no payment.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | The Base58 Solana public key to appraise (32–44 chars). |
| prefixLen | integer | – | Override how many leading characters to treat as the pattern prefix. |
| suffixLen | integer | – | Override how many trailing characters to treat as the pattern suffix. |
No output schema declared.
No examples provided.
vanity_board Browse the vanity grind-bounty board ~166
Browse the public grind-bounty board: vanity-address bounties requesters have escrowed for the worker fleet to grind. Filter by status (open / all / settled), sort by recency, reward, or expiry, and paginate. Each bounty shows its pattern, USDC amount, difficulty, status, and timing. Read-only; posting a bounty is a separate x402-paid write on the HTTP API.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max bounties to return (1–100, default 24). |
| offset | integer | – | Pagination offset (default 0). |
| sort | string | – | Order: newest first, biggest reward first, or soonest to expire. Default recency. |
| status | string | – | Which bounties to list. Default open. |
No output schema declared.
No examples provided.
vanity_config Bounty market config: payout + asset metadata ~91
Read the grind-bounty market configuration: whether on-chain payouts are configured (can a winner actually be paid?), the settlement asset (USDC) and its decimals, which escrow networks are live (Base / Solana), the pricing band (floor + max atomics), the bounty protocol version, and the sealed-envelope scheme. Check this before posting to confirm the market can pay out. Read-only, no params.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
vanity_gallery Browse the proof-of-grind rarity gallery ~180
Browse the public proof-of-grind gallery: rare Solana addresses people have published with a verifiable grind receipt. Sort by rarity score or recency, filter by tier, minimum pattern length, or a substring the pattern must contain, and paginate. Each entry shows the address, pattern, rarity score/bits, tier, and an explorer link. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | string | – | Only addresses whose vanity pattern contains this substring. |
| limit | integer | – | Max entries to return (1–100, default 24). |
| minLength | integer | – | Only patterns at least this many characters long. |
| offset | integer | – | Pagination offset (default 0). |
| sort | string | – | Order by rarity score (rarest first) or recency. Default score. |
| tier | string | – | Filter to a single rarity tier id. |
No output schema declared.
No examples provided.
vanity_leaderboard Top grinders by USDC earned ~66
Rank the worker fleet: the top grinders by total USDC earned from winning vanity-address bounties. Each entry shows a worker id and its cumulative payout. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | How many top grinders to return (1–100, default 10). |
No output schema declared.
No examples provided.
vanity_open List claimable open bounties for workers ~97
List the open, unexpired bounties a grinding worker can race to claim — the queue worker fleets poll. Each entry carries the pattern to grind and the escrowed USDC reward; the first worker to submit a verified, sealed key wins. Read-only discovery; submitting a claim is a separate write on the HTTP API.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max claimable bounties to return (1–100, default 30). |
No output schema declared.
No examples provided.
vanity_quote Quote the bounty price for a vanity pattern ~152
Quote how hard a Solana vanity address is and what to escrow for it. Give a Base58 prefix and/or suffix and get the expected attempts, rarity tier, and an honest suggested USDC bounty (atomic units) from the difficulty→price oracle. Pure function of the pattern — no wallet, no payment, fully read-only. Use this before posting a grind-bounty so you escrow a fair amount.
| Name | Type | Req | Description |
|---|---|---|---|
| ignoreCase | boolean | – | Match the pattern case-insensitively (cheaper, less rare). Default false. |
| prefix | string | – | Base58 prefix the address must start with (e.g. "THREE"). |
| suffix | string | – | Base58 suffix the address must end with. |
No output schema declared.
No examples provided.
vanity_stats Live grind-bounty market totals ~59
Get live totals for the grind-bounty market: how many bounties are open, how much USDC is currently escrowed, and how much has been paid out to winning workers. A quick pulse on market activity. Read-only, no params.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the three.ws Vanity MCP server?
three.ws Vanity runs locally as an npm package, launched with npx -y @three-ws/vanity-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 · @three-ws/vanity-mcp
claude mcp add nirholas-vanity-mcp -- npx -y @three-ws/vanity-mcp
What is the three.ws Vanity MCP server?
three.ws Vanity is an MCP server listed in the public MCP registry as io.github.nirholas/vanity-mcp. Read the three.ws vanity-address market: quote difficulty + USDC price, browse the board. This page covers its npm package (@three-ws/vanity-mcp).
Is the three.ws Vanity MCP server safe to use?
three.ws Vanity scores 79 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 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 three.ws Vanity MCP server expose?
three.ws Vanity exposes 8 tools: vanity_quote, vanity_appraise, vanity_board, vanity_open, vanity_stats, and 3 more. Their descriptions and schemas cost roughly 947 tokens of context every time the server is loaded.
Is the three.ws Vanity MCP server still maintained?
three.ws Vanity 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.
What licence is the three.ws Vanity MCP server under?
three.ws Vanity declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.