mcp-registry/io.github.tathagat22/slipstream/slipstream_recall / alternatives

Live alternatives to mcp-registry/io.github.tathagat22/slipstream/slipstream_recall

The best live alternatives to mcp-registry/io.github.tathagat22/slipstream/slipstream_recall right now are mcp-registry/io.sentinelsignal/verify/get_drift_report, mcp-registry/ai.agentberg/agentberg/query_findings, mcp-registry/io.github.alisammour/storyflo-mcp/digest, mcp-registry/io.github.dan-cleary/convalytics/weekly_digest, mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending — capability-matched and ranked by current reliability. mcp-registry/io.github.tathagat22/slipstream/slipstream_recall itself is currently "healthy".

alternative	server
mcp-registry/io.sentinelsignal/verify/get_drift_report	io.sentinelsignal/verify	live status →
mcp-registry/ai.agentberg/agentberg/query_findings	ai.agentberg/agentberg	live status →
mcp-registry/io.github.alisammour/storyflo-mcp/digest	io.github.Alisammour/storyflo-mcp	live status →
mcp-registry/io.github.dan-cleary/convalytics/weekly_digest	io.github.Dan-Cleary/convalytics	live status →
mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending	io.github.pipeworx-io/google_calendar	live status →
mcp-registry/io.github.pipeworx-io/sarb-za/pipeworx_trending	io.github.pipeworx-io/sarb-za	live status →
mcp-registry/io.github.pipeworx-io/monarch-initiative/pipeworx_trending	io.github.pipeworx-io/monarch-initiative	live status →
mcp-registry/io.github.pipeworx-io/ripe-stat/pipeworx_trending	io.github.pipeworx-io/ripe-stat	live status →
mcp-registry/io.github.pipeworx-io/ipqualityscore/pipeworx_trending	io.github.pipeworx-io/ipqualityscore	live status →
mcp-registry/io.github.pipeworx-io/openweather/pipeworx_trending	io.github.pipeworx-io/openweather	live status →
mcp-registry/io.github.pipeworx-io/timeapi-io/pipeworx_trending	io.github.pipeworx-io/timeapi-io	live status →
mcp-registry/io.github.pipeworx-io/un-sdg/pipeworx_trending	io.github.pipeworx-io/un-sdg	live status →

FAQ

What is the best alternative to mcp-registry/io.github.tathagat22/slipstream/slipstream_recall?

mcp-registry/io.sentinelsignal/verify/get_drift_report is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.agentberg/agentberg/query_findings, mcp-registry/io.github.alisammour/storyflo-mcp/digest, mcp-registry/io.github.dan-cleary/convalytics/weekly_digest, mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.tathagat22/slipstream/slipstream_recall down right now?

mcp-registry/io.github.tathagat22/slipstream/slipstream_recall's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.tathagat22%2Fslipstream%2Fslipstream_recall.

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.tathagat22%2Fslipstream%2Fslipstream_recall or MCP find_alternatives. Check mcp-registry/io.github.tathagat22/slipstream/slipstream_recall's live status: https://glimind.com/tool/mcp-registry/io.github.tathagat22/slipstream/slipstream_recall.