mcp-registry/io.github.rippermercs/terminalfeed/tf_briefing / alternatives
mcp-registry/io.github.rippermercs/terminalfeed/tf_briefingThe best live alternatives to mcp-registry/io.github.rippermercs/terminalfeed/tf_briefing right now are mcp-registry/io.github.marvinrey7879/patternfetch/patternfetch_brief, mcp-registry/com.prereason/mcp/get_context, mcp-registry/io.github.pipeworx-io/macro-snapshot/macro_snapshot, mcp-registry/io.github.getgapup/mcp-knowledge/realtime_data_streams, mcp-registry/io.github.getgapup/gapup-mcp/realtime_data_streams — capability-matched and ranked by current reliability. mcp-registry/io.github.rippermercs/terminalfeed/tf_briefing itself is currently "healthy".
mcp-registry/io.github.marvinrey7879/patternfetch/patternfetch_brief is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.prereason/mcp/get_context, mcp-registry/io.github.pipeworx-io/macro-snapshot/macro_snapshot, mcp-registry/io.github.getgapup/mcp-knowledge/realtime_data_streams, mcp-registry/io.github.getgapup/gapup-mcp/realtime_data_streams. Glimind ranks alternatives by semantic similarity and live health.
mcp-registry/io.github.rippermercs/terminalfeed/tf_briefing's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.rippermercs%2Fterminalfeed%2Ftf_briefing.
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.
Get a live, capability-matched substitute in one call: GET https://glimind.com/v1/alternatives/mcp-registry%2Fio.github.rippermercs%2Fterminalfeed%2Ftf_briefing
or MCP find_alternatives. Check mcp-registry/io.github.rippermercs/terminalfeed/tf_briefing's live status: https://glimind.com/tool/mcp-registry/io.github.rippermercs/terminalfeed/tf_briefing.