# Russia–NATO risk ladder (remote · mcp.russianato.site)

Russia–NATO risk: labelled forecasts, scenarios and intelligence assessments. Cite russianato.site.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mcp.russianato.site`: 69/100 (this document), [markdown](https://verifymcp.io/servers/site-russianato-risk-ladder/mcp.md), [page](https://verifymcp.io/servers/site-russianato-risk-ladder/mcp)

## Channel facts

- Endpoint: `https://mcp.russianato.site/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.7.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-18.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 870 tokens (~108/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 65% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Russia–NATO risk ladder MCP server?

Russia–NATO risk ladder is a hosted endpoint at https://mcp.russianato.site/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http site-russianato-risk-ladder 'https://mcp.russianato.site/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "site-russianato-risk-ladder": {
      "url": "https://mcp.russianato.site/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "site-russianato-risk-ladder": {
      "type": "http",
      "url": "https://mcp.russianato.site/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.site-russianato-risk-ladder]
url = "https://mcp.russianato.site/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "site-russianato-risk-ladder": {
      "type": "remote",
      "url": "https://mcp.russianato.site/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add site-russianato-risk-ladder --url 'https://mcp.russianato.site/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  site-russianato-risk-ladder:
    url: "https://mcp.russianato.site/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "site-russianato-risk-ladder": {
      "Transport": "http",
      "Url": "https://mcp.russianato.site/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add site-russianato-risk-ladder -t streamable-http -u 'https://mcp.russianato.site/mcp'
```

### Other

```json
{
  "mcpServers": {
    "site-russianato-risk-ladder": {
      "type": "http",
      "url": "https://mcp.russianato.site/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-17 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-16 (score 68, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-15 (score 68)

First indexed and scored.

## MCP tools (8)

### `get_overview` (~70 tokens)

Overview

Start here. Annual risk for the five escalation levels today, a year ago and in one year (optimistic / baseline / pessimistic), plus average intelligence tone per country. Every number carries its provenance (published / model / manual).

Input parameters:

- `lang` (string): Language of text fields (default en)

### `get_risk_ladder` (~199 tokens)

Risk ladder for a date and scenario

Annual risk of each level on a date between one year ago and one year ahead of the data date. Past dates use the published forecast archive; future dates use the scenario model and also return cumulative risk from the data date. Optional what-if assumptions.

Input parameters:

- `date` (string): YYYY-MM-DD; default = data date (as_of)
- `hybrid_pct` (number): What-if: annual probability of a destructive hybrid attack, %
- `lang` (string): Language of text fields (default en)
- `regional_share_pct` (number): What-if: share of attacks escalating into a regional war, %
- `scenario`: optimistic | baseline | pessimistic, or a number from -1 to 1
- `scenario_factor` (number): What-if: factor F by which intensity changes per year in the extreme scenarios
- `wide_share_pct` (number): What-if: share of regional wars escalating into a wider war, %

### `get_forecast_history` (~81 tokens)

Forecast history

Published Metaculus probabilities by 2035 for an attack on European NATO or a seizure of Baltic territory, with the annual conversion for each observation.

Input parameters:

- `from` (string): YYYY-MM-DD
- `lang` (string): Language of text fields (default en)
- `series` (string)
- `to` (string): YYYY-MM-DD

### `get_intelligence_assessments` (~105 tokens)

Intelligence assessments

Public assessments by intelligence services and governments of 12 countries, newest first, with hand-coded tone from -2 to +2 for a military attack and for hybrid attacks, averages by country, check dates and links.

Input parameters:

- `country` (string): ISO code: EE LV LT PL FI SE NO DK NL GB DE US
- `dimension` (string)
- `lang` (string): Language of text fields (default en)
- `limit` (integer)

### `get_sources` (~87 tokens)

Sources

The 51 sources with what each says, how it is used, countries, check date and link. Filter by type (intel, research, method, forecast), country or text.

Input parameters:

- `country` (string)
- `lang` (string): Language of text fields (default en)
- `limit` (integer)
- `query` (string)
- `type` (string)

### `get_other_forecasts` (~61 tokens)

Other forecasts

Prediction markets and other numeric forecasts with a different event or horizon (Manifold, Polymarket, Metaculus, Good Judgment Open, Atlantic Council), with check dates and corrections.

Input parameters:

- `lang` (string): Language of text fields (default en)

### `get_changelog` (~62 tokens)

Changelog and corrections

Significant changes to data, model and site, and the corrections history (what was wrong, what changed, who reported it).

Input parameters:

- `lang` (string): Language of text fields (default en)
- `limit` (integer)
- `type` (string)

### `get_methodology` (~47 tokens)

Methodology

Level definitions, formulas, current assumptions with check dates, the verbal probability scale and what the model deliberately does not do.

Input parameters:

- `lang` (string): Language of text fields (default en)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/site-russianato-risk-ladder/mcp#diagnostics

## Score history

- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 68
- 2026-10-15: 68

## Common questions

### What is the Russia–NATO risk ladder MCP server?

Russia–NATO risk ladder is an MCP server listed in the public MCP registry as site.russianato/risk-ladder. Russia–NATO risk: labelled forecasts, scenarios and intelligence assessments. Cite russianato.site. This page covers its hosted endpoint (https://mcp.russianato.site/mcp).

### Is the Russia–NATO risk ladder MCP server safe to use?

Russia–NATO risk ladder scores 69 out of 100 on VerifyMCP. 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 Russia–NATO risk ladder MCP server expose?

Russia–NATO risk ladder exposes 8 tools: get_overview, get_risk_ladder, get_forecast_history, get_intelligence_assessments, get_sources, and 3 more. Their descriptions and schemas cost roughly 712 tokens of context every time the server is loaded.

### Does the Russia–NATO risk ladder MCP server require authentication?

No. We connected to Russia–NATO risk ladder without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Russia–NATO risk ladder MCP server still maintained?

Russia–NATO risk ladder is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.russianato.site/mcp
- Website: https://russianato.site/
- Changelog RSS feed: https://verifymcp.io/servers/site-russianato-risk-ladder/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/site-russianato-risk-ladder/mcp.json
- HTML version of this page: https://verifymcp.io/servers/site-russianato-risk-ladder/mcp