Remote MCP · Endpoint
CleanSlice MCP server
No. CleanSlice answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.cleanslice.org/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.CleanSlice/mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 311 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 94.4% from 18 checks
- Described by its publisher as
- Architecture docs and patterns for NestJS + Nuxt full-stack apps
- Website
- https://cleanslice.dev/
- Repository
- https://github.com/CleanSlice/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 311 ms |
| 1 day ago | Handshake completed | 377 ms |
| 2 days ago | Handshake completed | 139 ms |
| 3 days ago | Handshake completed | 343 ms |
| 4 days ago | Handshake completed | 324 ms |
| 5 days ago | Handshake completed | 348 ms |
| 6 days ago | Handshake completed | 315 ms |
| 9 days ago | Handshake completed | 159 ms |
| 11 days ago | Handshake completed | 308 ms |
| 14 days ago | Handshake completed | 347 ms |
| 16 days ago | Failed - the request timed out | — |
| 18 days ago | Handshake completed | 346 ms |
| 20 days ago | Handshake completed | 404 ms |
| 22 days ago | Handshake completed | 170 ms |
| 24 days ago | Handshake completed | 142 ms |
| 26 days ago | Handshake completed | 149 ms |
| 27 days ago | Handshake completed | 350 ms |
| 29 days ago | Handshake completed | 333 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 28 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 CleanSlice and makes no claim about it beyond what these checks measured.