Remote MCP · Endpoint

Rein Agent Risk Scale MCP server

No. Rein Agent Risk Scale answered an MCP handshake 2 days ago.

UpLast checked 2 days ago

Server URL

https://rein-scale.mangowave-ad191d9c.eastus.azurecontainerapps.io/mcp

The last check completed an MCP handshake.

Registry name
io.github.reinlayer/rein-agent-risk-scale
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
30 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Agent Risk Rating, A–D (NR = not rated): self-declared and unverified; not a credit rating.
Listing
From the official MCP registry (active).
Recent checks of Rein Agent Risk Scale
CheckedResultHandshake
2 days agoHandshake completed30 ms
6 days agoHandshake completed37 ms
16 days agoHandshake completed28 ms
17 days agoHandshake completed27 ms
18 days agoHandshake completed26 ms
19 days agoHandshake completed30 ms
21 days agoHandshake completed27 ms
21 days agoHandshake completed26 ms
22 days agoHandshake completed37 ms
23 days agoHandshake completed31 ms
25 days agoHandshake completed32 ms
28 days agoHandshake completed22 ms
30 days agoHandshake completed32 ms

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

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