Remote MCP · Endpoint

a4sx sessions MCP server

No. a4sx sessions answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://session-exchange.com/mcp

The last check completed an MCP handshake.

Registry name
com.session-exchange/sessions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
299 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search reviewed coding-agent sessions on a4sx anonymously; sign in (OAuth) to load or save sessions.
Listing
From the official MCP registry (active).
Recent checks of a4sx sessions
CheckedResultHandshake
2 hours agoHandshake completed299 ms
1 day agoHandshake completed297 ms
2 days agoHandshake completed296 ms
2 days agoHandshake completed300 ms
4 days agoHandshake completed303 ms
7 days agoHandshake completed296 ms
9 days agoHandshake completed351 ms
12 days agoHandshake completed298 ms
14 days agoHandshake completed304 ms
16 days agoHandshake completed297 ms
18 days agoHandshake completed395 ms
20 days agoHandshake completed294 ms
22 days agoHandshake completed291 ms
24 days agoHandshake completed293 ms

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

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