snooze
REMOTE · MCP.SNOOZE.DOMAINS · SCANNED SEP 24
Watch domains and forecast when they drop; check a name's domain, handles, and trademark.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (unwatch_domains). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 368 tokens (~73/item across 5 items; 5 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 5 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
How do I install the snooze MCP server?
snooze is a hosted endpoint at https://mcp.snooze.domains/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.snooze.domains
claude mcp add --transport http domains-snooze-snooze 'https://mcp.snooze.domains/mcp'
{
"mcpServers": {
"domains-snooze-snooze": {
"url": "https://mcp.snooze.domains/mcp"
}
}
} {
"servers": {
"domains-snooze-snooze": {
"type": "http",
"url": "https://mcp.snooze.domains/mcp"
}
}
} [mcp_servers.domains-snooze-snooze] url = "https://mcp.snooze.domains/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"domains-snooze-snooze": {
"type": "remote",
"url": "https://mcp.snooze.domains/mcp",
"enabled": true
}
}
} openclaw mcp add domains-snooze-snooze --url 'https://mcp.snooze.domains/mcp' --transport streamable-http
mcp_servers:
domains-snooze-snooze:
url: "https://mcp.snooze.domains/mcp" {
"McpServers": {
"domains-snooze-snooze": {
"Transport": "http",
"Url": "https://mcp.snooze.domains/mcp"
}
}
} assistant mcp add domains-snooze-snooze -t streamable-http -u 'https://mcp.snooze.domains/mcp'
{
"mcpServers": {
"domains-snooze-snooze": {
"type": "http",
"url": "https://mcp.snooze.domains/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 26 Aug 26 79
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
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 24 Sept 2026 · Probed https://mcp.snooze.domains/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=snooze.domains | CN=YE2,O=Let's Encrypt,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5e1fc6360d3a2f85399834f5e8921f5a59c |
| SANs: *.snooze.domains, snooze.domains | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.snooze.domains. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| domains. | present | 39406 | 8 | Verified |
| snooze.domains. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.snooze.domains/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.snooze.domains/mcp | HTTPS enforced | 301 | https://mcp.snooze.domains/mcp |
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 →
check_domains Check domains ~108
Check the registration status of one or more domains — whether each is taken, expiring, in redemption, in pendingDelete, or available to register. Returns status, expiry, registrar, name servers, EPP codes, and a buyer-focused drop forecast (predicted release window and confidence) for names in their lapse cycle. No authentication required. Up to 20 domains per call.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Domain names to check, e.g. ["example.com", "acme.io"] |
No output schema declared.
No examples provided.
check_name Check a brand name ~89
Name Safety Check for a brand name: domain availability across .com/.io/.ai/.app/.dev/.co, social-handle availability (best effort), and a US trademark knockout search of public USPTO records. Returns structured results. This is a knockout search, not legal advice. No authentication required.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | A brand name to check, e.g. "acme" |
No output schema declared.
No examples provided.
list_watches List watched domains ~46
List every domain on your snooze watchlist with its current status and drop forecast — so an agent can see what it is already tracking. Requires signing in to your snooze account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
unwatch_domains Stop watching domains ~42
Remove one or more domains from your snooze watchlist. Requires signing in to your snooze account.
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Domain names to stop watching |
No output schema declared.
No examples provided.
watch_domains Watch domains ~83
Add one or more domains to your snooze watchlist. Each is monitored continuously and you get an email when its status changes or it nears a drop. Requires signing in to your snooze account. Up to 25 domains per call (100 total).
| Name | Type | Req | Description |
|---|---|---|---|
| domains | array | yes | Domain names to watch, e.g. ["example.com", "acme.io"] |
No output schema declared.
No examples provided.
What is the snooze MCP server?
snooze is an MCP server listed in the public MCP registry as domains.snooze/snooze. Watch domains and forecast when they drop; check a name's domain, handles, and trademark. This page covers its hosted endpoint (https://mcp.snooze.domains/mcp).
Is the snooze MCP server safe to use?
snooze scores 79 out of 100 on VerifyMCP. 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 snooze MCP server expose?
snooze exposes 5 tools: check_domains, check_name, watch_domains, unwatch_domains, list_watches. Their descriptions and schemas cost roughly 368 tokens of context every time the server is loaded.
Does the snooze MCP server require authentication?
No. We connected to snooze without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the snooze MCP server still maintained?
snooze is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.