Read the three.ws vanity-address grind-bounty market and proof-of-grind rarity gallery from any AI agent. Quote a pattern's difficulty + USDC price, appraise any address's rarity, and browse the bounty board, claimable queue, stats, leaderboard, config, and gallery. Read-only — no key, no signer, no payment.
Eight read-only tools with strong naming (verb_noun pattern), comprehensive descriptions (150-250 chars each), and complete Zod schemas. All parameters are typed and described. Tool annotations (readOnlyHint, idempotentHint, openWorldHint) are present and correct. Output schemas are not explicitly documented in the visible code, and error handling is minimal (generic try-catch). Composition is clean, each tool has one responsibility. Naming is clear and consistent (vanity_* prefix). No security issues detected (read-only, no secrets). Descriptions are LLM-optimized and include context on when to use each tool.
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.
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.
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.
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.
Output schemas not documented in tool definitions. LLMs cannot predict response structure or plan downstream chaining.
Error handling is generic (try-catch with basic error object). No recovery guidance, categorization (retryable vs fatal), or actionable error messages for LLM self-correction.
Pagination tools (vanity_board, vanity_gallery) accept limit and offset but do not document total count or next_cursor in response. LLMs cannot determine if more results exist.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 59 | 2026-07-28+ | v2 |
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.
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.
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.
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.
No batch variants for tools agents might call in loops. If an agent needs to appraise 10 addresses, it must make 10 sequential calls instead of one batch call.
STDIO transport only, not remotely accessible. Cannot be used by hosted MCP clients or cloud-based agents. Limits deployment scenarios.