Remote MCP · Endpoint

Snapforge Ship-Ready Check MCP server

No. Snapforge Ship-Ready Check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.snapforgelab.com/mcp

The last check completed an MCP handshake.

Registry name
com.snapforgelab/ship-ready-check
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Free, read-only ship-readiness check for Replit, Lovable and Bolt apps.
Listing
From the official MCP registry (active).
Recent checks of Snapforge Ship-Ready Check
CheckedResultHandshake
1 hour agoHandshake completed103 ms
9 days agoHandshake completed177 ms
10 days agoHandshake completed159 ms
11 days agoHandshake completed78 ms
12 days agoHandshake completed76 ms
14 days agoHandshake completed101 ms
14 days agoHandshake completed90 ms
15 days agoHandshake completed109 ms
17 days agoHandshake completed239 ms
19 days agoHandshake completed238 ms
21 days agoHandshake completed85 ms
24 days agoHandshake completed111 ms
26 days agoHandshake completed109 ms
28 days agoHandshake completed124 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 Snapforge Ship-Ready Check and makes no claim about it beyond what these checks measured.