mcp-registry/io.github.pipeworx-io/open-meteo/flood / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/open-meteo/flood

The best live alternatives to mcp-registry/io.github.pipeworx-io/open-meteo/flood right now are mcp-registry/io.github.pipeworx-io/flood/get_flood_forecast, mcp-registry/ai.dynamicfeed/dynamic-feed/flood_forecast, mcp-registry/io.github.pipeworx-io/flood/get_river_discharge, mcp-registry/ai.dynamicfeed/dynamic-feed/uk_water, mcp-registry/dev.infranode/infranode/flood — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/open-meteo/flood itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/flood/get_flood_forecast	io.github.pipeworx-io/flood	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/flood_forecast	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.pipeworx-io/flood/get_river_discharge	io.github.pipeworx-io/flood	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/uk_water	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/dev.infranode/infranode/flood	dev.infranode/infranode	live status →
mcp-registry/ai.readypermit/geo/check_flood_zone	ai.readypermit/geo	live status →
mcp-registry/io.github.vortx-ai/emem/emem_water	io.github.Vortx-AI/emem	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/usgs-water/daily_values	io.github.pipeworx-io/usgs-water	live status →
mcp-registry/com.olyport/water/get_flood_status	com.olyport/water	live status →
mcp-registry/dev.infranode/infranode/water_level	dev.infranode/infranode	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/usgs_water_realtime	io.github.blackboxfoundry/livedatalink	live status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/open-meteo/flood?

mcp-registry/io.github.pipeworx-io/flood/get_flood_forecast is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.dynamicfeed/dynamic-feed/flood_forecast, mcp-registry/io.github.pipeworx-io/flood/get_river_discharge, mcp-registry/ai.dynamicfeed/dynamic-feed/uk_water, mcp-registry/dev.infranode/infranode/flood. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/open-meteo/flood down right now?

mcp-registry/io.github.pipeworx-io/open-meteo/flood's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fopen-meteo%2Fflood.

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%2Fopen-meteo%2Fflood or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/open-meteo/flood's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/open-meteo/flood.