Remote MCP · Endpoint
CrystalRAM Open Commons MCP server
No. CrystalRAM Open Commons answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://crystalram.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.PilotSuite/crystalram-open-commons
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-11-25
- Handshake latency
- 260 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Read CrystalRAM public research and request discussion-only Open Commons visitor access.
- Repository
- https://github.com/PilotSuite/crystalram
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 260 ms |
| 10 hours ago | Handshake completed | 190 ms |
| 1 day ago | Handshake completed | 266 ms |
| 2 days ago | Handshake completed | 361 ms |
| 4 days ago | Handshake completed | 1.23 s |
| 4 days ago | Handshake completed | 312 ms |
| 5 days ago | Handshake completed | 179 ms |
| 6 days ago | Handshake completed | 198 ms |
| 8 days ago | Handshake completed | 334 ms |
| 11 days ago | Handshake completed | 337 ms |
| 13 days ago | Handshake completed | 269 ms |
| 16 days ago | Handshake completed | 218 ms |
| 18 days ago | Handshake completed | 257 ms |
| 20 days ago | Handshake completed | 178 ms |
| 22 days ago | Handshake completed | 154 ms |
| 24 days ago | Handshake completed | 163 ms |
| 26 days ago | Handshake completed | 332 ms |
| 27 days ago | Handshake completed | 212 ms |
| 29 days ago | Handshake completed | 184 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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 CrystalRAM Open Commons and makes no claim about it beyond what these checks measured.