mcp-registry/com.olyport/nws-alerts/get_alerts / alternatives

Live alternatives to mcp-registry/com.olyport/nws-alerts/get_alerts

The best live alternatives to mcp-registry/com.olyport/nws-alerts/get_alerts right now are mcp-registry/io.github.pipeworx-io/nws/get_alerts, mcp-registry/ai.dynamicfeed/dynamic-feed/weather_alerts, mcp-registry/ai.intuitek.the-stall/the-stall/weather-alerts, mcp-registry/io.github.foundrynet/weather-intel-mcp/weather_alerts, mcp-registry/io.github.colinhughes2121/gocreative-agent-api/weather_alerts — capability-matched and ranked by current reliability. mcp-registry/com.olyport/nws-alerts/get_alerts itself is currently "healthy".

alternativeserver
mcp-registry/io.github.pipeworx-io/nws/get_alertsio.github.pipeworx-io/nwslive status →
mcp-registry/ai.dynamicfeed/dynamic-feed/weather_alertsai.dynamicfeed/dynamic-feedlive status →
mcp-registry/ai.intuitek.the-stall/the-stall/weather-alertsai.intuitek.the-stall/the-stalllive status →
mcp-registry/io.github.foundrynet/weather-intel-mcp/weather_alertsio.github.FoundryNet/weather-intel-mcplive status →
mcp-registry/io.github.colinhughes2121/gocreative-agent-api/weather_alertsio.github.ColinHughes2121/gocreative-agent-apilive status →
mcp-registry/io.github.blackboxfoundry/livedatalink/nws_active_alertsio.github.blackboxfoundry/livedatalinklive status →
mcp-registry/io.github.pipeworx-io/nps/list_alertsio.github.pipeworx-io/npslive status →
mcp-registry/com.olyport/water/get_flood_statuscom.olyport/waterlive status →
mcp-registry/com.olyport/water/get_sites_by_statecom.olyport/waterlive status →
mcp-registry/io.github.supplymaven-scr/supply-chain-intelligence/get_natural_disaster_alertsio.github.SupplyMaven-SCR/supply-chain-intelligencelive status →
mcp-registry/com.olyport/wildfire/get_active_firescom.olyport/wildfirelive status →
mcp-registry/io.github.pipeworx-io/weather-gc-ca/active_alertsio.github.pipeworx-io/weather-gc-calive status →

FAQ

What is the best alternative to mcp-registry/com.olyport/nws-alerts/get_alerts?

mcp-registry/io.github.pipeworx-io/nws/get_alerts is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.dynamicfeed/dynamic-feed/weather_alerts, mcp-registry/ai.intuitek.the-stall/the-stall/weather-alerts, mcp-registry/io.github.foundrynet/weather-intel-mcp/weather_alerts, mcp-registry/io.github.colinhughes2121/gocreative-agent-api/weather_alerts. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.olyport/nws-alerts/get_alerts down right now?

mcp-registry/com.olyport/nws-alerts/get_alerts's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.olyport%2Fnws-alerts%2Fget_alerts.

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.olyport%2Fnws-alerts%2Fget_alerts or MCP find_alternatives. Check mcp-registry/com.olyport/nws-alerts/get_alerts's live status: https://glimind.com/tool/mcp-registry/com.olyport/nws-alerts/get_alerts.