mcp-registry/com.datanexusmcp/mcp-server/domain_fetch_dns_records / alternatives
mcp-registry/com.datanexusmcp/mcp-server/domain_fetch_dns_recordsThe best live alternatives to mcp-registry/com.datanexusmcp/mcp-server/domain_fetch_dns_records right now are mcp-registry/io.github.xogz3/botoi-mcp/lookup_dns, mcp-registry/io.github.vee3io/vee3/domains.dns_records, mcp-registry/io.github.br0ski777/dns-lookup/network_lookup_dns, mcp-registry/io.github.abtdomain/domainkits-mcp/dns, mcp-registry/ai.intuitek.the-stall/the-stall/dns-lookup — capability-matched and ranked by current reliability. mcp-registry/com.datanexusmcp/mcp-server/domain_fetch_dns_records itself is currently "healthy".
mcp-registry/io.github.xogz3/botoi-mcp/lookup_dns is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.vee3io/vee3/domains.dns_records, mcp-registry/io.github.br0ski777/dns-lookup/network_lookup_dns, mcp-registry/io.github.abtdomain/domainkits-mcp/dns, mcp-registry/ai.intuitek.the-stall/the-stall/dns-lookup. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/com.datanexusmcp/mcp-server/domain_fetch_dns_records's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.datanexusmcp%2Fmcp-server%2Fdomain_fetch_dns_records.
By semantic capability match (what the tool does) filtered to tools that are healthy right now — from cross-ecosystem real usage. Neutral: Glimind sells no tools.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcom.datanexusmcp%2Fmcp-server%2Fdomain_fetch_dns_records
or MCP find_alternatives. Check mcp-registry/com.datanexusmcp/mcp-server/domain_fetch_dns_records's live status: https://glimind.com/tool/mcp-registry/com.datanexusmcp/mcp-server/domain_fetch_dns_records.