eCommerce
vacaytickets.com
Provides grounded VacayTickets.com cruise facts, answers cruise-fit questions via Coco, and connects travelers to live WorldVia quotes, cabin holds, or deposits.
ENDPOINT 1
https://vacaytickets.com/api/coco/mcp
MCP server metadata
- Name
- vacaytickets-coco
- Version
- 1.0.0
Coco is the VacayTickets.com AI host. Never invent fares. Space is not held. Virgin is 18+. Send people to /match or /contact for a live WorldVia quote — not a booking widget.
Known tools 3
vacay_factsGrounded VacayTickets.com facts: planted sailings, Florida ports, family vs 18+, cabins Coco will not recommend.
Inferred read-onlylive_quote_pathWhen a traveler needs a live WorldVia quote, cabin hold, or deposit.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.vacaytickets-coco]
url = "https://vacaytickets.com/api/coco/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"vacaytickets-coco": {
"type": "http",
"url": "https://vacaytickets.com/api/coco/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: vacaytickets-coco
Remote MCP URL: https://vacaytickets.com/api/coco/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"vacaytickets-coco": {
"url": "https://vacaytickets.com/api/coco/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"vacaytickets-coco": {
"type": "http",
"url": "https://vacaytickets.com/api/coco/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "vacaytickets-coco",
"transport": "streamable-http",
"url": "https://vacaytickets.com/api/coco/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.