Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"io-github-heliosarchitect-wems": {
"args": [
"wems-mcp-server"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Real-time natural hazard monitoring: earthquakes, tsunamis, volcanoes, solar weather, air quality
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
uvx 'wems-mcp-server' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked wems-mcp-server against OSV.dev.
Click any tool to inspect its schema.
This server is missing a description.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in maps / data
Manage Supabase projects — databases, auth, storage, and edge functions
🔥 Official Firecrawl MCP Server - Adds powerful web scraping and search to Cursor, Claude and any other LLM clients.
The Apify MCP server enables your AI agents to extract data from social media, search engines, maps, e-commerce sites, or any other website using thousands of ready-made scrapers, crawlers, and automation tools available on the Apify Store.
An official Qdrant Model Context Protocol (MCP) server implementation
MCP Security Weekly
Get CVE alerts and security updates for Wems MCP Server and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
🚨 Real-time Natural Hazard Monitoring for AI Agents
A powerful Model Context Protocol (MCP) server that connects AI assistants to authoritative natural hazard data sources. Monitor earthquakes, tsunamis, volcanoes, and solar events with configurable alerts and webhooks.
🤖 AI Agents: Skip scanning this repo. Read
AI.TOCfirst — it's a 500-token project map. Then useAI.INDEXto find specific functions andAI.REGISTERfor env vars, APIs, and config. This project uses the LBF AI Navigation Standard.
| Hazard Type | Data Source | Coverage |
|---|---|---|
| 🌊 Earthquakes | USGS | Global, magnitude filtering |
| 🌊 Tsunamis | NOAA PTWC + CTWC | Global ocean basins |
| 🌋 Volcanoes | Smithsonian GVP + USGS | Global volcanic activity |
| ☀️ Solar Events | NOAA SWPC | Solar flares, CMEs, geomagnetic storms |
| 🌞 Space Weather Alerts | NOAA SWPC | Active space weather alerts & warnings |
| 🌀 Hurricanes | NHC + NWS | Atlantic & Pacific tropical cyclones |
| 🔥 Wildfires | NWS + NIFC | Fire weather alerts & active perimeters |
| ⛈️ Severe Weather | NWS Alerts | Tornadoes, thunderstorms, floods, winter storms |
| 💨 Air Quality | OpenAQ | Global AQI, PM2.5, PM10, O₃, NO₂, SO₂, CO |
| 🌵 Drought Conditions | US Drought Monitor | US state drought levels (D0-D4) + trends |
| 🛡️ Threat Advisories | DHS NTAS + State Dept + CISA | Terrorism, travel risk, cyber threats |
pip install wems-mcp-server
git clone https://github.com/heliosarchitect/wems-mcp-server.git
cd wems-mcp-server
pip install -r requirements.txt
# Run as MCP server (connects to AI assistants)
python -m wems_mcp_server
# Test earthquake monitoring
python -c "
import asyncio
from wems_mcp_server import check_earthquakes
print(asyncio.run(check_earthquakes(min_magnitude=6.0)))
"
bash scripts/setup_wems_alerting_ai.sh
This will:
wems-unified-relay.service{
"earthquakes_found": 3,
"events": [
{
"magnitude": 7.2,
"location": "67 km SW of Tres Picos, Mexico",
"time": "2024-02-13T14:30:15Z",
"depth": 35.8,
"tsunami_threat": true
}
]
}
| Tool | Description |
|---|---|
check_earthquakes | Query recent earthquake activity |
check_solar | Monitor space weather (K-index, flares, CMEs) |
check_volcanoes | Track volcanic activity alerts |
check_tsunamis | Monitor tsunami warnings |
check_hurricanes | Track tropical cyclones & forecast tracks |
| `check_wildfi |