Remote MCP · Endpoint

Watermelon UI MCP server

No. Watermelon UI answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://mcp.watermelon.sh/mcp

The last check completed an MCP handshake.

Registry name
sh.watermelon/ui
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
53 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search free React, Tailwind, and shadcn components, blocks, and dashboards; get installable source.
Listing
From the official MCP registry (active).
Recent checks of Watermelon UI
CheckedResultHandshake
3 hours agoHandshake completed53 ms
2 days agoHandshake completed91 ms
4 days agoHandshake completed451 ms
6 days agoHandshake completed243 ms
8 days agoHandshake completed110 ms
10 days agoHandshake completed86 ms
12 days agoHandshake completed43 ms
14 days agoHandshake completed61 ms
16 days agoHandshake completed45 ms
17 days agoHandshake completed345 ms
18 days agoHandshake completed82 ms
21 days agoHandshake completed32 ms
22 days agoHandshake completed434 ms
24 days agoHandshake completed43 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 Watermelon UI and makes no claim about it beyond what these checks measured.