Remote MCP · Endpoint

Sleek MCP server

No. Sleek answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sleek.design/api/mcp

The last check completed an MCP handshake.

Registry name
design.sleek/sleek
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
673 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Design your mobile app UI with AI, then have your coding agent build the real app from it.
Listing
From the official MCP registry (active).
Recent checks of Sleek
CheckedResultHandshake
1 hour agoHandshake completed673 ms
18 hours agoHandshake completed102 ms
2 days agoHandshake completed66 ms
3 days agoHandshake completed93 ms
4 days agoHandshake completed139 ms
5 days agoHandshake completed109 ms
5 days agoHandshake completed107 ms
7 days agoHandshake completed65 ms
10 days agoHandshake completed127 ms
12 days agoHandshake completed139 ms
15 days agoHandshake completed195 ms
17 days agoHandshake completed1.07 s
19 days agoHandshake completed116 ms
21 days agoHandshake completed74 ms

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

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