mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns

The best live alternatives to mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns right now are mcp-registry/com.robtex/mcp/reverse_lookup_cname, mcp-registry/com.robtex/mcp/domain_shared_ns, mcp-registry/dev.sipflow/sipflow/dns_diagnose_sip_target, mcp-registry/com.robtex/mcp/lookup_dns, mcp-registry/io.github.davidmosiah/delx-mcp-a2a/util_dns_lookup — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns itself is currently "healthy".

alternative	server
mcp-registry/com.robtex/mcp/reverse_lookup_cname	com.robtex/mcp	live status →
mcp-registry/com.robtex/mcp/domain_shared_ns	com.robtex/mcp	live status →
mcp-registry/dev.sipflow/sipflow/dns_diagnose_sip_target	dev.sipflow/sipflow	live status →
mcp-registry/com.robtex/mcp/lookup_dns	com.robtex/mcp	live status →
mcp-registry/io.github.davidmosiah/delx-mcp-a2a/util_dns_lookup	io.github.davidmosiah/delx-mcp-a2a	live status →
mcp-registry/com.robtex/mcp/historic_reverse_lookup_cname	com.robtex/mcp	live status →
mcp-registry/com.robtex/mcp/domain_shared_ip	com.robtex/mcp	live status →
mcp-registry/io.github.abtdomain/domainkits-mcp/ns_reverse	io.github.ABTdomain/domainkits-mcp	live status →
mcp-registry/com.themailx/email-deliverability/ptr_lookup	com.themailx/email-deliverability	live status →
mcp-registry/com.robtex/mcp/reverse_lookup_dns_records	com.robtex/mcp	live status →
mcp-registry/com.datanexusmcp/mcp-server/domain_fetch_reverse_ip	com.datanexusmcp/mcp-server	live status →
mcp-registry/com.robtex/mcp/historic_reverse_lookup_ns	com.robtex/mcp	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns?

mcp-registry/com.robtex/mcp/reverse_lookup_cname is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.robtex/mcp/domain_shared_ns, mcp-registry/dev.sipflow/sipflow/dns_diagnose_sip_target, mcp-registry/com.robtex/mcp/lookup_dns, mcp-registry/io.github.davidmosiah/delx-mcp-a2a/util_dns_lookup. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns down right now?

mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fhackertarget%2Freverse_dns.

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%2Fio.github.pipeworx-io%2Fhackertarget%2Freverse_dns or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/hackertarget/reverse_dns.