Remote MCP · Endpoint

Shipstry Launch Data MCP server

No. Shipstry Launch Data answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://shipstry.com/mcp

The last check completed an MCP handshake.

Registry name
com.shipstry/launch-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
421 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Weekly product launch data from Shipstry: launches, winners, and category benchmarks.
Listing
From the official MCP registry (active).
Recent checks of Shipstry Launch Data
CheckedResultHandshake
3 hours agoHandshake completed421 ms
9 days agoHandshake completed425 ms
10 days agoHandshake completed481 ms
11 days agoHandshake completed345 ms
12 days agoHandshake completed50 ms
14 days agoHandshake completed939 ms
14 days agoHandshake completed541 ms
15 days agoHandshake completed401 ms
17 days agoHandshake completed677 ms
19 days agoHandshake completed499 ms
21 days agoHandshake completed811 ms
24 days agoHandshake completed690 ms
26 days agoHandshake completed746 ms
28 days agoHandshake completed46 ms

The last 14 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 Shipstry Launch Data and makes no claim about it beyond what these checks measured.