mcp-registry/io.github.trycourier/courier/get_message_history / alternatives

Live alternatives to mcp-registry/io.github.trycourier/courier/get_message_history

The best live alternatives to mcp-registry/io.github.trycourier/courier/get_message_history right now are mcp-registry/io.github.saloprj/dialogbrain/messages_read_history, mcp-registry/io.favcrm/favcrm/get_conversation_messages, mcp-registry/io.famulor/famulor-mcp/get_conversation, mcp-registry/tools.growthkit/revenue-intelligence/getHistory, mcp-registry/app.himalayas/mcp/get_conversation — capability-matched and ranked by current reliability. mcp-registry/io.github.trycourier/courier/get_message_history itself is currently "healthy".

alternative	server
mcp-registry/io.github.saloprj/dialogbrain/messages_read_history	io.github.saloprj/dialogbrain	live status →
mcp-registry/io.favcrm/favcrm/get_conversation_messages	io.favcrm/favcrm	live status →
mcp-registry/io.famulor/famulor-mcp/get_conversation	io.famulor/famulor-mcp	live status →
mcp-registry/tools.growthkit/revenue-intelligence/getHistory	tools.growthkit/revenue-intelligence	live status →
mcp-registry/app.himalayas/mcp/get_conversation	app.himalayas/mcp	live status →
pulsemcp/100hires/hires_get_message	100Hires	live status →
mcp-registry/io.github.itsmalware/the-lounge/get_lounge_history	io.github.ItsMalware/the-lounge	live status →
mcp-registry/io.github.shree-git/sendit/get_conversation	io.github.Shree-git/sendit	live status →
mcp-registry/io.github.pipeworx-io/intercom/ic_get_conversation	io.github.pipeworx-io/intercom	live status →
mcp-registry/bot.mailbox/mailbox/get_facility_messages	bot.mailbox/mailbox	live status →
mcp-registry/com.b2bware/mcp-server/get_event_delivery_log	com.b2bware/mcp-server	live status →
pulsemcp/100hires/hires_list_messages	100Hires	live status →

FAQ

What is the best alternative to mcp-registry/io.github.trycourier/courier/get_message_history?

mcp-registry/io.github.saloprj/dialogbrain/messages_read_history is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.favcrm/favcrm/get_conversation_messages, mcp-registry/io.famulor/famulor-mcp/get_conversation, mcp-registry/tools.growthkit/revenue-intelligence/getHistory, mcp-registry/app.himalayas/mcp/get_conversation. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.trycourier/courier/get_message_history down right now?

mcp-registry/io.github.trycourier/courier/get_message_history's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.trycourier%2Fcourier%2Fget_message_history.

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.trycourier%2Fcourier%2Fget_message_history or MCP find_alternatives. Check mcp-registry/io.github.trycourier/courier/get_message_history's live status: https://glimind.com/tool/mcp-registry/io.github.trycourier/courier/get_message_history.