Domain Radar

io.github.sonwrPublished by GitHub account sonwrv0.1.2Updated Oct 24, 2026

MCP server that checks domain availability in real-time during brand naming

VerifiedSTDIODesktop onlyWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Lets an assistant check whether domain names are available across many TLDs while brainstorming brand names.

What you can do
Domain Radar exposes four tools: check_domains for exact names, check_brand_domains for one name across 17 or more TLDs, suggest_and_check_domains to generate variations from keywords and check them, and list_supported_tlds. It resolves availability through DNS lookups and WHOIS queries, and reports results as available, taken, or unknown. A built-in brand-naming prompt guides a step-by-step naming session.
When to use it
Useful when naming a product, brand, or project and you want domain availability checked inside the same conversation instead of switching to a browser or terminal. Best suited to early naming and brainstorming work where many candidate names need quick screening.
Requirements
Runs as a local process installed from the npm package mcp-domain-radar, so Node.js and npm are needed; clients are configured with npx or a global install. No API keys or accounts are declared. Network access is required for WHOIS queries, while DNS checks can work offline.
Before you install
The server sends the candidate domain names it checks to DNS resolvers and WHOIS services, so unannounced product or brand names leave your machine. It only reads registration status; it does not register, buy, or reserve domains, and no payment or credentials are involved.

Installation

In SourceWeft

  1. Open Domain Radar in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

mcp-domain-radar

[domain-radar]

[npm version] [npm downloads] [license]

Works with
Claude Code · Claude Desktop · Cursor · Codex CLI · any MCP-compatible client

MCP server that checks domain availability in real-time during brand naming.

Name your brand. Check the domain. All in one conversation.

Why?

We've all been there:

You:    "Suggest a name for my service"AI:     "How about NexFlow?"You:     Search nexflow.com... already takenYou:    "Another one"AI:     "DataPulse?"You:     Search datapulse.com... also takenYou:    "..."        (repeat 10 times)

Install mcp-domain-radar once, and your AI checks domain availability the moment it thinks of a name. No more switching between browser and terminal.

Quick Start

1. Install

bash
npm install -g mcp-domain-radar

2. Connect to your AI coding tool

Claude Code
bash
claude mcp add domain-radar -- mcp-domain-radar
Codex CLI
bash
codex mcp add domain-radar -- npx mcp-domain-radar
Cursor

Add to .cursor/mcp.json:

json
{  "mcpServers": {    "domain-radar": {      "command": "npx",      "args": ["mcp-domain-radar"]    }  }}
Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "domain-radar": {      "command": "npx",      "args": ["mcp-domain-radar"]    }  }}

3. Install the brand-naming skill (optional, Claude Code only)

bash
mkdir -p ~/.claude/skills/brand-namingcp node_modules/mcp-domain-radar/.claude/skills/brand-naming/SKILL.md ~/.claude/skills/brand-naming/

Or copy it manually from the GitHub repo.

4. Use it

With the skill installed, type /brand-naming in Claude Code to start a guided naming session.

Or just talk naturally:

"I'm building a task management app for developers. Help me find a brand name with an available domain."

Claude will automatically check domains as it brainstorms.

What You Get

4 Tools — automatically used by Claude during conversations

ToolWhat it does
check_domainsCheck exact domain names — "Is mybrand.com taken?"
check_brand_domainsCheck one name across 17+ TLDs at once — "Check nexflow across all popular TLDs"
suggest_and_check_domainsGenerate name variations from keywords & check all — "Brainstorm names from keywords: pulse, data, flow"
list_supported_tldsShow all TLDs this server supports

30+ TLDs — including trending ones

CategoryTLDs
Classic.com .net .org
Tech / Startup.io .dev .app .co .tech .sh
Trending.ai .gg .so .me .xyz .cc .to .run .cloud .tv
Creative.lol .wtf .cool .world .studio .design
Commerce.online .site .store
Country.kr

Examples

Check a specific name

You: Check if "nexflow" is available — try .com, .io, .ai, and .dev
AVAILABLE:  + nexflow.dev  + nexflow.ai
TAKEN:  - nexflow.com  - nexflow.io
--- 2 available / 2 taken / 0 unknown ---

Brainstorm from keywords

You: I need a name for an AI code review tool.     Keywords: code, review, pulse, scan.     Find me names with available domains.
Generated 20 name variations from: code, review, pulse, scanChecking .com .io .ai .dev .app .co for each
+ codepulse (compound) — available: .dev, .ai | taken: .com, .io+ scanflow (suffix) — available: .ai, .dev, .app | taken: .com+ getpulse (prefix) — available: .dev, .co | taken: .com, .io, .ai+ revscan (blend) — available: .com, .io, .ai, .dev, .app, .co- codelab (suffix) — all checked TLDs taken
TOP PICKS (have available domains):  revscan → revscan.com, revscan.io, revscan.ai, revscan.dev, revscan.app, revscan.co  codepulse → codepulse.dev, codepulse.ai  scanflow → scanflow.ai, scanflow.dev, scanflow.app

Guided workflow with the brand-naming prompt

The server includes a built-in prompt template that walks you through the full naming process step by step.

How It Works

Your question    │    ▼  Claude brainstorms names    │    ▼  mcp-domain-radar    ├── 1. DNS lookup (fast — if it resolves, it's taken)    └── 2. WHOIS query (definitive — checks registration status)    │    ▼  Only names with available domains are recommended
  • No API keys required — uses native DNS and WHOIS protocols
  • Rate-limit friendly — batches queries with delays
  • Works offline for DNS checks — WHOIS requires network

Development

bash
git clone https://github.com/sonwr/mcp-domain-radar.gitcd mcp-domain-radarnpm installnpm run build

Test locally:

bash
claude mcp add domain-radar -- node ./dist/index.js

Roadmap

  • Domain price estimation per registrar
  • Expiring / recently dropped domain suggestions
  • Registrar API integration (Namecheap, Cloudflare, GoDaddy)
  • Internationalized domain name (IDN) support
  • More TLDs and WHOIS servers

Contributions welcome! Open an issue or PR.

License

MIT

Source: README.md at commit 3e6d99b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts