Remote MCP · Endpoint

MCP Operation Risk MCP server

No. MCP Operation Risk answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://87-106-119-237.sslip.io/mcp-operation-risk/mcp

The last check completed an MCP handshake.

Registry name
io.github.dnsreicht/mcp-operation-risk
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
305 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Operation-level risk guidance for consolidated MCP tools, including schema drift and retry signals.
Listing
From the official MCP registry (active).
Recent checks of MCP Operation Risk
CheckedResultHandshake
42 minutes agoHandshake completed305 ms
3 days agoHandshake completed313 ms
13 days agoHandshake completed320 ms
13 days agoHandshake completed310 ms
15 days agoHandshake completed342 ms
15 days agoHandshake completed312 ms
17 days agoHandshake completed309 ms
18 days agoHandshake completed311 ms
18 days agoHandshake completed316 ms
20 days agoHandshake completed304 ms
22 days agoHandshake completed648 ms
25 days agoHandshake completed402 ms
27 days agoHandshake completed397 ms
30 days agoHandshake completed306 ms

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

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 MCP Operation Risk and makes no claim about it beyond what these checks measured.