three.ws Vanity
io.github.nirholasPublished by GitHub account nirholasv0.1.3Updated Oct 27, 2026
Read the three.ws vanity-address market: quote difficulty + USDC price, browse the board.
Overview
Read-only MCP server for the three.ws Solana vanity-address bounty market: quote pattern difficulty and USDC prices, appraise addresses, browse the board.
- What you can do
- Quote a vanity pattern: expected attempts, rarity tier and suggested USDC bounty
- Appraise any Solana address's rarity score, bits, tier and attempts
- Browse the bounty board and the claimable open-bounty queue with filters and paging
- Read live market stats, the top-grinder leaderboard and payout/asset config
- Browse the proof-of-grind rarity gallery by tier, length or substring
- When to use it
- Useful when you want an assistant to price or compare Solana vanity-address patterns, judge how rare an address is, or survey the three.ws bounty market and gallery without leaving the chat. It is a read-only discovery surface, so it suits research and quoting rather than posting or claiming bounties.
- Requirements
- Node.js 20 or newer, run via npx or a local install over stdio. Network access to three.ws; the optional THREE_WS_BASE variable points at another base URL and THREE_WS_TIMEOUT_MS sets the per-request timeout. No API key, signer or payment is needed.
Installation
In SourceWeft
- Open three.ws Vanity in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@three-ws/vanity-mcp
Read the three.ws vanity-address grind-bounty market + rarity gallery from any AI agent.
[npm] [license] [node] [MCP Registry] [three.ws]
A Model Context Protocol server that gives any AI assistant the read/discovery surface of the three.ws vanity-address grind-bounty market over stdio. Quote how hard a Solana vanity pattern is and what to escrow for it, appraise the rarity of any address, and browse the live bounty board, claimable queue, stats, leaderboard, config, and the proof-of-grind gallery.
The market is secret-blind: a requester escrows a USDC bounty for a pattern, a fleet of independent workers grinds it in parallel, and the first to submit a verified key matching the pattern is paid on-chain — yet the found secret is sealed to the requester, so the worker earns the bounty without ever seeing the wallet. Posting a bounty and claiming one are the x402-paid write paths on the HTTP API; this MCP exposes the read/discovery + rarity surface. No API key, no signer, no payment — every call hits the public /api/vanity endpoints.
Install
Or run with npx (no install):
Quick start
Claude Code, one line:
Claude Desktop / Cursor (claude_desktop_config.json or mcp.json):
Inspect the surface with the MCP Inspector:
Tools
vanity_quote and vanity_appraise are pure functions of their input (same pattern/address → same result), so they're marked idempotent. The other six read the live market and gallery.
Input parameters
vanity_quote — prefix (optional Base58 prefix), suffix (optional Base58 suffix), ignoreCase (bool, default false). At least one of prefix/suffix is required.
vanity_appraise — address (required, Base58 32–44 chars), prefixLen (int, optional), suffixLen (int, optional).
vanity_board — status (open | all | settled, default open), sort (recency | reward | expiry, default recency), limit (1–100, default 24), offset (default 0).
vanity_open — limit (1–100, default 30).
vanity_stats — no params.
vanity_leaderboard — limit (1–100, default 10).
vanity_config — no params.
vanity_gallery — sort (score | recency, default score), tier (string), minLength (int), contains (string), limit (1–100, default 24), offset (default 0).
Example
Examples
Runnable examples live in examples/:
Both spawn this server over stdio and read the live market. Every tool here is
read-only, so nothing can be posted, claimed, or paid. See
examples/README.md for expected output.
Requirements
- Node.js >= 20.
- Network access to
https://three.ws(or your ownTHREE_WS_BASE).
Environment variables
Links
- Homepage: https://three.ws
- Changelog: https://three.ws/changelog
- Issues: https://github.com/nirholas/three.ws/issues
- License: Apache-2.0, see LICENSE
Part of the three.ws SDK suite — 3D AI agents, on-chain identity, and agent payments.
Website · Changelog · GitHub
Source: packages/vanity-mcp/README.md at commit c8f2cde
Tools
0Version history
2- v0.1.3LatestOct 10, 2026
- v0.1.2Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts