Sail
REMOTE · SAILRIDES.CO · SCANNED SEP 21
Search places, compare ride-hailing options, and plan trotro minibus journeys.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 310 tokens (~62/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 82% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Sail MCP server?
Sail is a hosted endpoint at https://sailrides.co/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sailrides.co
claude mcp add --transport http co-sailrides-sail 'https://sailrides.co/mcp'
{
"mcpServers": {
"co-sailrides-sail": {
"url": "https://sailrides.co/mcp"
}
}
} {
"servers": {
"co-sailrides-sail": {
"type": "http",
"url": "https://sailrides.co/mcp"
}
}
} [mcp_servers.co-sailrides-sail] url = "https://sailrides.co/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-sailrides-sail": {
"type": "remote",
"url": "https://sailrides.co/mcp",
"enabled": true
}
}
} openclaw mcp add co-sailrides-sail --url 'https://sailrides.co/mcp' --transport streamable-http
mcp_servers:
co-sailrides-sail:
url: "https://sailrides.co/mcp" {
"McpServers": {
"co-sailrides-sail": {
"Transport": "http",
"Url": "https://sailrides.co/mcp"
}
}
} assistant mcp add co-sailrides-sail -t streamable-http -u 'https://sailrides.co/mcp'
{
"mcpServers": {
"co-sailrides-sail": {
"type": "http",
"url": "https://sailrides.co/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://sailrides.co/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sailrides.co | CN=YR2,O=Let's Encrypt,C=US | 23 Aug 2026 | 21 Nov 2026 | RSA 4096 | SHA256-RSA | 6328c8922e923e8f5b8392b35f45b85d922 |
| SANs: sailrides.co | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of sailrides.co. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| co. | present | 7786 | 8 | Verified |
| sailrides.co. | present | 19852 | 13 | Verified |
| sailrides.co. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sailrides.co/mcp | Verified | 200 | |
| http (plaintext) | http://sailrides.co/mcp | HTTPS enforced | 301 | https://sailrides.co/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_rides Compare rides ~47
Compare current ride-hailing prices and pickup times from the providers available through Sail.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | object | yes | Resolved destination place |
| pickup | object | yes | Resolved pickup place |
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | yes | – |
| optionCounts | object | yes | – |
| options | array | yes | – |
No examples provided.
plan_trip Plan a trip ~51
Compare ride-hailing and trotro options together. This is the default tool for multimodal trip planning.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | object | yes | Resolved destination place |
| pickup | object | yes | Resolved pickup place |
| Name | Type | Req | Description |
|---|---|---|---|
| rides | – | yes | – |
| status | string | yes | – |
| trotro | – | yes | – |
No examples provided.
plan_trotro_route Plan a trotro route ~49
Plan public transport journeys by trotro, including fares, walking legs, transfers, and boarding instructions.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | object | yes | Destination coordinates |
| pickup | object | yes | Pickup coordinates |
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | yes | – |
| routeCounts | object | yes | – |
| routes | array | yes | – |
| routesRequiringRideConnection | array | yes | – |
No examples provided.
resolve_place Resolve place ~39
Resolve a place ID from search_places to an exact name, address, and coordinates.
| Name | Type | Req | Description |
|---|---|---|---|
| placeId | string | yes | Place ID returned by search_places |
| Name | Type | Req | Description |
|---|---|---|---|
| place | – | yes | – |
No examples provided.
search_places Search places ~67
Search for pickup or destination places. Use resolve_place on the selected result before planning a trip.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | – |
| near | object | – | Coordinates used to bias nearby results |
| query | string | yes | Place name or address |
| radiusMeters | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | yes | – |
| placeCounts | object | yes | – |
| places | array | yes | – |
No examples provided.
What is the Sail MCP server?
Sail is an MCP server listed in the public MCP registry as co.sailrides/sail. Search places, compare ride-hailing options, and plan trotro minibus journeys. This page covers its hosted endpoint (https://sailrides.co/mcp).
Is the Sail MCP server safe to use?
Sail scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sail MCP server expose?
Sail exposes 5 tools: search_places, resolve_place, plan_trip, compare_rides, plan_trotro_route. Their descriptions and schemas cost roughly 253 tokens of context every time the server is loaded.
Does the Sail MCP server require authentication?
No. We connected to Sail without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sail MCP server still maintained?
Sail is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.