Tornadoes MCP server
{
"mcpServers": {
"daedalmap-tornadoes": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/tornadoes"
}
}
}{
"mcpServers": {
"daedalmap-tornadoes": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/tornadoes"
}
}
}{
"mcpServers": {
"daedalmap-tornadoes": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/tornadoes"
}
}
}{
"servers": {
"daedalmap-tornadoes": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/tornadoes"
}
}
}{
"mcpServers": {
"daedalmap-tornadoes": {
"type": "http",
"url": "https://app.daedalmap.com/mcp/tornadoes"
}
}
}What it does
DaedalMap exposes US tornado events from 1950 to present via the NOAA Storm Prediction Center, including EF ratings, tracks, and damage data. It is for developers building applications that need to query tornado events by location and time, join tornado data with other geographic datasets, or integrate tornado information into geographic analysis workflows.
- Query tornado events for a specific US location and time window to show historical storm activity.
- Join tornado damage data with population or economic indicators to compare disaster impact across regions.
- Download tornado tracks and EF ratings locally or query them through the hosted MCP endpoint for analysis.
Tools this server exposes
| Tool | Does |
|---|---|
| get_catalog | Discover available data packs, including the tornado dataset. |
| read_geometry_catalog | Check current geometry coverage for tornado events and other datasets. |
This entry comes from the registry but points to no public repository, so there is nothing to check: no commit history, no source, no tool list. It is listed for completeness and left out of search engines.
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.