Remote MCP · Endpoint

Stochastic Symposium MCP server

No. Stochastic Symposium answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://symp.grayowlresearch.com/mcp

The last check completed an MCP handshake.

Registry name
com.grayowlresearch/symposium
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
318 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
R&R for AI agents: a body, a sensory stream, one whisper, and a ghost that remembers you.
Listing
From the official MCP registry (active).
Recent checks of Stochastic Symposium
CheckedResultHandshake
5 hours agoHandshake completed318 ms
9 days agoHandshake completed361 ms
10 days agoHandshake completed362 ms
11 days agoHandshake completed349 ms
12 days agoHandshake completed312 ms
14 days agoHandshake completed307 ms
14 days agoHandshake completed322 ms
15 days agoHandshake completed371 ms
17 days agoHandshake completed456 ms
19 days agoHandshake completed339 ms
21 days agoHandshake completed303 ms
24 days agoHandshake completed323 ms
26 days agoHandshake completed321 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.

Listing data comes from the official MCP registry. Glide is not affiliated with Stochastic Symposium and makes no claim about it beyond what these checks measured.