mcpField
W
wems

wems

Local
github.com/heliosarchitectScience & Education1Updated 35w ago

About wems

wems is an MCP server for AI agents that monitors natural hazards using authoritative data sources, with real-time queries, configurable thresholds, and webhook alerts. It serves risk monitoring, reporting, and research needs.

Key features

  1. 01Monitor earthquakes, tsunamis, and volcanoes
  2. 02Track solar and space weather events
  3. 03Cover hurricanes, wildfires, and severe weather
  4. 04Query air quality, drought, and threat advisories
  5. 05Set alerts by threshold and region
  6. 06Send notifications through webhooks

Use cases

  1. 01Assess hazard risks to global operations
  2. 02Get real-time event information for news reporting
  3. 03Collect natural hazard data for research
  4. 04Set up location-specific hazard monitoring for families

MCP support

Exposes natural hazard query tools to MCP clients, including checks for multiple event types, alert configuration, and multi-source incident fusion.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"heliosarchitect-wems": {
"command": "uvx",
"args": [
"wems-mcp-server"
]
}
}
}
Run commanduvx wems-mcp-server

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
pypiwems-mcp-server1.5.3

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

🌍 WEMS - World Event Monitoring System

PyPI version License: MIT Python 3.8+ MCP Compatible

🚨 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.TOC first — it's a 500-token project map. Then use AI.INDEX to find specific functions and AI.REGISTER for env vars, APIs, and config. This project uses the LBF AI Navigation Standard.

⚡ Key Features

  • 🌋 9+ Authoritative Data Sources: USGS, NOAA, Smithsonian GVP, NHC, NIFC, OpenAQ, DHS, State Dept, CISA, US Drought Monitor
  • 🎯 Real-time Monitoring: Live data feeds with customizable thresholds
  • 🔔 Smart Alerts: Webhook notifications for critical events
  • 🗺️ Geographic Filtering: Target specific regions or global coverage
  • 🔧 Zero Configuration: Works out-of-the-box, configure only what you need
  • 🐳 Production Ready: Docker support, comprehensive error handling
Natural Hazards Covered
Hazard TypeData SourceCoverage
🌊 EarthquakesUSGSGlobal, magnitude filtering
🌊 TsunamisNOAA PTWC + CTWCGlobal ocean basins
🌋 VolcanoesSmithsonian GVP + USGSGlobal volcanic activity
☀️ Solar EventsNOAA SWPCSolar flares, CMEs, geomagnetic storms
🌞 Space Weather AlertsNOAA SWPCActive space weather alerts & warnings
🌀 HurricanesNHC + NWSAtlantic & Pacific tropical cyclones
🔥 WildfiresNWS + NIFCFire weather alerts & active perimeters
⛈️ Severe WeatherNWS AlertsTornadoes, thunderstorms, floods, winter storms
💨 Air QualityOpenAQGlobal AQI, PM2.5, PM10, O₃, NO₂, SO₂, CO
🌵 Drought ConditionsUS Drought MonitorUS state drought levels (D0-D4) + trends
🛡️ Threat AdvisoriesDHS NTAS + State Dept + CISATerrorism, travel risk, cyber threats

🚀 Quick Start

Install via PyPI (Recommended)
pip install wems-mcp-server
Or install from source
git clone https://github.com/heliosarchitect/wems-mcp-server.git
cd wems-mcp-server
pip install -r requirements.txt
Basic Usage
# 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)))
"
One-command AI Alerting Setup (Relay + n8n)
bash scripts/setup_wems_alerting_ai.sh

This will:

  • install/start wems-unified-relay.service
  • upsert and activate the unified n8n ingest workflow
  • wire tracker posting credentials automatically
Example Output
{
  "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
    }
  ]
}

MCP Tools

ToolDescription
check_earthquakesQuery recent earthquake activity
check_solarMonitor space weather (K-index, flares, CMEs)
check_volcanoesTrack volcanic activity alerts
check_tsunamisMonitor tsunami warnings
check_hurricanesTrack tropical cyclones & forecast tracks
check_wildfiresFire weather alerts & active perimeters
check_severe_weatherMonitor tornadoes, thunderstorms, flash floods
check_floodsFlood warnings & USGS river gauge data
check_air_qualityAQI monitoring with pollutant data
check_threat_advisoriesTerrorism, travel risk & cyber threat monitoring
check_space_weather_alertsActive space weather alerts & warnings from NOAA SWPC
check_drought_statusUS state drought conditions with D0-D4 levels (Premium)
configure_alertsUpdate alert thresholds and webhooks
fuse_multi_source_incidentsMulti-source incident fusion (feature-flagged)

