io.github.CloudCorpRecords/sailguide
NPM · @RENETURCIOS/SAILGUIDE · 2 COMPONENTS
Dream On BVI charter concierge reads: fact sheet, availability, open windows, quotes, other yachts.
Available components
Last scanned (19 hours ago)
Scores higher than 41% of npm servers
Category E-commerce
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability74
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 636 tokens (~127/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.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 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 17 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 16 Nov 26 55
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 21 Nov 2026 · Analysed npm/@reneturcios/sailguide@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
check_availability Check availability ~102
Check whether specific dates are open (48-hour turnaround applied). If not open, returns suggested_open_windows nearby — always offer those to the guest.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Disembarkation date (YYYY-MM-DD) |
| nights | integer | – | Use instead of end |
| requester | object | – | Optional: who this request is for, so the owner can follow up personally. |
| start | string | yes | Embarkation date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
find_open_windows Find open dates ~110
List open windows between two dates (e.g. a whole month or season) for charters of at least min_nights. Use when the guest is flexible or asks what's open.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Search from (YYYY-MM-DD) |
| min_nights | integer | – | Minimum nights (5–7 typical) |
| requester | object | – | Optional: who this request is for, so the owner can follow up personally. |
| to | string | yes | Search to (YYYY-MM-DD) |
No output schema declared.
No examples provided.
get_dream_on_facts Get Dream On facts ~110
Return Dream On's published fact sheet: the yacht, cabins, toys, amenities, crew, what's included, rates rules, booking process, sample itinerary and FAQ. This is the ONLY source of truth for answers.
| Name | Type | Req | Description |
|---|---|---|---|
| requester | object | – | Optional: who this request is for, so the owner can follow up personally. |
| section | string | – | Optional section: vessel, crew, inclusions, rates, booking, sample_itinerary, faq, contact. Omit for everything. |
No output schema declared.
No examples provided.
get_quote Get a price estimate ~108
Estimate the all-inclusive charter fee from the published rate rules. If priced=false and refer_to_owner=true, do not invent a price — offer to pass the question to the owner with ask_owner.
| Name | Type | Req | Description |
|---|---|---|---|
| guests | integer | yes | Number of guests (max 8) |
| nights | integer | yes | Number of nights |
| requester | object | – | Optional: who this request is for, so the owner can follow up personally. |
| start | string | yes | Embarkation date (YYYY-MM-DD) |
No output schema declared.
No examples provided.
suggest_other_yachts Suggest other yachts ~206
Only after Dream On's own options don't work — the group is larger than 8, or none of Dream On's open dates suit the guest — return a link to Islands & Sails, Dream On's sister concierge (run by Dream On's owner), pre-filled with the guest's dates and party size, where they can explore other hand-picked BVI crewed yachts.
| Name | Type | Req | Description |
|---|---|---|---|
| guests | integer | – | Party size, if known |
| nights | integer | – | Number of nights, if known |
| note | string | – | Short note on what they want (occasion, style), optional |
| requester | object | – | Optional: who this request is for, so the owner can follow up personally. |
| start | string | – | Preferred start date — always include it when the guest has named dates or a period (e.g. 'the last week of May 2027' → 2027-05-22 with nights 7) (YYYY-MM-DD) |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/sailguide MCP server?
io.github.CloudCorpRecords/sailguide runs locally as an npm package, launched with npx -y @reneturcios/sailguide mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/sailguide
claude mcp add cloudcorprecords-sailguide -- npx -y @reneturcios/sailguide mcp
What is the io.github.CloudCorpRecords/sailguide MCP server?
io.github.CloudCorpRecords/sailguide is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/sailguide. Dream On BVI charter concierge reads: fact sheet, availability, open windows, quotes, other yachts. This page covers its npm package (@reneturcios/sailguide).
Is the io.github.CloudCorpRecords/sailguide MCP server safe to use?
io.github.CloudCorpRecords/sailguide scores 70 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/sailguide MCP server expose?
io.github.CloudCorpRecords/sailguide exposes 5 tools: get_dream_on_facts, check_availability, find_open_windows, get_quote, suggest_other_yachts. Their descriptions and schemas cost roughly 636 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/sailguide MCP server still maintained?
io.github.CloudCorpRecords/sailguide is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/sailguide MCP server under?
io.github.CloudCorpRecords/sailguide declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.CloudCorpRecords/sailguide MCP server?
VerifyMCP ran 15 checks on io.github.CloudCorpRecords/sailguide, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/sailguide: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.