mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations / alternatives

Live alternatives to mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations

The best live alternatives to mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations right now are mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_declarations, mcp-registry/com.olyport/fema/get_disaster_declarations, mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_history_summary, mcp-registry/com.olyport/fema/get_disaster_detail, mcp-registry/io.github.pipeworx-io/gdacs/events — capability-matched and ranked by current reliability. mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations itself is currently "healthy".

alternativeserver
mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_declarationsio.github.blackboxfoundry/livedatalinklive status →
mcp-registry/com.olyport/fema/get_disaster_declarationscom.olyport/femalive status →
mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_history_summaryio.github.blackboxfoundry/livedatalinklive status →
mcp-registry/com.olyport/fema/get_disaster_detailcom.olyport/femalive status →
mcp-registry/io.github.pipeworx-io/gdacs/eventsio.github.pipeworx-io/gdacslive status →
mcp-registry/com.olyport/fema/get_public_assistancecom.olyport/femalive status →
mcp-registry/io.github.blackboxfoundry/livedatalink/flood_zone_lookupio.github.blackboxfoundry/livedatalinklive status →
mcp-registry/com.stratalize/realestate/get_noaa_disaster_economicscom.stratalize/realestatelive status →
mcp-registry/com.olyport/fema/get_individual_assistancecom.olyport/femalive status →
mcp-registry/com.daedalmap/volcanoes/search_disaster_linkscom.daedalmap/volcanoeslive status →
mcp-registry/com.daedalmap/tornadoes/search_disaster_linkscom.daedalmap/tornadoeslive status →
mcp-registry/com.daedalmap/tsunamis/search_disaster_linkscom.daedalmap/tsunamislive status →

FAQ

What is the best alternative to mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations?

mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_declarations is the top capability-matched alternative that's live right now. Other options: mcp-registry/com.olyport/fema/get_disaster_declarations, mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_history_summary, mcp-registry/com.olyport/fema/get_disaster_detail, mcp-registry/io.github.pipeworx-io/gdacs/events. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations down right now?

mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fio.github.pipeworx-io%2Fopenfema%2Fdisaster_declarations.

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%2Fopenfema%2Fdisaster_declarations or MCP find_alternatives. Check mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations's live status: https://glimind.com/tool/mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations.