mcp-registry/com.peerpush/peerpush/peerpush_trending / alternatives

Live alternatives to mcp-registry/com.peerpush/peerpush/peerpush_trending

The best live alternatives to mcp-registry/com.peerpush/peerpush/peerpush_trending right now are mcp-registry/io.github.pipeworx-io/google_calendar/pipeworx_trending, mcp-registry/io.github.pipeworx-io/tomorrow-io/pipeworx_trending, mcp-registry/io.github.pipeworx-io/tiingo/pipeworx_trending, mcp-registry/io.github.pipeworx-io/theaudiodb/pipeworx_trending, mcp-registry/io.github.pipeworx-io/statbel-be/pipeworx_trending — capability-matched and ranked by current reliability. mcp-registry/com.peerpush/peerpush/peerpush_trending 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/tomorrow-io/pipeworx_trending	io.github.pipeworx-io/tomorrow-io	live status →
mcp-registry/io.github.pipeworx-io/tiingo/pipeworx_trending	io.github.pipeworx-io/tiingo	live status →
mcp-registry/io.github.pipeworx-io/theaudiodb/pipeworx_trending	io.github.pipeworx-io/theaudiodb	live status →
mcp-registry/io.github.pipeworx-io/statbel-be/pipeworx_trending	io.github.pipeworx-io/statbel-be	live status →
mcp-registry/io.github.pipeworx-io/sports/pipeworx_trending	io.github.pipeworx-io/sports	live status →
mcp-registry/io.github.pipeworx-io/sefaria/pipeworx_trending	io.github.pipeworx-io/sefaria	live status →
mcp-registry/io.github.pipeworx-io/rfc-editor/pipeworx_trending	io.github.pipeworx-io/rfc-editor	live status →
mcp-registry/io.github.pipeworx-io/polymarket/pipeworx_trending	io.github.pipeworx-io/polymarket	live status →
mcp-registry/io.github.pipeworx-io/paleobiodb/pipeworx_trending	io.github.pipeworx-io/paleobiodb	live status →
mcp-registry/io.github.pipeworx-io/pangaea/pipeworx_trending	io.github.pipeworx-io/pangaea	live status →
mcp-registry/io.github.pipeworx-io/zippopotam/pipeworx_trending	io.github.pipeworx-io/zippopotam	live status →

FAQ

What is the best alternative to mcp-registry/com.peerpush/peerpush/peerpush_trending?

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/tomorrow-io/pipeworx_trending, mcp-registry/io.github.pipeworx-io/tiingo/pipeworx_trending, mcp-registry/io.github.pipeworx-io/theaudiodb/pipeworx_trending, mcp-registry/io.github.pipeworx-io/statbel-be/pipeworx_trending. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.peerpush/peerpush/peerpush_trending down right now?

mcp-registry/com.peerpush/peerpush/peerpush_trending's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.peerpush%2Fpeerpush%2Fpeerpush_trending.

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%2Fcom.peerpush%2Fpeerpush%2Fpeerpush_trending or MCP find_alternatives. Check mcp-registry/com.peerpush/peerpush/peerpush_trending's live status: https://glimind.com/tool/mcp-registry/com.peerpush/peerpush/peerpush_trending.