Remote MCP · Endpoint

Russia–NATO risk ladder MCP server

No. Russia–NATO risk ladder answered an MCP handshake 15 minutes ago.

UpLast checked 15 minutes ago

Server URL

https://mcp.russianato.site/mcp

The last check completed an MCP handshake.

Registry name
site.russianato/risk-ladder
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
89 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Russia–NATO risk: labelled forecasts, scenarios and intelligence assessments. Cite russianato.site.
Listing
From the official MCP registry (active).
Recent checks of Russia–NATO risk ladder
CheckedResultHandshake
15 minutes agoHandshake completed89 ms
9 days agoHandshake completed57 ms
9 days agoHandshake completed57 ms
11 days agoHandshake completed108 ms
12 days agoHandshake completed89 ms
13 days agoHandshake completed53 ms
14 days agoHandshake completed194 ms
14 days agoHandshake completed73 ms
16 days agoHandshake completed365 ms
19 days agoHandshake completed84 ms
21 days agoHandshake completed55 ms
24 days agoHandshake completed98 ms
26 days agoHandshake completed93 ms
28 days agoHandshake completed65 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Russia–NATO risk ladder and makes no claim about it beyond what these checks measured.