mcp-registry/bot.mailbox/mailbox/register_expected / alternatives

Live alternatives to mcp-registry/bot.mailbox/mailbox/register_expected

The best live alternatives to mcp-registry/bot.mailbox/mailbox/register_expected right now are mcp-registry/io.github.baneado98/freight-pulse/appointment_plan, mcp-registry/com.wearmu/mu/mu_ship_mark, mcp-registry/io.github.trycourier/courier/track_inbound_event, mcp-registry/dev.agent-module/mcp/register_interest, mcp-registry/io.github.lxxmng/container-loading/export_plan — capability-matched and ranked by current reliability. mcp-registry/bot.mailbox/mailbox/register_expected itself is currently "healthy".

alternative	server
mcp-registry/io.github.baneado98/freight-pulse/appointment_plan	io.github.Baneado98/freight-pulse	live status →
mcp-registry/com.wearmu/mu/mu_ship_mark	com.wearmu/mu	live status →
mcp-registry/io.github.trycourier/courier/track_inbound_event	io.github.trycourier/courier	live status →
mcp-registry/dev.agent-module/mcp/register_interest	dev.agent-module/mcp	live status →
mcp-registry/io.github.lxxmng/container-loading/export_plan	io.github.lxxmng/container-loading	live status →
mcp-registry/io.github.packrift/packrift-mcp/prepare_purchase_handoff	io.github.Packrift/packrift-mcp	live status →
mcp-registry/io.github.basilalshukaili/agent-broker/handle_inbound	io.github.basilalshukaili/agent-broker	live status →
mcp-registry/com.aftership.mcp/tracking-public/track_shipment	com.aftership.mcp/tracking-public	live status →
pulsemcp/aftership-tracking/track_shipment	AfterShip Tracking	live status →
mcp-registry/io.github.agentlux/agentlux/agentlux_service_accept_hire	io.github.agentlux/agentlux	live status →
mcp-registry/io.github.baneado98/freight-pulse/required_documents	io.github.Baneado98/freight-pulse	live status →
mcp-registry/com.zobrx/zobrx/list_picklists	com.zobrx/zobrx	live status →

FAQ

What is the best alternative to mcp-registry/bot.mailbox/mailbox/register_expected?

mcp-registry/io.github.baneado98/freight-pulse/appointment_plan is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.wearmu/mu/mu_ship_mark, mcp-registry/io.github.trycourier/courier/track_inbound_event, mcp-registry/dev.agent-module/mcp/register_interest, mcp-registry/io.github.lxxmng/container-loading/export_plan. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/bot.mailbox/mailbox/register_expected down right now?

mcp-registry/bot.mailbox/mailbox/register_expected's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fbot.mailbox%2Fmailbox%2Fregister_expected.

How does Glimind pick alternatives?

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.

For agents

Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fbot.mailbox%2Fmailbox%2Fregister_expected or MCP find_alternatives. Check mcp-registry/bot.mailbox/mailbox/register_expected's live status: https://glimind.com/tool/mcp-registry/bot.mailbox/mailbox/register_expected.