mcp-registry/io.github.pipeworx-io/flood/get_flood_forecast / alternatives

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

The best live alternatives to mcp-registry/io.github.pipeworx-io/flood/get_flood_forecast right now are mcp-registry/io.github.pipeworx-io/open-meteo/flood, mcp-registry/ai.dynamicfeed/dynamic-feed/flood_forecast, mcp-registry/io.github.pipeworx-io/usgs-water/daily_values, mcp-registry/io.github.pipeworx-io/marine/get_wave_forecast, mcp-registry/com.olyport/water/get_flood_status — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/flood/get_flood_forecast itself is currently "healthy".

alternative	server
mcp-registry/io.github.pipeworx-io/open-meteo/flood	io.github.pipeworx-io/open-meteo	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/flood_forecast	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.pipeworx-io/usgs-water/daily_values	io.github.pipeworx-io/usgs-water	live status →
mcp-registry/io.github.pipeworx-io/marine/get_wave_forecast	io.github.pipeworx-io/marine	live status →
mcp-registry/com.olyport/water/get_flood_status	com.olyport/water	live status →
pulsemcp/adbutler/get_display_forecast	AdButler	live status →
mcp-registry/com.adbutler/mcp-server/get_display_forecast	com.adbutler/mcp-server	live status →
mcp-registry/ai.dynamicfeed/dynamic-feed/uk_water	ai.dynamicfeed/dynamic-feed	live status →
mcp-registry/io.github.pipeworx-io/nws/get_forecast	io.github.pipeworx-io/nws	live status →
mcp-registry/io.github.pipeworx-io/weather/get_forecast	io.github.pipeworx-io/weather	live status →
mcp-registry/dev.infranode/infranode/flood	dev.infranode/infranode	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_history_summary	io.github.blackboxfoundry/livedatalink	live status →

FAQ

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

mcp-registry/io.github.pipeworx-io/open-meteo/flood 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/usgs-water/daily_values, mcp-registry/io.github.pipeworx-io/marine/get_wave_forecast, mcp-registry/com.olyport/water/get_flood_status. Glimind ranks alternatives by semantic similarity and live health.

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

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

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