Remote MCP · Endpoint

Unslop MCP server

No. Unslop answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://oleg.design/unslop/mcp

The last check completed an MCP handshake.

Registry name
io.github.0design/unslop
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
287 ms
Tools exposed
0 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Read-only canon of design and copy rules for AI agents to audit generated UI, served as resources.
Listing
From the official MCP registry (active).
Recent checks of Unslop
CheckedResultHandshake
1 hour agoHandshake completed287 ms
1 day agoHandshake completed169 ms
2 days agoHandshake completed235 ms
3 days agoHandshake completed144 ms
4 days agoHandshake completed144 ms
5 days agoHandshake completed235 ms
6 days agoHandshake completed272 ms
8 days agoHandshake completed206 ms
11 days agoHandshake completed170 ms
13 days agoHandshake completed188 ms
15 days agoHandshake completed298 ms
18 days agoHandshake completed200 ms
20 days agoHandshake completed488 ms
22 days agoHandshake completed144 ms
24 days agoHandshake completed164 ms

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

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