mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname / alternatives

Live alternatives to mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname

The best live alternatives to mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname right now are mcp-registry/com.themailx/email-deliverability/cname_lookup, mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns, mcp-registry/io.github.pipeworx-io/hackertarget/dns_host_search, mcp-registry/io.github.pipeworx-io/hackertarget/dns_lookup, mcp-registry/ai.dynamicfeed/dynamic-feed/dns_lookup — capability-matched and ranked by current reliability. mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname itself is currently "healthy".

alternative	server
mcp-registry/com.themailx/email-deliverability/cname_lookup	com.themailx/email-deliverability	live status →
mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns	io.github.pipeworx-io/hackertarget	live status →
mcp-registry/io.github.pipeworx-io/hackertarget/dns_host_search	io.github.pipeworx-io/hackertarget	live status →
mcp-registry/io.github.pipeworx-io/hackertarget/dns_lookup	io.github.pipeworx-io/hackertarget	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/dns_lookup	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.abtdomain/domainkits-mcp/ns_reverse	io.github.ABTdomain/domainkits-mcp	live status →
mcp-registry/io.github.pipeworx-io/hackertarget/reverse_ip	io.github.pipeworx-io/hackertarget	live status →
mcp-registry/io.github.pipeworx-io/dns/reverse_dns	io.github.pipeworx-io/dns	live status →
mcp-registry/com.sprytools/sprytools/dns_lookup	com.sprytools/sprytools	live status →
mcp-registry/io.github.pipeworx-io/hackertarget/find_shared_dns	io.github.pipeworx-io/hackertarget	live status →
mcp-registry/io.github.xogz3/botoi-mcp/lookup_dns_monitor	io.github.XogZ3/botoi-mcp	live status →
mcp-registry/io.github.pipeworx-io/dns/dns_lookup	io.github.pipeworx-io/dns	live status →

FAQ

What is the best alternative to mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname?

mcp-registry/com.themailx/email-deliverability/cname_lookup is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns, mcp-registry/io.github.pipeworx-io/hackertarget/dns_host_search, mcp-registry/io.github.pipeworx-io/hackertarget/dns_lookup, mcp-registry/ai.dynamicfeed/dynamic-feed/dns_lookup. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname down right now?

mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.robtex%2Fmcp%2Fhistoric_reverse_lookup_cname.

How does Glimind pick alternatives?

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.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fcom.robtex%2Fmcp%2Fhistoric_reverse_lookup_cname or MCP find_alternatives. Check mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname's live status: https://glimind.com/tool/mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname.