mcp-registry/io.github.pipeworx-io/slack_connect/slack_channel_history / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/slack_connect/slack_channel_history

The best live alternatives to mcp-registry/io.github.pipeworx-io/slack_connect/slack_channel_history right now are mcp-registry/io.github.tathagat22/slipstream/slipstream_recall, mcp-registry/co.superforms/superforms/list_asks, mcp-registry/io.github.pipeworx-io/urlhaus/pipeworx_trending, mcp-registry/io.github.pipeworx-io/studio-ghibli/pipeworx_trending, mcp-registry/io.github.pipeworx-io/statec-lu/pipeworx_trending — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/slack_connect/slack_channel_history itself is currently "healthy".

alternative	server
mcp-registry/io.github.tathagat22/slipstream/slipstream_recall	io.github.tathagat22/slipstream	live status →
mcp-registry/co.superforms/superforms/list_asks	co.superforms/superforms	live status →
mcp-registry/io.github.pipeworx-io/urlhaus/pipeworx_trending	io.github.pipeworx-io/urlhaus	live status →
mcp-registry/io.github.pipeworx-io/studio-ghibli/pipeworx_trending	io.github.pipeworx-io/studio-ghibli	live status →
mcp-registry/io.github.pipeworx-io/statec-lu/pipeworx_trending	io.github.pipeworx-io/statec-lu	live status →
mcp-registry/io.github.pipeworx-io/jpl-ssd/pipeworx_trending	io.github.pipeworx-io/jpl-ssd	live status →
mcp-registry/io.github.pipeworx-io/themeparks/pipeworx_trending	io.github.pipeworx-io/themeparks	live status →
mcp-registry/io.github.pipeworx-io/fbiwanted/pipeworx_trending	io.github.pipeworx-io/fbiwanted	live status →
mcp-registry/io.github.pipeworx-io/sec-xbrl/pipeworx_trending	io.github.pipeworx-io/sec-xbrl	live status →
mcp-registry/io.github.pipeworx-io/nsf-awards/pipeworx_trending	io.github.pipeworx-io/nsf-awards	live status →
mcp-registry/io.github.pipeworx-io/nps/pipeworx_trending	io.github.pipeworx-io/nps	live status →
mcp-registry/io.github.pipeworx-io/musicbrainz/pipeworx_trending	io.github.pipeworx-io/musicbrainz	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/slack_connect/slack_channel_history?

mcp-registry/io.github.tathagat22/slipstream/slipstream_recall is the top capability-matched alternative that's live right now. Other options: mcp-registry/co.superforms/superforms/list_asks, mcp-registry/io.github.pipeworx-io/urlhaus/pipeworx_trending, mcp-registry/io.github.pipeworx-io/studio-ghibli/pipeworx_trending, mcp-registry/io.github.pipeworx-io/statec-lu/pipeworx_trending. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/slack_connect/slack_channel_history down right now?

mcp-registry/io.github.pipeworx-io/slack_connect/slack_channel_history's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fslack_connect%2Fslack_channel_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.pipeworx-io%2Fslack_connect%2Fslack_channel_history or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/slack_connect/slack_channel_history's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/slack_connect/slack_channel_history.