Futuristic Risk Intelligence
PYPI · WAR-DASHBOARD-DATA · SCANNED SEP 20
Geopolitical conflict risk, political events, and maritime traffic data for AI agents
Available components
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 178 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 346 tokens (~115/item across 3 items; 3 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Futuristic Risk Intelligence MCP server?
Futuristic Risk Intelligence runs locally as a PyPI package, launched with uvx war-dashboard-data. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · war-dashboard-data
claude mcp add cct15-war-dashboard-data -- uvx war-dashboard-data
{
"mcpServers": {
"cct15-war-dashboard-data": {
"command": "uvx",
"args": [
"war-dashboard-data"
]
}
}
} {
"servers": {
"cct15-war-dashboard-data": {
"command": "uvx",
"args": [
"war-dashboard-data"
]
}
}
} codex mcp add cct15-war-dashboard-data -- uvx war-dashboard-data
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cct15-war-dashboard-data": {
"type": "local",
"command": [
"uvx",
"war-dashboard-data"
],
"enabled": true
}
}
} openclaw mcp add cct15-war-dashboard-data --command uvx --arg war-dashboard-data
mcp_servers:
cct15-war-dashboard-data:
command: "uvx"
args: ["war-dashboard-data"] {
"McpServers": {
"cct15-war-dashboard-data": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"war-dashboard-data"
]
}
}
} assistant mcp add cct15-war-dashboard-data -t stdio -c uvx -a war-dashboard-data
{
"mcpServers": {
"cct15-war-dashboard-data": {
"command": "uvx",
"args": [
"war-dashboard-data"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/war-dashboard-data@1.0.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_conflict_risks ~170
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_maritime_traffic ~110
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.
| Name | Type | Req | Description |
|---|---|---|---|
| zone_id | string | – | Optional: filter to a single maritime zone. |
No output schema declared.
No examples provided.
get_political_events ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional: filter by event category. |
No output schema declared.
No examples provided.
What is the Futuristic Risk Intelligence MCP server?
Futuristic Risk Intelligence is an MCP server listed in the public MCP registry as io.github.cct15/war-dashboard-data. Geopolitical conflict risk, political events, and maritime traffic data for AI agents. This page covers its PyPI package (war-dashboard-data).
Is the Futuristic Risk Intelligence MCP server safe to use?
Futuristic Risk Intelligence scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Futuristic Risk Intelligence MCP server expose?
Futuristic Risk Intelligence exposes 3 tools: get_conflict_risks, get_political_events, get_maritime_traffic. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.
Is the Futuristic Risk Intelligence MCP server still maintained?
Futuristic Risk Intelligence is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Futuristic Risk Intelligence MCP server under?
Futuristic Risk Intelligence declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.