whoismd-mcp-server
Related Servers
Alternatives to whoismd-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server for domain intelligence — WHOIS, DNS records, SSL certificate inspection, SPF/DMARC validation, security-header audits, and blacklist/reputation checks, callable by AI agents. Powered by domainintel.app; runs server-side, no local setup.758 npmMIT

DNS Doctorofficial
AlicenseAqualityBmaintenanceChecks and fixes a domain's email authentication (SPF, DKIM, DMARC), DNS health, propagation, blacklists and domain/SSL expiry, returning copy-paste fix records from a validating engine, never a model guess. Local stdio server (npx -y @dnsdoctor/mcp) with the same 27 tools as the hosted https://dnsdoctor.dev/mcp.29411 npm2Apache 2.0- AlicenseAqualityDmaintenanceMCP server for DNS lookups, reverse DNS, WHOIS, and domain checks. Zero auth, zero config.564 npm3MIT
- AlicenseNot gradedqualityDmaintenanceEnables domain intelligence lookups including RDAP registration data, DNS records, and Certificate Transparency searches.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to look up domains, URLs, IPs/ASNs, email addresses, phone numbers, crypto wallets, and business records; run autonomous investigations; collect crawl artifacts; and perform evidence-backed scam checks with traceable provenance.MIT
- AlicenseAqualityDmaintenanceMCP server providing DNS resolution, reverse DNS, RDAP-based WHOIS, and IP geolocation lookups. No API keys required , and all upstreams are public.4MIT
TDQS
Scored across 2 tools
The two tools are clearly distinct: one handles a single domain lookup, the other handles batch processing of many domains. There is no ambiguity in their purposes.
Both tools follow a consistent verb_noun pattern using snake_case with the same whoismd_ prefix: whoismd_lookup and whoismd_bulk. The naming is predictable and uniform.
With only two tools, the server is quite thin for a domain intelligence service. While each tool is useful, the absence of operations like historical data, reverse WHOIS, or alerting makes the count feel borderline minimal.
The server covers basic single and bulk lookups, but lacks other common domain intelligence operations such as historical WHOIS, reverse IP lookups, or real-time monitoring. These gaps may limit its usefulness for advanced workflows.