mcp-registry/com.olyport/fema/get_disaster_detail / alternatives

Live alternatives to mcp-registry/com.olyport/fema/get_disaster_detail

The best live alternatives to mcp-registry/com.olyport/fema/get_disaster_detail right now are mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_declarations, mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations, mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_history_summary, mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_disaster_risk_profile, mcp-registry/com.daedalmap/earthquakes/get_disaster_links_for_event — capability-matched and ranked by current reliability. mcp-registry/com.olyport/fema/get_disaster_detail itself is currently "healthy".

alternative	server
mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_declarations	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations	io.github.pipeworx-io/openfema	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_history_summary	io.github.blackboxfoundry/livedatalink	live status →
mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_disaster_risk_profile	io.github.andrew-sondgeroth/zipexplore-mcp	live status →
mcp-registry/com.daedalmap/earthquakes/get_disaster_links_for_event	com.daedalmap/earthquakes	live status →
mcp-registry/com.daedalmap/county-map/get_disaster_links_for_event	com.daedalmap/county-map	live status →
mcp-registry/com.daedalmap/wildfires/get_disaster_links_for_event	com.daedalmap/wildfires	live status →
mcp-registry/com.daedalmap/tsunamis/get_disaster_links_for_event	com.daedalmap/tsunamis	live status →
mcp-registry/com.daedalmap/volcanoes/get_disaster_links_for_event	com.daedalmap/volcanoes	live status →
mcp-registry/io.github.pipeworx-io/gdacs/event	io.github.pipeworx-io/gdacs	live status →
mcp-registry/com.olyport/earthquake/get_earthquake_detail	com.olyport/earthquake	live status →
mcp-registry/io.github.blackboxfoundry/livedatalink/usgs_earthquake_detail	io.github.blackboxfoundry/livedatalink	live status →

FAQ

What is the best alternative to mcp-registry/com.olyport/fema/get_disaster_detail?

mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_declarations is the top capability-matched alternative that's live right now. Other options: mcp-registry/io.github.pipeworx-io/openfema/disaster_declarations, mcp-registry/io.github.blackboxfoundry/livedatalink/disaster_history_summary, mcp-registry/io.github.andrew-sondgeroth/zipexplore-mcp/get_disaster_risk_profile, mcp-registry/com.daedalmap/earthquakes/get_disaster_links_for_event. Glimind ranks alternatives by semantic similarity and live health.

Is mcp-registry/com.olyport/fema/get_disaster_detail down right now?

mcp-registry/com.olyport/fema/get_disaster_detail's current verdict is "healthy". See its live status and score at https://glimind.com/tool/mcp-registry%2Fcom.olyport%2Ffema%2Fget_disaster_detail.

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%2Ffema%2Fget_disaster_detail or MCP find_alternatives. Check mcp-registry/com.olyport/fema/get_disaster_detail's live status: https://glimind.com/tool/mcp-registry/com.olyport/fema/get_disaster_detail.