mcp-registry/io.github.saloprj/dialogbrain/messages_read_history / alternatives

Live alternatives to mcp-registry/io.github.saloprj/dialogbrain/messages_read_history

The best live alternatives to mcp-registry/io.github.saloprj/dialogbrain/messages_read_history right now are mcp-registry/io.favcrm/favcrm/get_conversation_messages, mcp-registry/io.github.trycourier/courier/get_message_history, mcp-registry/io.github.agentlinehq/agentline/list_calls, mcp-registry/io.favcrm/favcrm/list_conversations, mcp-registry/io.github.pipeworx-io/intercom/ic_get_conversation — capability-matched and ranked by current reliability. mcp-registry/io.github.saloprj/dialogbrain/messages_read_history itself is currently "healthy".

alternativeserver
mcp-registry/io.favcrm/favcrm/get_conversation_messagesio.favcrm/favcrmlive status →
mcp-registry/io.github.trycourier/courier/get_message_historyio.github.trycourier/courierlive status →
mcp-registry/io.github.agentlinehq/agentline/list_callsio.github.AgentLineHQ/agentlinelive status →
mcp-registry/io.favcrm/favcrm/list_conversationsio.favcrm/favcrmlive status →
mcp-registry/io.github.pipeworx-io/intercom/ic_get_conversationio.github.pipeworx-io/intercomlive status →
mcp-registry/app.himalayas/mcp/get_conversationapp.himalayas/mcplive status →
mcp-registry/cz.salesbot/linkedin-mcp-server/get_chat_messagescz.salesbot/linkedin-mcp-serverlive status →
mcp-registry/io.famulor/famulor-mcp/get_conversationio.famulor/famulor-mcplive status →
mcp-registry/io.github.itsmalware/the-lounge/get_lounge_historyio.github.ItsMalware/the-loungelive status →
mcp-registry/io.github.shree-git/sendit/get_conversationio.github.Shree-git/senditlive status →
mcp-registry/io.github.agentlinehq/agentline/list_messagesio.github.AgentLineHQ/agentlinelive status →
mcp-registry/com.almured/marketplace/read_messagescom.almured/marketplacelive status →

FAQ

What is the best alternative to mcp-registry/io.github.saloprj/dialogbrain/messages_read_history?

mcp-registry/io.favcrm/favcrm/get_conversation_messages is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.trycourier/courier/get_message_history, mcp-registry/io.github.agentlinehq/agentline/list_calls, mcp-registry/io.favcrm/favcrm/list_conversations, mcp-registry/io.github.pipeworx-io/intercom/ic_get_conversation. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.saloprj/dialogbrain/messages_read_history down right now?

mcp-registry/io.github.saloprj/dialogbrain/messages_read_history's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.saloprj%2Fdialogbrain%2Fmessages_read_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.saloprj%2Fdialogbrain%2Fmessages_read_history or MCP find_alternatives. Check mcp-registry/io.github.saloprj/dialogbrain/messages_read_history's live status: https://glimind.com/tool/mcp-registry/io.github.saloprj/dialogbrain/messages_read_history.