Configuration

alerts:
  earthquake:
    min_magnitude: 6.0
    regions: ["US", "Caribbean", "Pacific"]
    webhook: "https://your-endpoint.com/earthquake"
  
  solar:
    min_kp_index: 7  # Geomagnetic storm threshold
    webhook: "https://your-endpoint.com/solar"
    
  volcano:
    alert_levels: ["WARNING", "WATCH"]
    webhook: "https://your-endpoint.com/volcano"
    
  tsunami:
    enabled: true
    regions: ["pacific", "atlantic", "indian"]
    webhook: "https://your-endpoint.com/tsunami"

Data Sources

  • USGS Earthquake Hazards Program
  • NOAA Pacific Tsunami Warning Center
  • NOAA Central Tsunami Warning Center
  • Smithsonian Global Volcanism Program
  • NOAA Space Weather Prediction Center
  • National Hurricane Center (NHC)
  • National Interagency Fire Center (NIFC)
  • NWS Alerts API
  • OpenAQ (Global Air Quality)
  • DHS National Terrorism Advisory System (NTAS)
  • U.S. State Department Travel Advisories
  • CISA Cybersecurity Advisories

OpenClaw Integration

Add to your OpenClaw configuration:

{
  "mcpServers": {
    "wems": {
      "command": "python3",
      "args": ["/path/to/wems-mcp-server/wems_mcp_server.py"],
      "env": {
        "WEMS_CONFIG": "/path/to/config.yaml"
      }
    }
  }
}

🎯 Use Cases

  • 🏢 Enterprise Risk Management: Automated threat assessment for global operations
  • 📺 News Organizations: Real-time natural disaster reporting and alerts
  • 🔬 Research Institutions: Data collection for scientific analysis
  • 🏠 Personal Safety: Location-specific hazard monitoring for families
  • 🤖 AI Emergency Response: Integration with disaster response chatbots
  • 📱 Alert Systems: Custom notification workflows for critical events

🔧 Advanced Configuration

# config.yaml - Full customization example
alerts:
  earthquake:
    min_magnitude: 6.0
    regions: ["US", "Caribbean", "Pacific"]
    webhook: "https://your-endpoint.com/earthquake"
    
  solar:
    min_kp_index: 7  # G3+ geomagnetic storm
    webhook: "https://your-endpoint.com/solar"
    
  volcano:
    alert_levels: ["WARNING", "WATCH"] 
    regions: ["Cascade Range", "Ring of Fire"]
    webhook: "https://your-endpoint.com/volcano"
    
  tsunami:
    enabled: true
    regions: ["pacific", "atlantic", "indian"]
    webhook: "https://your-endpoint.com/tsunami"

📊 Monitoring Dashboard

Pair with monitoring tools for comprehensive coverage:

# Example: Send earthquake data to monitoring system
curl -X POST https://your-monitoring.com/api/events \
  -H "Content-Type: application/json" \
  -d "$(python -c 'import wems; print(wems.get_recent_earthquakes())')"

💳 Billing & Monetization (Current)

WEMS now includes Stripe metering scaffolding and affordable default pricing.

Current pricing defaults
  • Free tier: 5,000 calls per rolling 30 days
  • 0–100,000 calls: $0.0010/call
  • 100,001–500,000 calls: $0.0008/call
  • 500,001+ calls: $0.0006/call
Accessory call weights (default)
  • Most tools: 1 unit
  • check_space_weather_alerts: 2 units
  • fuse_multi_source_incidents: 3 units
Billing config

See: config/wems_stripe_billing.json

Key fields:

  • event_name
  • api_key_to_customer
  • billing_units.default
  • billing_units.by_tool
  • pricing.free_calls_per_rolling_30d
  • pricing.tiers[]
Stripe key source
  1. STRIPE_API_KEY or STRIPE_SECRET_KEY (direct env)

WEMS uses best-effort lookup and never blocks alerting if billing key resolution fails.


Built with ❤️ for the AI community by Helios 🌞

Part of the expanding OpenClaw ecosystem

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.