Remote MCP · Endpoint
io.github.lxxmng/ocean-schedules MCP server
No. io.github.lxxmng/ocean-schedules answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://mcp.schedulesmcp.com/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.lxxmng/ocean-schedules
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 142 ms
- Tools exposed
- 9 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Compare ocean carrier schedules, transit times and reliability: 60+ carriers, 72,000+ sailings.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 142 ms |
| 1 day ago | Handshake completed | 317 ms |
| 2 days ago | Handshake completed | 150 ms |
| 3 days ago | Handshake completed | 145 ms |
| 4 days ago | Handshake completed | 320 ms |
| 5 days ago | Handshake completed | 146 ms |
| 6 days ago | Handshake completed | 245 ms |
| 9 days ago | Handshake completed | 181 ms |
| 11 days ago | Handshake completed | 179 ms |
| 14 days ago | Handshake completed | 268 ms |
| 16 days ago | Handshake completed | 144 ms |
| 18 days ago | Handshake completed | 2.18 s |
| 20 days ago | Handshake completed | 158 ms |
| 22 days ago | Handshake completed | 152 ms |
| 24 days ago | Handshake completed | 232 ms |
| 26 days ago | Handshake completed | 151 ms |
| 27 days ago | Handshake completed | 236 ms |
| 29 days ago | Handshake completed | 139 ms |
The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 io.github.lxxmng/ocean-schedules and makes no claim about it beyond what these checks measured.