Connects to Claude via stdio and exposes four domain availability tools: check_domains for exact lookups, check_brand_domains to test one name across 17+ TLDs at once, suggest_and_check_domains to generate variations from keywords and batch-check them, and list_supported_tlds. Uses DNS lookups plus WHOIS queries under the hood, no API keys needed. Supports 30+ TLDs including .com, .io, .ai, .dev, and trending options like .gg and .so. Ships with an optional brand-naming skill for Claude Code that guides you through the full naming workflow. Reach for this when you're brainstorming product names and want to filter out taken domains in real time instead of tab-switching to a registrar every 30 seconds.
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.
We've all been there:
You: "Suggest a name for my service"
AI: "How about NexFlow?"
You: Search nexflow.com... already taken
You: "Another one"
AI: "DataPulse?"
You: Search datapulse.com... also taken
You: "..."
(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.
1. Install
npm install -g mcp-domain-radar
2. Connect to your AI coding tool
claude mcp add domain-radar -- mcp-domain-radar
codex mcp add domain-radar -- npx mcp-domain-radar
Add to .cursor/mcp.json:
{
"mcpServers": {
"domain-radar": {
"command": "npx",
"args": ["mcp-domain-radar"]
}
}
}
Add to claude_desktop_config.json:
{
"mcpServers": {
"domain-radar": {
"command": "npx",
"args": ["mcp-domain-radar"]
}
}
}
3. Install the brand-naming skill (optional, Claude Code only)
mkdir -p ~/.claude/skills/brand-naming
cp 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.
| Tool | What it does |
|---|---|
check_domains | Check exact domain names — "Is mybrand.com taken?" |
check_brand_domains | Check one name across 17+ TLDs at once — "Check nexflow across all popular TLDs" |
suggest_and_check_domains | Generate name variations from keywords & check all — "Brainstorm names from keywords: pulse, data, flow" |
list_supported_tlds | Show all TLDs this server supports |
| Category | TLDs |
|---|---|
| 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 |
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 ---
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, scan
Checking .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
brand-naming promptThe server includes a built-in prompt template that walks you through the full naming process step by step.
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
git clone https://github.com/sonwr/mcp-domain-radar.git
cd mcp-domain-radar
npm install
npm run build
Test locally:
claude mcp add domain-radar -- node ./dist/index.js
Contributions welcome! Open an issue or PR.
MIT