Remote MCP · Endpoint

UICapsule MCP server

No. UICapsule answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.uicapsule.com/mcp

The last check completed an MCP handshake.

Registry name
com.uicapsule/components
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
118 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and install interactive React components with unusual motion, via the shadcn CLI.
Listing
From the official MCP registry (active).
Recent checks of UICapsule
CheckedResultHandshake
1 hour agoHandshake completed118 ms
2 days agoHandshake completed109 ms
4 days agoHandshake completed111 ms
6 days agoHandshake completed64 ms
8 days agoHandshake completed87 ms
10 days agoHandshake completed70 ms
12 days agoHandshake completed49 ms
13 days agoHandshake completed70 ms
14 days agoHandshake completed66 ms
16 days agoHandshake completed71 ms
18 days agoHandshake completed258 ms
20 days agoHandshake completed142 ms
21 days agoHandshake completed91 ms
23 days agoHandshake completed88 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 UICapsule and makes no claim about it beyond what these checks measured.