Remote MCP · Endpoint

NTWX AAAS catalogue MCP server

No. NTWX AAAS catalogue answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://aaas.ml-nightworx.io/mcp

The last check completed an MCP handshake.

Registry name
io.ml-nightworx.aaas/catalogue
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
117 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only parent catalogue of NTWX live surfaces. No checkout.
Listing
From the official MCP registry (active).
Recent checks of NTWX AAAS catalogue
CheckedResultHandshake
2 hours agoHandshake completed117 ms
2 days agoHandshake completed107 ms
4 days agoHandshake completed152 ms
6 days agoHandshake completed104 ms
8 days agoHandshake completed209 ms
10 days agoHandshake completed108 ms
13 days agoHandshake completed190 ms
14 days agoHandshake completed70 ms
16 days agoHandshake completed151 ms
17 days agoHandshake completed470 ms
18 days agoHandshake completed81 ms
21 days agoCredentials required—
22 days agoHandshake completed87 ms
24 days agoHandshake completed173 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 NTWX AAAS catalogue and makes no claim about it beyond what these checks measured.