mcp-registry/io.github.lazymac2x/email-validator/check_domain / alternatives

Live alternatives to mcp-registry/io.github.lazymac2x/email-validator/check_domain

The best live alternatives to mcp-registry/io.github.lazymac2x/email-validator/check_domain right now are mcp-registry/email.verifly/verifly/check_domain_health, mcp-registry/com.robtex/mcp/domain_reputation, mcp-registry/io.github.getgapup/mcp-knowledge/email_domain_health_check, mcp-registry/io.github.getgapup/gapup-mcp/email_domain_health_check, mcp-registry/com.datanexusmcp/mcp-server/domain_check_email_security — capability-matched and ranked by current reliability. mcp-registry/io.github.lazymac2x/email-validator/check_domain itself is currently "healthy".

alternative	server
mcp-registry/email.verifly/verifly/check_domain_health	email.verifly/verifly	live status →
mcp-registry/com.robtex/mcp/domain_reputation	com.robtex/mcp	live status →
mcp-registry/io.github.getgapup/mcp-knowledge/email_domain_health_check	io.github.getgapup/mcp-knowledge	live status →
mcp-registry/io.github.getgapup/gapup-mcp/email_domain_health_check	io.github.getgapup/gapup-mcp	live status →
mcp-registry/com.datanexusmcp/mcp-server/domain_check_email_security	com.datanexusmcp/mcp-server	live status →
mcp-registry/com.robtex/mcp/lookup_dns	com.robtex/mcp	live status →
mcp-registry/dev.primitive/email/verifyDomain	dev.primitive/email	live status →
mcp-registry/io.github.emailens/mcp/check_deliverability	io.github.emailens/mcp	live status →
mcp-registry/com.defaultprivacy/default-privacy/check_email_security	com.defaultprivacy/default-privacy	live status →
mcp-registry/io.inboxguard/email-deliverability/scan_domain	io.inboxguard/email-deliverability	live status →
mcp-registry/io.inboxguard/email-deliverability/get_domain	io.inboxguard/email-deliverability	live status →
mcp-registry/io.github.pipeworx-io/disify/check_domain	io.github.pipeworx-io/disify	live status →

FAQ

What is the best alternative to mcp-registry/io.github.lazymac2x/email-validator/check_domain?

mcp-registry/email.verifly/verifly/check_domain_health is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.robtex/mcp/domain_reputation, mcp-registry/io.github.getgapup/mcp-knowledge/email_domain_health_check, mcp-registry/io.github.getgapup/gapup-mcp/email_domain_health_check, mcp-registry/com.datanexusmcp/mcp-server/domain_check_email_security. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.lazymac2x/email-validator/check_domain down right now?

mcp-registry/io.github.lazymac2x/email-validator/check_domain's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.lazymac2x%2Femail-validator%2Fcheck_domain.

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.lazymac2x%2Femail-validator%2Fcheck_domain or MCP find_alternatives. Check mcp-registry/io.github.lazymac2x/email-validator/check_domain's live status: https://glimind.com/tool/mcp-registry/io.github.lazymac2x/email-validator/check_domain.