Remote MCP · Endpoint

CleanSlice MCP server

No. CleanSlice answered an MCP handshake 2 hours ago.

UpLast checked 2 hours 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
404 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 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).
Recent checks of CleanSlice
CheckedResultHandshake
2 hours agoHandshake completed404 ms
2 days agoHandshake completed170 ms
4 days agoHandshake completed142 ms
5 days agoHandshake completed149 ms
7 days agoHandshake completed350 ms
8 days agoHandshake completed333 ms
9 days agoHandshake completed313 ms
12 days agoHandshake completed321 ms
13 days agoHandshake completed315 ms
15 days agoHandshake completed386 ms
17 days agoHandshake completed340 ms
18 days agoHandshake completed326 ms
19 days agoHandshake completed333 ms
20 days agoHandshake completed325 ms
20 days agoHandshake completed128 ms
21 days agoHandshake completed127 ms
23 days agoHandshake completed323 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.