Remote MCP · Endpoint
io.github.cyanheads/stackexchange-mcp-server MCP server
No. io.github.cyanheads/stackexchange-mcp-server answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://stackexchange.caseyjhand.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.cyanheads/stackexchange-mcp-server
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 241 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Search Stack Exchange questions, fetch Q&A threads as markdown, look up tag FAQs and user profiles.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 241 ms |
| 1 day ago | Handshake completed | 774 ms |
| 2 days ago | Handshake completed | 378 ms |
| 3 days ago | Handshake completed | 271 ms |
| 4 days ago | Handshake completed | 259 ms |
| 5 days ago | Handshake completed | 256 ms |
| 6 days ago | Handshake completed | 294 ms |
| 9 days ago | Handshake completed | 281 ms |
| 11 days ago | Handshake completed | 263 ms |
| 14 days ago | Handshake completed | 281 ms |
| 16 days ago | Handshake completed | 507 ms |
| 18 days ago | Handshake completed | 190 ms |
| 20 days ago | Handshake completed | 202 ms |
| 22 days ago | Handshake completed | 101 ms |
| 24 days ago | Handshake completed | 92 ms |
| 26 days ago | Handshake completed | 103 ms |
| 27 days ago | Handshake completed | 100 ms |
| 29 days ago | Handshake completed | 635 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 io.github.cyanheads/stackexchange-mcp-server and makes no claim about it beyond what these checks measured.