dotsweep
com.dotsweep/dotsweep · 1.2.1
Domain availability across 1,200+ TLDs, with renewal price, minimum term and eligibility
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://dotsweep.com/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 4 tools.
- Protocol
- 2025-06-18
- Calls itself
- dotsweep 0.1.0
- Handshake time
- 64 ms
- HTTP status
- 200
The tools it lists (4, as of 5 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
check_domainsChecks 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 acros
whoisRegistry 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
list_tldsEvery 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 belon
watch_domainRegister 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 re
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.dotsweep/dotsweep, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 70 days ago. The registry entry · dotsweep.com