Remote MCP · Endpoint

Ply UI MCP server

No. Ply UI answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://mcp.ply-ui.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.ply-ui-ng/ply-ui
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
797 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
List, search, and inspect Ply Angular + Tailwind copy-in components.
Listing
From the official MCP registry (active).
Recent checks of Ply UI
CheckedResultHandshake
1 day agoHandshake completed797 ms
3 days agoHandshake completed132 ms
5 days agoHandshake completed740 ms
7 days agoHandshake completed245 ms
9 days agoHandshake completed220 ms
11 days agoHandshake completed161 ms
13 days agoHandshake completed253 ms
14 days agoHandshake completed460 ms
15 days agoHandshake completed155 ms
18 days agoHandshake completed148 ms
19 days agoHandshake completed179 ms
21 days agoHandshake completed252 ms
22 days agoHandshake completed198 ms
23 days agoHandshake completed151 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 Ply UI and makes no claim about it beyond what these checks measured.