sweepdot
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
sweepdot
Ask the registries directly, from your own machine's tool list. sweepdot is a local forwarding client for the hosted dotsweep MCP service: it answers tools/list locally from the captured tool definitions and forwards every lookup to dotsweep, returning the answers exactly as the service sends them back.
The built surface covers domain availability with registration and renewal prices, WHOIS registry records for a single domain, and the catalogue of checkable extensions with their prices and eligibility rules. Nothing is cached, stored or computed locally — the package is a pipe, not a registrar.
This is a labelled subset rebuild: the upstream capture enumerates four tools, and three are built here. The remaining one, watch_domain, registers a watch that emails a caller-supplied address when a domain becomes registrable, so it is omitted — not registered, not served in tools/list, and not available on the CLI.
The tools
check_domains— Checks whether domain names are available, with registration and renewal prices, answered from the registry itself.namesis required: bare names are expanded across the extensions intlds, and names with a dot are checked exactly as given. Unconfirmed registries are reported as unconfirmed, never as available.whois— The registry record for one domain: registrar, registration and expiry dates, nameservers, status codes, and whether it appears to be for sale.domainis required.list_tlds— Every extension the service can check, with registration and renewal price, minimum registration term, and any eligibility restriction. No parameters; call it beforecheck_domainswhen the extensions to check are not yet decided.
Related MCP server: Domain Checker
Install and run
As an MCP server via npm:
npx -y @reneturcios/sweepdot mcpMCP client configuration:
{
"mcpServers": {
"sweepdot": {
"command": "npx",
"args": ["-y", "@reneturcios/sweepdot", "mcp"]
}
}
}As a container:
docker run -i ghcr.io/cloudcorprecords/sweepdot
docker run --rm ghcr.io/cloudcorprecords/sweepdot whois '{"domain":"example.com"}'CLI
One binary serves both the command line and the MCP server. Each tool is a subcommand taking a single JSON string with that tool's arguments:
sweepdot check_domains '{"names":["mybakery"],"tlds":["de","com"]}'
sweepdot whois '{"domain":"example.com"}'
sweepdot list_tlds '{}'
sweepdot --versionExit codes: 0 when the forwarded call succeeds, 1 when the upstream result is an error, and 2 for usage problems such as an unknown subcommand or a malformed JSON argument.
Configuration
DOTSWEEP_MCP_URL— Overrides the upstream endpoint. The default is the pinned hosted endpoint,https://dotsweep.com/mcp. (The override variable is a reconstruction added by this rebuild.)
The upstream registry record declares no headers, so no authentication header is ever sent; the tool surface was captured keyless.
Upstream failures — a JSON-RPC error from the service, a non-2xx response, an unreadable body, or a request that fails outright — are reported to the caller as an error result whose text starts with sweepdot error:.
How forwarding works
The first forwarded call opens a session: an initialize request (protocol version 2025-03-26), followed by a notifications/initialized notification, then the tools/call itself. If the service answers the initialize request with an Mcp-Session-Id header, that value is carried on every later request, and the open session is reused for the rest of the process. Replies are accepted either as plain JSON or as server-sent events. Successful results pass through verbatim, including any isError flag and any extra fields the service includes.
Development
npm install
npm run build # tsc -> dist/ (dist/cli.js is the bin)
npm test # tsx --test test/*.test.ts — stubbed upstream, no network
npm run dev # run the CLI from sourceThe test suite checks the served tool list against the captured surface, asserts the omitted watch_domain tool is absent at the registry, MCP and CLI levels, exercises the session handshake and its reuse, verifies that no Authorization header is ever sent, and verifies that arguments go upstream untouched and results come back untouched.
License
MIT — see LICENSE. Copyright (c) 2026 Rene Turcios.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Domain availability search, WHOIS lookup, TLD pricing and registry rules from name.ai. Read-only.
Check domain availability and prices, and look up any domain's public records. Read-only.
Check domain name availability via RDAP. Single, bulk, and smart suggestions. No API key needed.
Check domain availability and live registry pricing, or search for available names.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables checking domain name availability using WHOIS lookups and DNS resolution. Supports both single and batch domain checking with detailed availability analysis.-
- FlicenseNot gradedqualityDmaintenanceEnables checking domain availability using WHOIS and DNS resolution, with support for single and batch queries.29-
- AlicenseAqualityDmaintenanceEnables checking domain name availability for single or multiple domains using WHOIS and DNS verification.131 PyPI21MIT
- AlicenseAqualityDmaintenanceEnables fast domain availability checking via hybrid DNS and RDAP/WHOIS verification, with support for bulk queries and automatic name expansion across popular TLDs.355 npmMIT