Remote MCP · Endpoint

Nasaq UI MCP server

No. Nasaq UI answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.nasaqui.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.fadymondy/nasaq
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
365 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Nasaq design system docs for agents: 390 components for React, Vue, Blade and HTML, with Arabic RTL.
Listing
From the official MCP registry (active).
Recent checks of Nasaq UI
CheckedResultHandshake
2 hours agoHandshake completed365 ms
1 day agoHandshake completed382 ms
2 days agoHandshake completed460 ms
3 days agoHandshake completed400 ms
4 days agoHandshake completed372 ms
5 days agoHandshake completed391 ms
6 days agoHandshake completed365 ms
9 days agoHandshake completed430 ms
12 days agoHandshake completed400 ms
14 days agoHandshake completed368 ms
16 days agoHandshake completed570 ms
18 days agoHandshake completed481 ms
20 days agoHandshake completed672 ms
22 days agoHandshake completed471 ms
24 days agoHandshake completed462 ms

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

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