Travel · Remote MCP server
Cruise Itinerary
Cruise sailings, itineraries, weekly fare history, port capacity and the Cruise Price Index.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.cruise-itinerary/mcp- Version
- 1.0.0
- Status
- Active
- Category
- travel
- Transport
- Streamable HTTP
- Published
- 2026-10-03
- Updated
- 2026-10-03
- Publisher
- com.cruise-itinerary
- Namespace
- Namespace verified by the MCP Registry via the domain cruise-itinerary.com · how
- Website
- cruise-itinerary.com/docs#mcp
- Repository
- github.com/BigBalli/cruise-itinerary-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://cruise-itinerary.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Cruise Itinerary
Cruise Itinerary is a remote MCP server: there is nothing to install. Its endpoint is https://cruise-itinerary.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
Site checks
The website's own root, cruise-itinerary.com, was checked for the files that tell AI systems about a site.
| File | Result |
|---|---|
/llms.txt | Real file, HTTP 200 · 2026-10-04 |
/.well-known/mcp.json | No real file found |
/.well-known/ai-plugin.json | No real file found |
/agents.json | No real file found |
More travel servers
| Server | Runs |
|---|---|
| CollabsmapDiscover travel brand collab opportunities for content creators via CollabsMap. | Local · stdio |
| ConciergeSearch Africa safari destinations, generate day-by-day itineraries, and price expert travel work. | Remote · HTTPLive check: ✓ handshake |
| Cricket 2026Cricket 2026 MCP - T20 World Cup + ICC tour matches. Tournaments, fixtures, players, venues. | Remote · HTTPLive check: ✗ no handshake |
| Cricket TravelBespoke cricket and golf tours. Tour operator and package organiser, not a broker. ABTOT 5718. | Remote · HTTPLive check: ✓ handshake |
| Cuddlynest MCPSearch CuddlyNest hotels and read rooms, prices, availability and cancellation policies. | Local · stdio |
| CultureLib DiscoverFrench cultural events search with multi-reseller ticket price comparison (theatre, concerts...) | Remote · HTTPLive check: ✓ handshake |
| Curb Cut MCPWorkplace accommodation options, cost evidence and drafts. Looks up and drafts; never sends. | Local · stdio |
| Customs Dog MCPPet travel docs + border readiness. Keyless: look up entry rules + sign up. Keyed: household docs. | Remote · HTTPLive check: ✓ handshake |