CAP Alert Extractor (OASIS CAP 1.2 emergency alerts)
Pricing
from $0.35 / 1,000 alert records
Point at ANY CAP alerting authority (US NWS, UN GDACS, Canada NAAD, PH PAGASA, NZ MetService + more in the WMO Register) and extract OASIS CAP 1.2 alerts as flat rows. Auto-decodes GeoJSON, inline CAP-XML feeds and Atom/RSS-linked CAP docs. One row per alert x info-language x area, with geometry.
You can access the CAP Alert Extractor (OASIS CAP 1.2 emergency alerts) programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in Integrations settings in Apify Console.
{ "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=datamule/cap-alert-extractor", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}Get a ready-to-use configuration for your MCP client with the CAP Alert Extractor — OASIS CAP 1.2 Emergency Alerts Actor preconfigured at mcp.apify.com?tools=datamule/cap-alert-extractor .
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.