RedAlert MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| REDALERT_API_KEY | Yes | Your RedAlert API key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_active_alertsA | Get real-time snapshot of cities currently under alert, grouped by alert type (missiles, earthquakes, etc.) |
| get_stats_summaryB | Get high-level overview of the alert system: totals, unique cities/zones, and optional top cities/zones/origins/timeline/peak data |
| get_stats_citiesB | Get city-level alert statistics with pagination, search, and optional translations/coordinates |
| get_stats_historyB | Get detailed historical alert records with full city data, filtering, sorting, and pagination |
| get_stats_distributionA | Get alert distribution grouped by category or origin, with filtering, sorting, and pagination |
| search_sheltersA | Find nearby shelters. Provide lat/lon directly, or just a city name to auto-resolve coordinates. |
| get_citiesA | Get city catalog for lookups - raw location records with optional translations, coordinates, and countdown times |
| health_checkA | Check the health status of the RedAlert API |
| subscribe_alertsB | Connect to RedAlert Socket.IO server and start receiving real-time emergency alerts. Optionally filter by alert types and enable test mode for simulated alerts. |
| poll_alertsA | Retrieve buffered real-time alerts that arrived since the last poll. Must call subscribe_alerts first. |
| unsubscribe_alertsA | Disconnect from RedAlert Socket.IO server and stop receiving real-time alerts. Clears the alert buffer. |
| get_alert_subscription_statusA | Check the current real-time alert subscription status including connection state, subscribed types, and buffer size. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: current alerts, historical stats, real-time subscription, shelters, health check. No two tools overlap in functionality.
Tools mostly follow a verb_noun snake_case pattern (e.g., get_active_alerts, subscribe_alerts). 'health_check' deviates slightly, but overall consistent.
12 tools cover the domain well—real-time alerts, stats, shelters, health—without being excessive or sparse.
The toolset covers all essential operations: viewing active alerts, subscribing/polling real-time data, accessing historical statistics, and finding shelters. No obvious gaps.