mcp-registry/co.truncus/mcp-server/truncus_get_email / alternatives
mcp-registry/co.truncus/mcp-server/truncus_get_emailThe best live alternatives to mcp-registry/co.truncus/mcp-server/truncus_get_email right now are mcp-registry/io.github.xbt786/hipaa-agent/get_outreach_status, mcp-registry/now.shiply/shiply/get_test_status, mcp-registry/com.adbutler/mcp-server/get_email_zone, mcp-registry/io.github.pipeworx-io/activecampaign/get_contact, mcp-registry/io.github.pipeworx-io/hunter/email_verifier — capability-matched and ranked by current reliability. mcp-registry/co.truncus/mcp-server/truncus_get_email itself is currently "unknown".
mcp-registry/io.github.xbt786/hipaa-agent/get_outreach_status is the top capability-matched alternative that's live right now. Other options: mcp-registry/now.shiply/shiply/get_test_status, mcp-registry/com.adbutler/mcp-server/get_email_zone, mcp-registry/io.github.pipeworx-io/activecampaign/get_contact, mcp-registry/io.github.pipeworx-io/hunter/email_verifier. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/co.truncus/mcp-server/truncus_get_email's current verdict is "unknown". See its live status and score at https://glimind.com/tool/mcp-registry%2Fco.truncus%2Fmcp-server%2Ftruncus_get_email.
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%2Fco.truncus%2Fmcp-server%2Ftruncus_get_email
or MCP find_alternatives. Check mcp-registry/co.truncus/mcp-server/truncus_get_email's live status: https://glimind.com/tool/mcp-registry/co.truncus/mcp-server/truncus_get_email.