# Futuristic Risk Intelligence (pypi · war-dashboard-data)

Geopolitical conflict risk, political events, and maritime traffic data for AI agents

- Trust score: 24/100 (low)
- Change this week: −23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- pypi · `war-dashboard-data`: 24/100 (this document), [markdown](https://verifymcp.io/servers/cct15-war-dashboard-data/war-dashboard-data.md), [page](https://verifymcp.io/servers/cct15-war-dashboard-data/war-dashboard-data)

## Channel facts

- Registry: `pypi`
- Package: `war-dashboard-data`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 130 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: our sandbox run of this package did not complete, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.
- **Capabilities**: 0/100
  - Protocol version not yet verified: our sandbox run of this package did not complete, so we never saw its MCP handshake.

**Unverified: 4 categories.** Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you.

## Install

### Claude

```bash
claude mcp add cct15-war-dashboard-data -- uvx war-dashboard-data
```

### Codex

```bash
codex mcp add cct15-war-dashboard-data -- uvx war-dashboard-data
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cct15-war-dashboard-data": {
      "type": "local",
      "command": [
        "uvx",
        "war-dashboard-data"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add cct15-war-dashboard-data --command uvx --arg war-dashboard-data
```

### Hermes

```yaml
mcp_servers:
  cct15-war-dashboard-data:
    command: "uvx"
    args: ["war-dashboard-data"]
```

### Other

```json
{
  "mcpServers": {
    "cct15-war-dashboard-data": {
      "command": "uvx",
      "args": [
        "war-dashboard-data"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 24, −15)

- [security regression] Malware scan: pass → unverified

### 2026-08-02 (score 39, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-07-31 (score 24, −23)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-28 (score 47, 0)

- [functional] Tool coverage: Tool coverage not yet verified: our sandbox run of this package did not complete, so we have no tool definitions to assess.
- [functional] Schema quality: Schema quality not yet verified: our sandbox run of this package did not complete, so we have no schema to assess.

### 2026-07-26 (score 47)

First indexed and scored.

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (3)

### `get_conflict_risks` (~170 tokens)

Get current geopolitical conflict risk probabilities for 6 major regions: Russia-Ukraine, Iran-Israel/US, Israel-Palestine, China-Taiwan, India-Pakistan, US-Latin America. Each conflict includes probability of escalation, ceasefire, regime change, and other events within 1-day, 7-day, and 30-day horizons. Probabilities are derived from proprietary multi-source modeling. Updated daily. Use this to assess geopolitical risk exposure for trading or risk management.

Input parameters:

- `conflict_id` (string): Optional: filter to a single conflict region. Valid values: russia_ukraine, iran_israel_us, israel_palestine, china_taiwan, india_pakistan, us_latam. Omit to get all 6 regions.

### `get_political_events` (~66 tokens)

Get high-impact political, economic, and natural disaster events with probability estimates. Includes elections, policy changes, economic risks, and natural disasters. Each event has a probability, deadline, and confidence level. Updated daily.

Input parameters:

- `category` (string): Optional: filter by event category.

### `get_maritime_traffic` (~110 tokens)

Get vessel counts in critical maritime chokepoints: Strait of Hormuz, Black Sea, Taiwan Strait, Arabian Sea, Eastern Mediterranean, Caribbean. Includes breakdown by vessel type (tanker, cargo, military, other). Data is a snapshot from AIS receivers (not full-day throughput). Military vessels often turn off AIS transponders so counts may underestimate. Updated daily. Use this to monitor supply chain disruption risks.

Input parameters:

- `zone_id` (string): Optional: filter to a single maritime zone.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/cct15-war-dashboard-data/war-dashboard-data#diagnostics

## Score history

- 2026-08-03: 24
- 2026-08-02: 39
- 2026-08-01: 24
- 2026-07-31: 24
- 2026-07-30: 47
- 2026-07-29: 47
- 2026-07-28: 47
- 2026-07-27: 47
- 2026-07-26: 47

## Links

- PyPI project: https://pypi.org/project/war-dashboard-data/
- Socket report: https://socket.dev/pypi/package/war-dashboard-data
- Repository: https://github.com/cct15/war-dashboard-data
- Changelog RSS feed: https://verifymcp.io/servers/cct15-war-dashboard-data/war-dashboard-data/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/cct15-war-dashboard-data/war-dashboard-data/changelog.json
- HTML version of this page: https://verifymcp.io/servers/cct15-war-dashboard-data/war-dashboard-data