domain-mcp
Related Servers
Alternatives to domain-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server for checking domain name availability via RDAP and WHOIS fallback, supporting single and bulk domain lookups.5MIT
- AlicenseNot gradedqualityFmaintenanceA simple MCP server that enables AI assistants to perform domain research including availability checking, WHOIS lookups, DNS record retrieval, and finding expired domains without requiring API keys.62MIT
- FlicenseNot gradedqualityNot gradedmaintenanceAn MCP server for domain availability checks, WHOIS lookups, and domain suggestions using RDAP and TCP port 43. It allows users to perform bulk checks and retrieve registration details across multiple TLDs without requiring an API key.41 npm-
- AlicenseNot gradedqualityDmaintenanceAn MCP server for domain management, enabling domain availability checks, bulk domain checks, and API connectivity testing through the RealtimeRegister API.5 npm1MIT
- AlicenseAqualityDmaintenanceMCP server for DNS lookups, reverse DNS, WHOIS, and domain checks. Zero auth, zero config.532 npm3MIT
- AlicenseAqualityDmaintenanceMCP server for checking domain name availability across 500+ TLDs using RDAP with WHOIS fallback for specific TLDs.2MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: domain search suggestions, single availability check, bulk availability check, and WHOIS lookup. Even though check_domain and whois_lookup both return registration details, one focuses on availability and RDAP while the other provides full WHOIS data, avoiding confusion.
All tool names follow a consistent verb_noun pattern with snake_case: search_domains, check_domain, check_multiple_domains, whois_lookup. The naming is predictable and uniform.
With 4 tools, the server is well-scoped for domain search and lookup operations. Each tool serves a core function without redundancy, fitting the typical 3-15 tool range.
The tool set covers search, single and bulk availability checks, and detailed WHOIS data—covering the main domain lookup needs. A minor gap is the absence of DNS record lookup, but for a domain availability and WHOIS server, this is acceptable.