mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup / alternatives

Live alternatives to mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup

The best live alternatives to mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup right now are mcp-registry/ai.readypermit/geo/check_flood_zone, mcp-registry/ai.readypermit/geo/analyze_property, mcp-registry/io.github.pipeworx-io/epa-envirofacts/facilities_by_zip, mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/get_zoning_info, mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_disaster_risk_profile — capability-matched and ranked by current reliability. mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup itself is currently "healthy".

alternative	server
mcp-registry/ai.readypermit/geo/check_flood_zone	ai.readypermit/geo	live status →
mcp-registry/ai.readypermit/geo/analyze_property	ai.readypermit/geo	live status →
mcp-registry/io.github.pipeworx-io/epa-envirofacts/facilities_by_zip	io.github.pipeworx-io/epa-envirofacts	live status →
mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/get_zoning_info	io.github.sugukurukabe/japan-real-estate-intel-mcp	live status →
mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_disaster_risk_profile	io.github.andrew-sondgeroth/zipexplore-mcp	live status →
mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations	io.github.pipeworx-io/openfema	live status →
mcp-registry/io.github.pipeworx-io/flood/get_flood_forecast	io.github.pipeworx-io/flood	live status →
mcp-registry/com.stratalize/finance/get_climate_risk_benchmark	com.stratalize/finance	live status →
mcp-registry/io.github.pipeworx-io/open-meteo/flood	io.github.pipeworx-io/open-meteo	live status →
mcp-registry/io.github.mcflamingo/local-intel/local_intel_zone	io.github.MCFLAMINGO/local-intel	live status →
mcp-registry/io.github.usdvcapital/real-estate-cfo/util-insurance	io.github.USDVCapital/real-estate-cfo	live status →
mcp-registry/io.github.foundrynet/foundrynet-geo/facility_risk	io.github.FoundryNet/foundrynet-geo	live status →

FAQ

What is the best alternative to mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup?

mcp-registry/ai.readypermit/geo/check_flood_zone is the top capability-matched alternative that's live right now. Other options: mcp-registry/ai.readypermit/geo/analyze_property, mcp-registry/io.github.pipeworx-io/epa-envirofacts/facilities_by_zip, mcp-registry/io.github.sugukurukabe/japan-real-estate-intel-mcp/get_zoning_info, mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_disaster_risk_profile. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup down right now?

mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.blackboxfoundry%2Flivedatalink%2Fflood_zone_lookup.

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.blackboxfoundry%2Flivedatalink%2Fflood_zone_lookup or MCP find_alternatives. Check mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup's live status: https://glimind.com/tool/mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookup.