mcp-registry/io.github.br0ski777/email-finder/email_find_by_name / alternatives
mcp-registry/io.github.br0ski777/email-finder/email_find_by_nameThe best live alternatives to mcp-registry/io.github.br0ski777/email-finder/email_find_by_name right now are mcp-registry/io.github.pipeworx-io/hunter/email_finder, mcp-registry/io.github.pipeworx-io/hunter/domain_search, mcp-registry/io.tooloracle/leadoracle/email_finder, mcp-registry/tools.growthkit/revenue-intelligence/findEmail, mcp-registry/io.github.deesmo/arch-tools-mcp/email-find — capability-matched and ranked by current reliability. mcp-registry/io.github.br0ski777/email-finder/email_find_by_name itself is currently "healthy".
mcp-registry/io.github.pipeworx-io/hunter/email_finder is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/hunter/domain_search, mcp-registry/io.tooloracle/leadoracle/email_finder, mcp-registry/tools.growthkit/revenue-intelligence/findEmail, mcp-registry/io.github.deesmo/arch-tools-mcp/email-find. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.br0ski777/email-finder/email_find_by_name's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.br0ski777%2Femail-finder%2Femail_find_by_name.
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.br0ski777%2Femail-finder%2Femail_find_by_name
or MCP find_alternatives. Check mcp-registry/io.github.br0ski777/email-finder/email_find_by_name's live status: https://glimind.com/tool/mcp-registry/io.github.br0ski777/email-finder/email_find_by_name.