Remote MCP · Endpoint

NTWX Studio catalogue MCP server

No. NTWX Studio catalogue answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.ml-nightworx.studio/catalogue
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
142 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only NTWX Studio catalogue for consumer agents. No checkout.
Listing
From the official MCP registry (active).
Recent checks of NTWX Studio catalogue
CheckedResultHandshake
5 hours agoHandshake completed142 ms
9 days agoHandshake completed210 ms
10 days agoHandshake completed121 ms
11 days agoHandshake completed176 ms
12 days agoHandshake completed114 ms
14 days agoHandshake completed138 ms
14 days agoHandshake completed73 ms
15 days agoHandshake completed80 ms
17 days agoHandshake completed135 ms
19 days agoHandshake completed128 ms
22 days agoHandshake completed141 ms
24 days agoHandshake completed95 ms
26 days agoHandshake completed165 ms
28 days agoHandshake completed203 ms

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

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