Russia–NATO risk ladder
REMOTE · MCP.RUSSIANATO.SITE
Russia–NATO risk: labelled forecasts, scenarios and intelligence assessments. Cite russianato.site.
Available components
Last scanned (14 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 18 Oct 2026.
Category Security
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 870 tokens (~108/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 65% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 17 Oct 26 +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.
- 16 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 15 Oct 26 68
First indexed and scored.
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 18 Oct 2026 · Probed https://mcp.russianato.site/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=russianato.site | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 13 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8d60bd2dc997f6f90ed8c51693b7b281 |
| SANs: russianato.site, mcp.russianato.site, *.mcp.russianato.site | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.russianato.site. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| site. | present | 31826 | 13 | Verified |
| russianato.site. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.russianato.site/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.russianato.site/mcp | HTTPS enforced | 301 | https://mcp.russianato.site/mcp |
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_changelog Changelog and corrections ~62
Significant changes to data, model and site, and the corrections history (what was wrong, what changed, who reported it).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of text fields (default en) |
| limit | integer | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
get_forecast_history Forecast history ~81
Published Metaculus probabilities by 2035 for an attack on European NATO or a seizure of Baltic territory, with the annual conversion for each observation.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | YYYY-MM-DD |
| lang | string | – | Language of text fields (default en) |
| series | string | – | – |
| to | string | – | YYYY-MM-DD |
No output schema declared.
No examples provided.
get_intelligence_assessments Intelligence assessments ~105
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – |
No output schema declared.
No examples provided.
get_methodology Methodology ~47
Level definitions, formulas, current assumptions with check dates, the verbal probability scale and what the model deliberately does not do.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of text fields (default en) |
No output schema declared.
No examples provided.
get_other_forecasts Other forecasts ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of text fields (default en) |
No output schema declared.
No examples provided.
get_overview Overview ~70
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).
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | Language of text fields (default en) |
No output schema declared.
No examples provided.
get_risk_ladder Risk ladder for a date and scenario ~199
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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, % |
No output schema declared.
No examples provided.
get_sources Sources ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | – |
| lang | string | – | Language of text fields (default en) |
| limit | integer | – | – |
| query | string | – | – |
| type | string | – | – |
No output schema declared.
No examples provided.
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.
remote · mcp.russianato.site
claude mcp add --transport http site-russianato-risk-ladder 'https://mcp.russianato.site/mcp'
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.