Futuristic Risk Intelligence

Created By
cct152 months ago
Daily-updated geopolitical risk data for AI agents. Covers 6 major conflict regions (Russia-Ukraine, Iran-Israel, China-Taiwan, etc.) with escalation/ceasefire probabilities, political event tracking, and maritime chokepoint vessel counts. Zero dependencies, Python 3.9+.
Overview

Tools

ToolDescription
get_conflict_risksRisk probabilities for 6 conflict regions with 1d/7d/30d horizons
get_political_eventsHigh-impact political, economic, and natural disaster events
get_maritime_trafficVessel counts in critical maritime chokepoints

Install

pip install war-dashboard-data

Use Cases

  • Trading agents: Adjust positions based on geopolitical risk changes
  • Risk management: Monitor escalation probabilities for portfolio hedging
  • DeFi protocols: Dynamic collateral ratios based on conflict risk
  • Research agents: Track probability trends across conflict regions

Data Coverage

  • 6 conflict regions: Russia-Ukraine, Iran-Israel/US, Israel-Palestine, China-Taiwan, India-Pakistan, US-Latin America
  • 5 event types: escalation, ceasefire, ceasefire_cancel, regime_change, diplomatic
  • 6 maritime zones: Strait of Hormuz, Black Sea, Taiwan Strait, Arabian Sea, Eastern Mediterranean, Caribbean
  • Update frequency: Daily

Server Config

{
  "mcpServers": {
    "futuristic-risk": {
      "command": "war-dashboard-data"
    }
  }
}
Project Info
Created At
2 months ago
Updated At
2 months ago
Author Name
cct15
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago