Skill Detail

Query real-time global intelligence through Worldmonitor MCP

Give MCP-capable agents a live global-intelligence surface for country briefs, risk scores, conflict, cyber, market, weather, and infrastructure monitoring.

Monitoring & AlertsMCP
Monitoring & Alerts MCP Security Reviewed
โญ 61.4k GitHub stars โฌ‡ 602/wk npm
INSTALL WITH ANY AGENT
npx skills add agentskillexchange/skills --skill query-real-time-global-intelligence-through-worldmonitor-mcp Copy
Works best when you want a reusable capability, not another fragile one-off prompt.
At a glance
Tools required
MCP-compatible client, Worldmonitor API key for authenticated tool calls, Node.js/npm for CLI usage
Install & setup
For MCP, configure the Streamable HTTP endpoint at `https://worldmonitor.app/mcp` and provide `X-WorldMonitor-Key` for authenticated tool calls. For CLI use, run `npx worldmonitor tools` to list available tools or install globally with `npm install -g worldmonitor`.
Author
koala73
Publisher
Individual
Last updated
Jul 6, 2026
Quick brief

Use Worldmonitor when an agent needs current situational intelligence instead of a static research prompt or manual dashboard browsing. The operator connects the hosted MCP endpoint or CLI, lists the available monitoring tools, then asks the agent to retrieve country briefs, risk scores, conflict, cyber, market, weather, or infrastructure signals for a bounded investigation. The scope is live intelligence lookup and monitoring through a documented MCP/CLI surface; it is not a generic dashboard listing or a replacement for human source judgment.

How it works

What this skill actually does

Inputs and prerequisites: MCP-compatible client, Worldmonitor API key for authenticated tool calls, Node.js/npm for CLI usage.

Setup notes: For MCP, configure the Streamable HTTP endpoint at https://worldmonitor.app/mcp and provide X-WorldMonitor-Key for authenticated tool calls. For CLI use, run npx worldmonitor tools to list available tools or install globally with npm install -g worldmonitor .

Source and verification boundary: use https://www.worldmonitor.app/docs/getting-started as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.

Framework fit: publish this as a MCP workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.