domain-search-mcp — Claude Code MCP server: setup and usage
Checks domain availability and social handles directly from your model session. It ranks project names and flags registered addresses without browser lookups.
claude mcp add --env PRICING_API_BASE_URL=<PRICING_API_BASE_URL> --env PRICING_API_TOKEN=<PRICING_API_TOKEN> --env PORKBUN_API_KEY=<PORKBUN_API_KEY> --env PORKBUN_API_SECRET=<PORKBUN_API_SECRET> --env NAMECHEAP_API_KEY=<NAMECHEAP_API_KEY> --transport stdio domain-search-mcp -- npx -y domain-search-mcpWhat domain-search-mcp does
The server evaluates generated names and inspects over 500 TLDs. Availability lookups run through an RDAP chain with fallback to GoDaddy and WHOIS. This sequence exposes auction signals and premium listings early. GoDaddy requests are safeguarded by a circuit breaker with a rate limit of 30 calls each minute.
The name_project tool provides a two-phase workflow. First, it returns generation rules for your model. Next, it accepts candidate names to filter and verify live availability. Domain suggestions run on the Qwen 7B-DPO model. By default, 12 tools are active, though SLIM_TOOLS=true narrows the exposed list down to 6 core functions.
Basic availability lookups require no API keys. Getting live checkout prices from Porkbun or Namecheap requires direct credentials or a dedicated backend URL. For local setups, stdio works right away, while the --http flag starts a server on port 3000 for ChatGPT actions or web clients.
What it helps with
- search domain availability across 500+ TLDs
- batch check up to 100 domain names simultaneously
- spot premium and aftermarket auction domains via GoDaddy
- compare registrar pricing across Porkbun and Namecheap
Example prompts for the agent
- Check if vibecoding is available on .com, .io, and .ai.
- Run name_project to brainstorm and score brand names for a developer tool.
- Perform a bulk search for 20 project names under the .dev zone.
How to install domain-search-mcp
Platform CLI
claude mcp add --env PRICING_API_BASE_URL=<PRICING_API_BASE_URL> --env PRICING_API_TOKEN=<PRICING_API_TOKEN> --env PORKBUN_API_KEY=<PORKBUN_API_KEY> --env PORKBUN_API_SECRET=<PORKBUN_API_SECRET> --env NAMECHEAP_API_KEY=<NAMECHEAP_API_KEY> --transport stdio domain-search-mcp -- npx -y domain-search-mcpReplace <…> with your own values. 1 more environment variable is in the server README
Platform CLI
codex mcp add domain-search-mcp --env PRICING_API_BASE_URL=<PRICING_API_BASE_URL> --env PRICING_API_TOKEN=<PRICING_API_TOKEN> --env PORKBUN_API_KEY=<PORKBUN_API_KEY> --env PORKBUN_API_SECRET=<PORKBUN_API_SECRET> --env NAMECHEAP_API_KEY=<NAMECHEAP_API_KEY> -- npx -y domain-search-mcpReplace <…> with your own values. 1 more environment variable is in the server README
Config file
{
"mcpServers": {
"domain-search-mcp": {
"command": "npx",
"args": [
"-y",
"domain-search-mcp"
],
"env": {
"PRICING_API_BASE_URL": "<PRICING_API_BASE_URL>",
"PRICING_API_TOKEN": "<PRICING_API_TOKEN>",
"PORKBUN_API_KEY": "<PORKBUN_API_KEY>",
"PORKBUN_API_SECRET": "<PORKBUN_API_SECRET>",
"NAMECHEAP_API_KEY": "<NAMECHEAP_API_KEY>"
}
}
}
}Replace <…> with your own values. 1 more environment variable is in the server README
Config file
{
"servers": {
"domain-search-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"domain-search-mcp"
],
"env": {
"PRICING_API_BASE_URL": "<PRICING_API_BASE_URL>",
"PRICING_API_TOKEN": "<PRICING_API_TOKEN>",
"PORKBUN_API_KEY": "<PORKBUN_API_KEY>",
"PORKBUN_API_SECRET": "<PORKBUN_API_SECRET>",
"NAMECHEAP_API_KEY": "<NAMECHEAP_API_KEY>"
}
}
}
}Replace <…> with your own values. 1 more environment variable is in the server README
Platform CLI
gemini mcp add -e PRICING_API_BASE_URL=<PRICING_API_BASE_URL> -e PRICING_API_TOKEN=<PRICING_API_TOKEN> -e PORKBUN_API_KEY=<PORKBUN_API_KEY> -e PORKBUN_API_SECRET=<PORKBUN_API_SECRET> -e NAMECHEAP_API_KEY=<NAMECHEAP_API_KEY> domain-search-mcp npx -y domain-search-mcpReplace <…> with your own values. 1 more environment variable is in the server README
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about domain-search-mcp
How do I install domain-search-mcp in Claude Code?
Run the following command: `claude mcp add --env PRICING_API_BASE_URL=<PRICING_API_BASE_URL> --env PRICING_API_TOKEN=<PRICING_API_TOKEN> --env PORKBUN_API_KEY=<PORKBUN_API_KEY> --env PORKBUN_API_SECRET=<PORKBUN_API_SECRET> --env NAMECHEAP_API_KEY=<NAMECHEAP_API_KEY> --transport stdio domain-search-mcp -- npx -y domain-search-mcp`. If you only need availability checks without pricing, omit the environment variables.
Are API keys required for checking domain availability?
No. Public RDAP and WHOIS lookups operate out of the box with zero configuration. You only need keys when fetching pricing from Porkbun or Namecheap.
What changes when setting SLIM_TOOLS=true?
The environment variable limits the tool surface from 12 tools to 6 core functions. It keeps name_project, search_domain, bulk_search, check_socials, tld_info, and ai_health.