dotsweep
REMOTE · DOTSWEEP.COM · SCANNED AUG 3
Domain availability across 1,200+ TLDs, with renewal price, minimum term and eligibility
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 →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS not yet verified: we couldn't determine whether a plaintext access path exists. View diagnostics → Unverified
- 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 Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1214 tokens (~303/item across 4 items; 4 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 Management10
- Stability observed for 3 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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · dotsweep.com
claude mcp add --transport http com-dotsweep-dotsweep https://dotsweep.com/mcp
[mcp_servers.com-dotsweep-dotsweep] url = "https://dotsweep.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dotsweep-dotsweep": {
"type": "remote",
"url": "https://dotsweep.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-dotsweep-dotsweep --url https://dotsweep.com/mcp --transport streamable-http
mcp_servers:
com-dotsweep-dotsweep:
url: "https://dotsweep.com/mcp" {
"mcpServers": {
"com-dotsweep-dotsweep": {
"type": "http",
"url": "https://dotsweep.com/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.
- 3 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Aug 26 0
- Schema quality: 994 → 1214 ▼ functional
- New tool “watch_domain” functional
- 1 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 31 Jul 26 53
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 3 Aug 2026 · Probed https://dotsweep.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=dotsweep.com | CN=WE1,O=Google Trust Services,C=US | 29 Jul 2026 | 27 Oct 2026 | ECDSA 256 | ECDSA-SHA256 | ac03948d67d6539d0e8ac20d1508efc5 |
| SANs: dotsweep.com, www.dotsweep.com, *.www.dotsweep.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of dotsweep.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| dotsweep.com. | 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 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; base-uri 'none'; form-action 'self'; frame-ancestors 'none'; object-src 'none'; img-src 'self' data:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://challenges.cloudflare.com; frame-src https://challenges.cloudflare.com; connect-src 'self' https://pubapi.registry.google |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://dotsweep.com/mcp | Verified | 200 | |
| http (plaintext) | http://dotsweep.com/mcp | Inconclusive | 405 |
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.
check_domains Check domain availability and price ~629
Checks whether domain names are available, with registration and renewal prices. Answers come from the registry itself: DNS delegation first, then RDAP, with a WHOIS fallback for the registries that publish no RDAP service. A registry that is throttled, timed out or unreachable is reported as unconfirmed, never as available — a raw whois query reports one as available, which is the one wrong answer that costs money. Covers .dev and .app, whose operators run no port-43 whois server at all, and resolves the right registry per extension without being told which. Accepts bare names (expanded across the given extensions) and exact domains (checked as-is). Returns availability, confidence, price, minimum registration term, any eligibility restriction, and where to buy. When a buy link has paid:true, show the response's top-level disclosure sentence alongside it — a commission is earned on that link and the reader is entitled to know before clicking. Each row in prices[] names the registrar it belongs to in vendor — quote the number with that registrar, and link the same one. buy[].url is the link to give; never compose a registrar URL yourself. Show the link for an available name in the same message as the verdict rather than waiting to be asked, and say so when renewal costs more than the first year or min_term_years makes the first bill a multiple of the price shown. confidence:estimated is not availability — it means no registry answered, usually because one was throttled, so present it as unconfirmed and never as a free name. A result carrying policy.closed is an extension that sells to nobody: it has no price and no buy link, and calling it available offers a name that cannot be bought at any price. When policy carries eligibility, say so before the price — a rule that turns the buyer away at checkout matters more than what they would have paid. Every quoted price is a floor: premium and reserved names return the same registry answer as an ordinary free one and can…
| Name | Type | Req | Description |
|---|---|---|---|
| names | array | yes | Brand names or exact domains. A name without a dot is checked across every extension in tlds; a name with a dot is checked exactly as given. |
| tlds | array | — | Extensions to check bare names against, without leading dots. Choose ones that fit the business: a bakery and an ML startup should not get the same list, and the person asking usually cannot name the… |
No output schema declared.
No examples provided.
list_tlds List checkable extensions with prices ~190
Every extension this server can check, with registration and renewal price, minimum registration term, and any eligibility restriction on who may register it. Use before check_domains when the extensions to check are not already decided: the catalogue is wider than the handful most people can name, prices vary by more than an order of magnitude, and min_term_years means the first bill can be a multiple of the price shown. An entry carrying vendor is priced by a registrar other than the one quoted by default, because that one does not sell the extension — the number is still real, it just belongs to the named registrar. An entry with no price at all means no registrar here sells it, which is a fact about this catalogue and not about the extension: several are sold perfectly well by registrars we hold no feed for, so an absent price leaves availability an open question rather than settling it. All prices are USD.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
watch_domain Get told when a taken domain becomes registrable ~220
Register a watch on a domain that is currently taken, and be emailed once — and only once — when the registry confirms it has become registrable. Use when someone wants a name that is already owned, or asks to be told when one expires or drops. It answers immediately and creates nothing when the name turns out to be free already, so it is safe to call on a domain whose status has not been established. It requires an email address the person supplied in the conversation. A confirmation mail is sent first and the watch stays inactive until its link is clicked, which is worth passing on in the reply. The address is stored against this one domain, is never used for anything else, and is used only for that notification. The notification fires only on a confirmed registry answer, never on an estimate: if a registry is unreachable the watch waits rather than reporting the name free.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A full domain, e.g. example.com |
| string | yes | Where to send the one notification. Must be given by the user. |
No output schema declared.
No examples provided.
whois Look up a domain's registry record ~175
Registry record for one domain: registrar, registration and expiry dates, nameservers, status codes, and whether it appears to be for sale. Resolves the correct registry host for the extension itself, and reads RDAP for .dev, .app and other extensions whose operators publish no port-43 whois service. Use when asked who owns a domain, when it expires, or where it is hosted. It forces a registry lookup, so it is also the only call that fills offer — a taken domain that appears to be parked or listed for sale. An offer is an inference from nameservers and a listing page, never a quote: the asking price lives on the listing and not in the registry, so link the listing rather than naming a figure.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | A full domain, e.g. example.com |
No output schema declared.
No examples provided.