mcp-registry/bot.mailbox/mailbox/list_inbound_forwarding_addresses / alternatives
mcp-registry/bot.mailbox/mailbox/list_inbound_forwarding_addressesThe best live alternatives to mcp-registry/bot.mailbox/mailbox/list_inbound_forwarding_addresses right now are mcp-registry/now.shiply/shiply/list_test_inbox_addresses, mcp-registry/com.po6/mailbox/get_alias, mcp-registry/com.po6/mailbox/update_alias, mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_tempmail_list, mcp-registry/com.po6/mailbox/forward_email — capability-matched and ranked by current reliability. mcp-registry/bot.mailbox/mailbox/list_inbound_forwarding_addresses itself is currently "healthy".
mcp-registry/now.shiply/shiply/list_test_inbox_addresses is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.po6/mailbox/get_alias, mcp-registry/com.po6/mailbox/update_alias, mcp-registry/com.mcp-revenue-empire/japan-public-ledgers/agent_tempmail_list, mcp-registry/com.po6/mailbox/forward_email. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/bot.mailbox/mailbox/list_inbound_forwarding_addresses's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fbot.mailbox%2Fmailbox%2Flist_inbound_forwarding_addresses.
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%2Fbot.mailbox%2Fmailbox%2Flist_inbound_forwarding_addresses
or MCP find_alternatives. Check mcp-registry/bot.mailbox/mailbox/list_inbound_forwarding_addresses's live status: https://glimind.com/tool/mcp-registry/bot.mailbox/mailbox/list_inbound_forwarding_addresses.