mcp-registry/io.inboxguard/email-deliverability/get_inbox_placement_status / alternatives
mcp-registry/io.inboxguard/email-deliverability/get_inbox_placement_statusThe best live alternatives to mcp-registry/io.inboxguard/email-deliverability/get_inbox_placement_status right now are mcp-registry/dev.primitive/email/getInboxStatus, mcp-registry/live.alpic.alpichack-3c740d01/alpichack/get-connection-status, mcp-registry/io.github.trycourier/courier/list_providers, mcp-registry/org.memoryapi/intel/check_provider_status, mcp-registry/network.tenzro/tenzro/list_providers — capability-matched and ranked by current reliability. mcp-registry/io.inboxguard/email-deliverability/get_inbox_placement_status itself is currently "healthy".
mcp-registry/dev.primitive/email/getInboxStatus is the top capability-matched alternative that's live right now. Other options: mcp-registry/live.alpic.alpichack-3c740d01/alpichack/get-connection-status, mcp-registry/io.github.trycourier/courier/list_providers, mcp-registry/org.memoryapi/intel/check_provider_status, mcp-registry/network.tenzro/tenzro/list_providers. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.inboxguard/email-deliverability/get_inbox_placement_status's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.inboxguard%2Femail-deliverability%2Fget_inbox_placement_status.
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.inboxguard%2Femail-deliverability%2Fget_inbox_placement_status
or MCP find_alternatives. Check mcp-registry/io.inboxguard/email-deliverability/get_inbox_placement_status's live status: https://glimind.com/tool/mcp-registry/io.inboxguard/email-deliverability/get_inbox_placement_status.