Sail
REMOTE · SAILRIDES.CO
Search places, compare ride-hailing options, and plan trotro minibus journeys.
Available components
Last scanned (16 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 463 tokens (~77/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 92% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 4 Oct 26 87
- The server rewrote its instructions, which are the text every model session reads security
- Tool “plan_trip” rewrote its description, which is the text the model reads security
- Tool “plan_trotro_route” rewrote its description, which is the text the model reads security
- Schema quality: 62 → 77 ▼ functional
- Tool coverage: 82% → 92% ▲ functional
- Schema quality: good → excellent functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “plan_public_transport” functional
- “search_places” reworded the description of “countryCode” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Aug 26 0
First indexed and scored.
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 5 Nov 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=YR1,O=Let's Encrypt,C=US | 23 Oct 2026 | 21 Jan 2027 | RSA 4096 | SHA256-RSA | 6d3fbbfbdb004e51b0211c1ad8000e97425 |
| SANs: sailrides.co | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| 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. | DS published | 7786 | 8 | Verified |
| sailrides.co. | DS published | 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_public_transport Plan public transport ~71
Plan public transport with fares, walking legs, transfers, and boarding instructions: trotro in Ghana, or buses leaving now in England, Scotland and Wales. Bus times come from published timetables, not live tracking.
| Name | Type | Req | Description |
|---|---|---|---|
| destination | object | yes | Destination coordinates |
| pickup | object | yes | Pickup coordinates |
| Name | Type | Req | Description |
|---|---|---|---|
| complete | boolean | yes | – |
| network | string | yes | trotro in Ghana, or bus in Great Britain |
| routeCounts | object | yes | – |
| routes | array | yes | – |
| routesRequiringRideConnection | array | yes | – |
| skipNote | string | – | – |
No examples provided.
plan_trip Plan a trip ~65
Compare ride-hailing with public transport: trotro in Ghana, or buses leaving now in England, Scotland and Wales. 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 |
|---|---|---|---|
| bus | – | – | Bus options, present only for trips within England, Scotland and Wales |
| rides | – | yes | – |
| status | string | yes | – |
| trotro | – | yes | – |
No examples provided.
plan_trotro_route Plan a trotro route ~61
Plan trotro journeys in Ghana, including fares, walking legs, transfers, and boarding instructions. Prefer plan_public_transport, which also covers buses in Great Britain.
| 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 | – |
| skipNote | string | – | – |
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 ~87
Search for pickup or destination places. Use resolve_place on the selected result before planning a trip.
| Name | Type | Req | Description |
|---|---|---|---|
| countryCode | string | – | Country to search: "gh" for Ghana, or "gb" for England, Scotland and Wales |
| 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.
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'
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 87 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 6 tools: search_places, resolve_place, plan_trip, compare_rides, plan_public_transport, plan_trotro_route. Their descriptions and schemas cost roughly 370 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 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Sail MCP server?
VerifyMCP ran 13 checks on Sail, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.