disaster-wire
Related Servers
Alternatives to disaster-wire
- AlicenseNot gradedqualityAmaintenanceAn MCP server for Datto BCDR (Business Continuity and Disaster Recovery), enabling management of backup jobs, restore points, and disaster recovery operations through Datto's API.Apache 2.0
- FlicenseNot gradedqualityBmaintenanceMCP server for querying the Kaggle 'All Natural Disasters 1900-2021 / EOSDIS' CSV dataset via pandas, exposing search and statistics tools.-
Related Servers
- AlicenseAqualityDmaintenanceGeopolitical conflict risk data for AI agents311 PyPI2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to query live earthquake and disaster event data, and to compute deterministic risk assessments with tamper-evident seals.MIT
- AlicenseBqualityBmaintenanceThe Decentralized Stripe & Radar for Autonomous AI Agents1028 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to query Earth observation data, satellite imagery, active fires, and weather via natural language, returning interactive maps and briefs.12MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLM agents to access live seismic data, calculate emergency vehicle routes, and dispatch first responders to incidents.MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that gives AI agents grounded access to US natural-hazard data — weather alerts, forecasts, earthquakes, and FEMA flood zones — from free, keyless US government APIs.MIT
TDQS
Scored across 3 tools
Each tool has a distinct purpose: discovery/filtering (list_active_disasters), single-event detail lookup (get_disaster_by_id), and spatial proximity search (find_disasters_near_coordinates). Descriptions explicitly guide when to use each and when not to, preventing misselection.
All tool names use snake_case with a leading verb and clear resource description, following a consistent verb_noun pattern. The slight variation in prepositional phrases (by_id, near_coordinates) remains predictable and readable.
Three tools is on the low end but well matched to the narrow read-only active-disaster monitoring scope. Each tool is necessary and non-redundant, though the surface could arguably host a few more query variants without bloat.
The tools cover the full read-only lifecycle for active disaster monitoring: discovery with filtering, detailed telemetry retrieval by ID, and geospatial exposure queries. No write operations are needed for this stated purpose, and minor extras like pagination or bulk retrieval are not essential.