snooze.domains
https://server.smithery.ai/snooze/snooze-mcp/mcp**snooze.domains** watches domains you want and tells your assistant the moment they free up — with a drop-date forecast no other domain tool gives you. It also runs a one-shot **Name Safety Check** for a brand name (domain + social handles + US trademark), and bulk-checks domain status. Free. ### Tools - **`check_domains`** — status of up to 20 domains at once (taken / expiring / redemption / pendingDelete / available) with expiry, registrar, and a buyer-focused **drop forecast** — when the name is likely to become available. - **`check_name`** — Name Safety Check for a brand name: domain availability across .com/.io/.ai/.app/.dev/.co, social handles, and a US trademark knockout search. - **`watch_domains`** — add domains to your watchlist; snooze monitors them and emails you when status changes or a drop nears. *(sign-in)* - **`list_watches`** — everything you're watching, with live status + drop forecast. *(sign-in)* - **`unwatch_domains`** — stop watching. *(sign-in)* ### Why snooze - **Drop forecasting** — for a name in its lapse cycle, snooze predicts *when* it could free up (e.g. "≈ 5 days" in pendingDelete), not just "it's taken." - **Stateful** — it remembers your watchlist across sessions and keeps checking; an agent can't hold that state on its own. - Reads public **RDAP / WHOIS / DNS** only, and hands registration off to any registrar — it's a watcher, not a backorder service. `check_domains` and `check_name` need no account; watching authenticates once via Google (OAuth) the first time.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 73.3/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 25/25 | Endpoint answers the MCP initialize handshake (1788 ms). |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 30/30 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 5 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 95% of peers
- This listing 88 · peer median 81
- Latency
- Faster than 38% of peers
- This listing 431 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/snooze/snooze-mcp/mcpcurl -X POST https://server.smithery.ai/snooze/snooze-mcp/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'