mcp-registry/io.github.shree-git/sendit/get_inbox_summary / alternatives

Live alternatives to mcp-registry/io.github.shree-git/sendit/get_inbox_summary

The best live alternatives to mcp-registry/io.github.shree-git/sendit/get_inbox_summary right now are mcp-registry/com.myagentinbox/myagentinbox/check_inbox, mcp-registry/io.github.peterjduffy/parsley-mcp/get_analytics_summary, mcp-registry/now.shiply/shiply/list_inbox, mcp-registry/io.github.dynamitecircle/dc/inbox_unread, mcp-registry/io.favcrm/favcrm/get_survey_stats — capability-matched and ranked by current reliability. mcp-registry/io.github.shree-git/sendit/get_inbox_summary itself is currently "healthy".

alternative	server
mcp-registry/com.myagentinbox/myagentinbox/check_inbox	com.myagentinbox/myagentinbox	live status →
mcp-registry/io.github.peterjduffy/parsley-mcp/get_analytics_summary	io.github.peterjduffy/parsley-mcp	live status →
mcp-registry/now.shiply/shiply/list_inbox	now.shiply/shiply	live status →
mcp-registry/io.github.dynamitecircle/dc/inbox_unread	io.github.dynamitecircle/dc	live status →
mcp-registry/io.favcrm/favcrm/get_survey_stats	io.favcrm/favcrm	live status →
mcp-registry/dev.primitive/email/getInboxStatus	dev.primitive/email	live status →
mcp-registry/com.zobrx/zobrx/get_dashboard_summary	com.zobrx/zobrx	live status →
mcp-registry/com.po6/mailbox/get_mailbox_stats	com.po6/mailbox	live status →
mcp-registry/com.kaicalls/kaicalls/get_analytics	com.kaicalls/kaicalls	live status →
mcp-registry/io.github.toshihiroshishido/revenuescope-mcp/get_summary	io.github.toshihiroshishido/revenuescope-mcp	live status →
mcp-registry/io.favcrm/favcrm/get_dashboard_stats	io.favcrm/favcrm	live status →
mcp-registry/io.favcrm/favcrm/list_conversations	io.favcrm/favcrm	live status →

FAQ

What is the best alternative to mcp-registry/io.github.shree-git/sendit/get_inbox_summary?

mcp-registry/com.myagentinbox/myagentinbox/check_inbox is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.peterjduffy/parsley-mcp/get_analytics_summary, mcp-registry/now.shiply/shiply/list_inbox, mcp-registry/io.github.dynamitecircle/dc/inbox_unread, mcp-registry/io.favcrm/favcrm/get_survey_stats. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.shree-git/sendit/get_inbox_summary down right now?

mcp-registry/io.github.shree-git/sendit/get_inbox_summary's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.shree-git%2Fsendit%2Fget_inbox_summary.

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%2Fio.github.shree-git%2Fsendit%2Fget_inbox_summary or MCP find_alternatives. Check mcp-registry/io.github.shree-git/sendit/get_inbox_summary's live status: https://glimind.com/tool/mcp-registry/io.github.shree-git/sendit/get_inbox_summary.