mcp-registry/io.github.rippermercs/terminalfeed/tf_premium_github_velocity / alternatives

Live alternatives to mcp-registry/io.github.rippermercs/terminalfeed/tf_premium_github_velocity

The best live alternatives to mcp-registry/io.github.rippermercs/terminalfeed/tf_premium_github_velocity right now are mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending, mcp-registry/io.github.pipeworx-io/nhl/pipeworx_trending, mcp-registry/io.github.pipeworx-io/musicbrainz/pipeworx_trending, mcp-registry/io.github.pipeworx-io/mailchimp/pipeworx_trending, mcp-registry/io.github.pipeworx-io/kegg/pipeworx_trending — capability-matched and ranked by current reliability. mcp-registry/io.github.rippermercs/terminalfeed/tf_premium_github_velocity itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending	io.github.pipeworx-io/google_calendar	live status →
mcp-registry/io.github.pipeworx-io/nhl/pipeworx_trending	io.github.pipeworx-io/nhl	live status →
mcp-registry/io.github.pipeworx-io/musicbrainz/pipeworx_trending	io.github.pipeworx-io/musicbrainz	live status →
mcp-registry/io.github.pipeworx-io/mailchimp/pipeworx_trending	io.github.pipeworx-io/mailchimp	live status →
mcp-registry/io.github.pipeworx-io/kegg/pipeworx_trending	io.github.pipeworx-io/kegg	live status →
mcp-registry/io.github.pipeworx-io/ine-es/pipeworx_trending	io.github.pipeworx-io/ine-es	live status →
mcp-registry/io.github.pipeworx-io/openholidays/pipeworx_trending	io.github.pipeworx-io/openholidays	live status →
mcp-registry/io.github.pipeworx-io/currents/pipeworx_trending	io.github.pipeworx-io/currents	live status →
mcp-registry/io.github.pipeworx-io/congress/pipeworx_trending	io.github.pipeworx-io/congress	live status →
mcp-registry/io.github.pipeworx-io/court-listener/pipeworx_trending	io.github.pipeworx-io/court-listener	live status →
mcp-registry/io.github.pipeworx-io/cftc-cot/pipeworx_trending	io.github.pipeworx-io/cftc-cot	live status →
mcp-registry/io.github.pipeworx-io/carbon-interface/pipeworx_trending	io.github.pipeworx-io/carbon-interface	live status →

FAQ

What is the best alternative to mcp-registry/io.github.rippermercs/terminalfeed/tf_premium_github_velocity?

mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/nhl/pipeworx_trending, mcp-registry/io.github.pipeworx-io/musicbrainz/pipeworx_trending, mcp-registry/io.github.pipeworx-io/mailchimp/pipeworx_trending, mcp-registry/io.github.pipeworx-io/kegg/pipeworx_trending. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.rippermercs/terminalfeed/tf_premium_github_velocity down right now?

mcp-registry/io.github.rippermercs/terminalfeed/tf_premium_github_velocity's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.rippermercs%2Fterminalfeed%2Ftf_premium_github_velocity.

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.rippermercs%2Fterminalfeed%2Ftf_premium_github_velocity or MCP find_alternatives. Check mcp-registry/io.github.rippermercs/terminalfeed/tf_premium_github_velocity's live status: https://glimind.com/tool/mcp-registry/io.github.rippermercs/terminalfeed/tf_premium_github_velocity.