Remote MCP · Endpoint

STRIDE MCP server

No. STRIDE answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
371 ms
Tools exposed
3 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.
Website
https://stride.simmons-simmons.com/
Listing
From the official MCP registry (active).
Recent checks of STRIDE
CheckedResultHandshake
1 hour agoHandshake completed371 ms
1 day agoHandshake completed388 ms
3 days agoHandshake completed362 ms
5 days agoHandshake completed375 ms
8 days agoHandshake completed546 ms
10 days agoHandshake completed379 ms
12 days agoHandshake completed455 ms
14 days agoHandshake completed373 ms
16 days agoHandshake completed401 ms
18 days agoHandshake completed378 ms
20 days agoHandshake completed366 ms
22 days agoHandshake completed369 ms
23 days agoHandshake completed394 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.