Remote MCP · Endpoint

NuvUI MCP server

No. NuvUI answered an MCP handshake 4 days ago.

UpLast checked 4 days ago

Server URL

https://nuvui.nuvraxis.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.Nuvraxis/nuvui
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
383 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
The docs, rules, blocks, charts and design tokens of nuvui, a React UI library, for coding agents.
Listing
From the official MCP registry (active).
Recent checks of NuvUI
CheckedResultHandshake
4 days agoHandshake completed383 ms
4 days agoHandshake completed490 ms
5 days agoHandshake completed398 ms
7 days agoHandshake completed386 ms
8 days agoHandshake completed412 ms
9 days agoHandshake completed398 ms
10 days agoHandshake completed396 ms
11 days agoHandshake completed414 ms
12 days agoHandshake completed509 ms
15 days agoHandshake completed409 ms
18 days agoHandshake completed420 ms
20 days agoHandshake completed389 ms
22 days agoHandshake completed400 ms
24 days agoHandshake completed408 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 NuvUI and makes no claim about it beyond what these checks measured.