SuperAPI AI Directory

war-dashboard-data

Daily geopolitical risk probabilities (escalation, ceasefire, regime change) for conflicts like Russia-Ukraine and China-Taiwan, plus chokepoint vessel data.

Open website

About this tool

war-dashboard-data is a geopolitical conflict risk data project for AI agents, providing structured risk data accessible through an MCP (Model Context Protocol) server and REST API. The project is built by Futuristic Risk Intelligence and is positioned as a "future risk intelligence" data source for AI agents.

[Purpose and Coverage] This data source is mainly used to provide AI agents with risk probability information on geopolitical conflicts. It covers 6 conflict regions: Russia-Ukraine, Iran-Israel/US, Israel-Palestine, China-Taiwan, India-Pakistan, and US-Latin America. Each conflict includes multiple event types with a clear risk direction, such as escalation, ceasefire, regime change, and so on. The specific list of event types is summarized in the official text only as "5 event types with clear risk direction," and not all names are listed individually.

[Main Data Content] The project includes two main data files, conflicts.json and political_events.json. political_events.json provides probability estimates for political, economic, and natural disaster events. Both files include an importance field, used to mark the importance of an event:

  • high: editorial recommendation level. Active conflicts, high-probability events, or events that have recently undergone significant changes. Consistent with the display filter of the daily intelligence report.
  • low: included for data completeness. Low probability, no active events, or regions that are not the current focus. Agents can still use it for comprehensive monitoring.

The chokepoint vessel data originally included in the design is currently paused. The official explanation states that free AIS data (45-second snapshots) produces sporadic zero-vessel readings in busy straits, which may mislead agents into inferring a blockade. The relevant interface currently returns {"status": "unavailable", "zones": []}, and will be restored after a reliable AIS data source is found.

[How to Use]

  1. MCP server: Add the configuration to claude_desktop_config.json (the official text does not provide a complete configuration example), then you can ask Claude directly, for example: "What's the current escalation risk for Russia-Ukraine?"
  2. Direct REST API: Obtain data through the API. For detailed interface documentation, see futuristicrisks.com.

[Technical Details]

  • Zero dependencies: The MCP server uses only the Python standard library and is compatible with Python 3.9+.
  • Data source: Proprietary multi-source modeling.
  • Update frequency: Daily updates.
  • Delay: Public data has about a 24-hour delay.
  • Licensing: Free for non-commercial use; commercial licensing requires contact.

[Applicable Scenarios] The official list includes the following typical uses:

  • Trading agents: Adjust cryptocurrency/commodity positions based on changes in geopolitical risk.
  • Risk management: Monitor conflict escalation probabilities for portfolio hedging.
  • DeFi protocols: Set dynamic collateral ratios based on geopolitical risk.
  • Research agents: Track risk probability trends across 6 conflict regions.
  • News agents: Obtain structured risk data instead of parsing news headlines.

[Website and Research] futuristicrisks.com provides a real-time risk dashboard, cascading impact analysis, daily verified intelligence, and API documentation. The research articles listed officially include: 2026 Global Geopolitical Risk Panorama Analysis, Analysis of the Impact of the Iran Situation on Oil Prices and Supply Chains, and Risk Assessment of the Impact of a Taiwan Strait Conflict on the Global Semiconductor Supply Chain.

[Limitations and Notes]

  • Public data has about a 24-hour delay and is not suitable for scenarios requiring real-time data.
  • Strait vessel AIS data is currently unavailable, and the interface returns an unavailable status.
  • Commercial use requires authorization.
  • The official text does not provide a complete code example for MCP configuration, endpoint details for the REST API, or specific pricing information.