Remote MCP · Endpoint

SeaReady MCP server

No. SeaReady answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://seaready.net/mcp

The last check completed an MCP handshake.

Registry name
net.seaready/seaready
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
173 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Ship inspection readiness: SIRE 2.0 prep questions, PSC checklists, upcoming vetting changes.
Website
https://seaready.net/
Listing
From the official MCP registry (active).
Recent checks of SeaReady
CheckedResultHandshake
56 minutes agoHandshake completed173 ms
1 day agoHandshake completed174 ms
2 days agoHandshake completed524 ms
5 days agoHandshake completed160 ms
8 days agoHandshake completed164 ms
10 days agoHandshake completed194 ms
12 days agoHandshake completed135 ms
14 days agoHandshake completed202 ms
16 days agoHandshake completed155 ms
18 days agoHandshake completed133 ms
20 days agoHandshake completed69 ms
22 days agoHandshake completed61 ms
23 days agoHandshake completed71 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with SeaReady and makes no claim about it beyond what these checks measured.