DomainScout

What DomainScout MCP server does

DomainScout MCP server validates domain ideas in bulk. An AI assistant can send up to 1,000 names in one request, including bare names such as acme, complete domains such as acme.io, or URLs such as https://acme.dev. Bare names are tested against the selected TLDs.

The response includes a concise report for the model and structured results for each input. Results can show available, likely available, taken, reserved, or unknown status. Available and likely available names can include registration dates, warnings, and links to buy the domain. Pricing comparisons cover Cloudflare, Porkbun, Namecheap, Spaceship, GoDaddy, Name.com, Dynadot, NameSilo, and Hover.

How it works

For each domain, DomainScout MCP server first checks DNS. It then queries the registry through RDAP, using WHOIS for TLDs without RDAP support or when RDAP cannot provide an answer. These checks distinguish a registered but unused domain from one that is not present in the registry. Results can also note when a registered domain is being deleted and may become available later.

Registrar confirmation is optional. When registrar API keys are configured, the server can confirm names that appear free, identify premium names, and detect reserved names or names that a registrar cannot sell. Without confirmation, a name that is absent from DNS and registry data is reported as likely_available, not as a confirmed purchase opportunity.

Setup and configuration

The package requires Node 20 or newer. A standard stdio configuration runs it with:

{
  "mcpServers": {
    "domainscout": {
      "command": "npx",
      "args": ["-y", "@dakaio/domainscout-mcp"]
    }
  }
}

DOMAINSCOUT_TLDS can set the default TLD list, such as com,net,ai,io. The tool's tlds argument overrides that default for names without a TLD. The server can also be installed from the Claude Desktop extension, added through the Cursor or VS Code installation links, or registered with Claude Code. From source, build with npm install && npm run build and run the resulting dist/index.js file.

Tools and capabilities

DomainScout MCP server exposes the read-only check_domains tool. Its main inputs are:

• domains: one to 1,000 names or domains.
• tlds: TLDs to try for names without one.
• confirm: whether to use configured registrar APIs, enabled by default.
• details: whether to include evidence from DNS, RDAP, WHOIS, and registrar checks.
• saved: previously selected domains to check again and retain in results.

The tool can return the cheapest known offer first, renewal pricing where it differs from the first year, and minimum-term costs when applicable. The bundled results panel can display registrar price tables, filter by TLD, save names, export free domains to CSV, and request related checks when the connected client supports MCP Apps and the relevant client actions.

Limitations and notes

The server does not brainstorm or register domains. The assistant supplies the candidate names, and check_domains only checks them; it never changes registrations. Network timeouts and rate limits can produce unknown results, which may require another check. API confirmation is optional, so likely_available is not equivalent to registrar-confirmed availability.

Clients that do not support the bundled MCP Apps interface receive the text report instead of the interactive panel. The project states that it runs on the user's machine and does not require an account or a hosted DomainScout server.