Remote MCP · Endpoint

Ship Check MCP server

No. Ship Check answered an MCP handshake 54 minutes ago.

UpLast checked 54 minutes ago

Server URL

https://uxcontinuum.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.uxcontinuum/ship-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
173 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Scan a deployed app URL for exposed keys, open Supabase tables and missing security headers.
Listing
From the official MCP registry (active).
Recent checks of Ship Check
CheckedResultHandshake
54 minutes agoHandshake completed173 ms
2 days agoHandshake completed172 ms
5 days agoHandshake completed170 ms
7 days agoHandshake completed194 ms
9 days agoHandshake completed200 ms
11 days agoHandshake completed814 ms
13 days agoHandshake completed248 ms
15 days agoHandshake completed132 ms
17 days agoHandshake completed115 ms
19 days agoHandshake completed998 ms
20 days agoHandshake completed166 ms
21 days agoHandshake completed191 ms
23 days agoHandshake completed134 ms

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

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