MCP DNS
Related Servers
Alternatives to MCP DNS
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server that provides comprehensive domain name research tools, including RDAP, WHOIS, and DNS query functionality.12Apache 2.0
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides comprehensive domain analysis capabilities including WHOIS lookups, DNS record queries, and DNS health checking.14MIT
- FlicenseAqualityDmaintenanceProvides DNS lookup and email authentication diagnostic tools (SPF, DKIM, DMARC, MX, etc.) for use with MCP-compatible clients. Enables natural language queries to check DNS records and email health.7-
- AlicenseAqualityCmaintenanceModel Context Protocol (MCP) server for deep DNS resolution, nameserver propagation, and DNSSEC validation17 npmMIT
- AlicenseNot gradedqualityFmaintenanceMCP server that enumerates DNS records, detects SPF/DMARC/DKIM misconfigurations, and identifies dangling subdomains.139 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables DNS record lookups for types like A, MX, TXT, and CNAME, bulk queries of all major record types, and reverse DNS resolution from IP addresses to hostnames.237 npmMIT
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The tool's purpose is clearly defined as making DNS queries, leaving no ambiguity for an agent to misselect among alternatives.
A single tool inherently has perfect naming consistency, as there are no other tools to compare against. The tool name 'dns-query' follows a clear and descriptive pattern, using a hyphen to separate domain and action.
A single tool is generally too few for a DNS server's scope, which typically involves operations like querying, resolving, or managing DNS records. This minimal set feels thin and may limit functionality for agents needing more comprehensive DNS interactions.
The tool surface is severely incomplete for a DNS domain. While 'dns-query' covers basic lookups, there are obvious gaps such as reverse DNS lookups, record management (e.g., adding or deleting records), or handling different DNS server configurations, which could cause agent failures in broader DNS-related tasks.