mcp-registry/io.github.pipeworx-io/data-calgary/calgary_recent / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/data-calgary/calgary_recent

The best live alternatives to mcp-registry/io.github.pipeworx-io/data-calgary/calgary_recent right now are mcp-registry/io.github.pipeworx-io/close-crm/recent_alerts, mcp-registry/io.github.pipeworx-io/climate/recent_alerts, mcp-registry/io.github.pipeworx-io/open-notify/recent_alerts, mcp-registry/io.github.pipeworx-io/open-meteo/recent_alerts, mcp-registry/io.github.pipeworx-io/octopus-energy/recent_alerts — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/data-calgary/calgary_recent itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/close-crm/recent_alerts	io.github.pipeworx-io/close-crm	live status →
mcp-registry/io.github.pipeworx-io/climate/recent_alerts	io.github.pipeworx-io/climate	live status →
mcp-registry/io.github.pipeworx-io/open-notify/recent_alerts	io.github.pipeworx-io/open-notify	live status →
mcp-registry/io.github.pipeworx-io/open-meteo/recent_alerts	io.github.pipeworx-io/open-meteo	live status →
mcp-registry/io.github.pipeworx-io/octopus-energy/recent_alerts	io.github.pipeworx-io/octopus-energy	live status →
mcp-registry/io.github.pipeworx-io/take-the-meeting/recent_alerts	io.github.pipeworx-io/take-the-meeting	live status →
mcp-registry/io.github.pipeworx-io/ship-on-friday/recent_alerts	io.github.pipeworx-io/ship-on-friday	live status →
mcp-registry/io.github.pipeworx-io/chaos-index/recent_alerts	io.github.pipeworx-io/chaos-index	live status →
mcp-registry/io.github.pipeworx-io/timeapi-io/recent_alerts	io.github.pipeworx-io/timeapi-io	live status →
mcp-registry/io.github.pipeworx-io/kitsu/recent_alerts	io.github.pipeworx-io/kitsu	live status →
mcp-registry/io.github.pipeworx-io/ipinfo/recent_alerts	io.github.pipeworx-io/ipinfo	live status →
mcp-registry/io.github.pipeworx-io/inspire-hep/recent_alerts	io.github.pipeworx-io/inspire-hep	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/data-calgary/calgary_recent?

mcp-registry/io.github.pipeworx-io/close-crm/recent_alerts is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/climate/recent_alerts, mcp-registry/io.github.pipeworx-io/open-notify/recent_alerts, mcp-registry/io.github.pipeworx-io/open-meteo/recent_alerts, mcp-registry/io.github.pipeworx-io/octopus-energy/recent_alerts. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/data-calgary/calgary_recent down right now?

mcp-registry/io.github.pipeworx-io/data-calgary/calgary_recent's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fdata-calgary%2Fcalgary_recent.

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%2Fdata-calgary%2Fcalgary_recent or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/data-calgary/calgary_recent's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/data-calgary/calgary_recent.