Remote MCP · Endpoint

STRIDE MCP server

No. STRIDE answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://stride.simmons-simmons.com/mcp/

The last check completed an MCP handshake.

Registry name
info.stride/stride
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
558 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Digital-regulation tracking and analysis across jurisdictions; STRIDE access is required.
Listing
From the official MCP registry (active).
Recent checks of STRIDE
CheckedResultHandshake
9 hours agoHandshake completed558 ms
4 days agoHandshake completed404 ms
14 days agoHandshake completed365 ms
15 days agoHandshake completed380 ms
15 days agoHandshake completed358 ms
17 days agoHandshake completed361 ms
18 days agoHandshake completed406 ms
19 days agoHandshake completed371 ms
20 days agoHandshake completed371 ms
21 days agoHandshake completed388 ms
23 days agoHandshake completed362 ms
26 days agoHandshake completed375 ms
28 days agoHandshake completed546 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 STRIDE and makes no claim about it beyond what these checks measured.