domain-search

Domain Search MCP provides rapid, local-first domain availability checks for MCP clients. It can verify domain availability across multiple TLDs, perform bulk checks, and enrich results with premium/auction signals via a backend you control. It also offers AI-powered domain suggestions, social handle checks, and optional pricing integration. Clients can connect via standard input/output (stdio) for Claude Desktop, Cursor, and VS Code, or use the HTTP/SSE interface for web apps and REST clients. The HTTP interface exposes endpoints for the MCP protocol, per-tool REST APIs, an OpenAPI spec, health metrics, and Prometheus-style metrics, making it suitable for embedding into automation or ChatGPT Actions workflows. Core functionality includes search_domain for multi-TLD checks, bulk_search for up to 100 names, and compare_registrars for pricing when a pricing backend is configured. AI features like suggest_domains and suggest_domains_smart generate brandable names with zero-config operation, while analyze_project can scan a local project or GitHub repo to suggest matching domain names.

Prerequisites:

• Node.js and npm installed on your system
• Git (optional, for cloning the repository)

Installation steps:

1. Install via npx (no local install required):

   • npx -y domain-search-mcp@latest

2. From source (optional, if you want to run from a local clone):

   • git clone https://github.com/dorukardahan/domain-search-mcp.git
   • cd domain-search-mcp
   • npm install
   • npm run build
   • npm start

3. If you plan to run via MCP client configs:

   • Ensure your mcp.json or equivalent client config points to the npx invocation as shown in the mcp_config section.

Notes:

• The server supports both stdio and HTTP/SSE transport modes. Use --http to enable the HTTP server (port defaults to 3000, can be overridden with MCP_PORT).

Tips and common considerations:

• Pricing backend: If you want registrar pricing, set PRICING_API_BASE_URL to your backend URL (which should expose /api/quote and /api/compare). Optionally set PRICING_API_TOKEN for authentication.
• BYOK: If pricing backend is not configured, you may provide local API keys for Porkbun/Namecheap (PORKBUN_API_KEY, PORKBUN_API_SECRET, NAMECHEAP_API_KEY, NAMECHEAP_API_USER, NAMECHEAP_CLIENT_IP).
• Redis cache: For horizontal scaling and distributed caching, configure REDIS_URL; otherwise, in-memory caching is used.
• Transport: By default, clients use stdio. For web clients or ChatGPT Actions, use the HTTP/SSE interface and the /openapi.json and /api/tools/* endpoints.
• Upgrading: Use the @latest tag when starting via npx to ensure you have the newest features and bug fixes.
• If you encounter rate limiting on GoDaddy or external services, consider configuring a backend pricing service and implementing circuit breakers as described in the documentation.