mcp-registry/io.github.deesmo/arch-tools-mcp/email-verify / alternatives
mcp-registry/io.github.deesmo/arch-tools-mcp/email-verifyThe best live alternatives to mcp-registry/io.github.deesmo/arch-tools-mcp/email-verify right now are mcp-registry/io.github.xogz3/botoi-mcp/lookup_email, mcp-registry/com.sprytools/sprytools/validate_email, mcp-registry/com.contrastcyber/api/email_verify, mcp-registry/io.github.lazymac2x/email-validator/validate_email, mcp-registry/ai.intuitek.the-stall/the-stall/email-verify — capability-matched and ranked by current reliability. mcp-registry/io.github.deesmo/arch-tools-mcp/email-verify itself is currently "healthy".
mcp-registry/io.github.xogz3/botoi-mcp/lookup_email is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.sprytools/sprytools/validate_email, mcp-registry/com.contrastcyber/api/email_verify, mcp-registry/io.github.lazymac2x/email-validator/validate_email, mcp-registry/ai.intuitek.the-stall/the-stall/email-verify. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.deesmo/arch-tools-mcp/email-verify's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.deesmo%2Farch-tools-mcp%2Femail-verify.
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%2Fio.github.deesmo%2Farch-tools-mcp%2Femail-verify
or MCP find_alternatives. Check mcp-registry/io.github.deesmo/arch-tools-mcp/email-verify's live status: https://glimind.com/tool/mcp-registry/io.github.deesmo/arch-tools-mcp/email-verify.