Remote MCP · Endpoint

Sail MCP server

No. Sail answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sailrides.co/mcp

The last check completed an MCP handshake.

Registry name
co.sailrides/sail
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
333 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Search places, compare ride-hailing options, and plan trotro minibus journeys.
Listing
From the official MCP registry (active).
Recent checks of Sail
CheckedResultHandshake
1 hour agoHandshake completed333 ms
1 day agoHandshake completed299 ms
2 days agoHandshake completed382 ms
3 days agoHandshake completed340 ms
4 days agoHandshake completed305 ms
5 days agoHandshake completed345 ms
7 days agoHandshake completed323 ms
10 days agoHandshake completed308 ms
12 days agoHandshake completed310 ms
14 days agoHandshake completed426 ms
17 days agoHandshake completed302 ms
19 days agoHandshake completed307 ms
21 days agoHandshake completed309 ms
23 days agoHandshake completed309 ms
25 days agoHandshake completed309 ms
26 days agoHandshake completed313 ms
28 days agoHandshake completed310 ms
29 days agoHandshake completed316 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 Sail and makes no claim about it beyond what these checks measured.