Cruise Itinerary
REMOTE · CRUISE-ITINERARY.COM
Cruise sailings, itineraries, weekly fare history, port capacity and the Cruise Price Index.
Available components
Last scanned (2 hours ago)
Scores higher than 35% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
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 Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability0
- Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http. See how to fix → View diagnostics → Unverified
Schema Quality & AI Usability0
- Schema blocked by authentication: the endpoint requires auth we don't have to read it. See how to fix → Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Tool Safety0
- Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.Unverified
Capabilities0
- Capabilities blocked by authentication: the endpoint requires auth we don't have to read them. See how to fix → Unverified
Unverified: 6 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm. Claim this server and supply a read-only token to verify it and lift the score.
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 −40
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- Transport: pass → unverified ▼ security
- Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Oct 26 79
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://cruise-itinerary.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cruise-itinerary.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 6994477c3223e7e40e73d517e2bc8bd4 |
| SANs: cruise-itinerary.com, *.cruise-itinerary.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cruise-itinerary.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cruise-itinerary.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On connection |
| HTTP status | 401 |
WWW-Authenticate challenge Bearer resource_metadata="https://cruise-itinerary.com/.well-known/oauth-protected-resource/mcp", scope="cruise:read"
Bearer resource_metadata="https://cruise-itinerary.com/.well-known/oauth-protected-resource/mcp", scope="cruise:read"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubdomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(self), microphone=(self), geolocation=(self), usb=(), serial=(), bluetooth=(), midi=(), hid=(), browsing-topics=(), interest-cohort=() |
| www-authenticate | Bearer resource_metadata="https://cruise-itinerary.com/.well-known/oauth-protected-resource/mcp", scope="cruise:read" |
Protected resource metadata
| Document | https://cruise-itinerary.com/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://cruise-itinerary.com/mcp |
| Authorisation server | https://cruise-itinerary.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cruise-itinerary.com/mcp | Auth required | 401 | |
| http (plaintext) | http://cruise-itinerary.com/mcp | HTTPS enforced | 301 | https://cruise-itinerary.com/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 →
cruise_price_index Get the Cruise Price Index ~270
The weekly Cruise Price Index: how cruise fares moved week on week, matching the same sailings across loads (100 = 2026-09-06), with the share of fares cut and raised and the average per-night fare. view "latest" (default, every plan) gives the last 12 weeks for all lines and the 8 largest lines. view "series" (Business plan or above) gives the full series for one line, cabin and segment (booking window or sail quarter).
| Name | Type | Req | Description |
|---|---|---|---|
| cabin | string | – | series only: cabin class (default any). |
| from | string | – | series only: earliest week (YYYY-MM-DD). |
| line | string | – | series only: cruise line id, or "all" (default). |
| page | integer | – | series only: page number, from 1. |
| per_page | integer | – | series only: rows per page (default 50). |
| segment | string | – | series only: all (default), a booking window w000_090, w091_180, w181_365, w366_plus, or a sail quarter like q2027_1. |
| to | string | – | series only: latest week (YYYY-MM-DD). |
| view | string | – | latest (default) or series. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| meta | – | yes | – |
No examples provided.
get_itinerary Get a sailing's or cruise's itinerary ~167
Day-by-day itinerary. With sailing_id (an integer sailing id): every dated day with its port, kind (embark, call, scenic, sea, disembark) and day_confidence, plus the sailing's latest fares. With cruise_id (a cruise slug, the route shared by its sailings): the ordered stop list, numbered by day where the line publishes its itinerary (itinerary_source "official") and without day numbers otherwise ("supplier"). Give exactly one of the two. Days marked "estimated" were placed by distance and can be off by a day. Needs the Developer plan or above.
| Name | Type | Req | Description |
|---|---|---|---|
| cruise_id | string | – | Cruise id (slug), e.g. from a sailing's cruise.id. |
| sailing_id | integer | – | Sailing id (integer). |
Structured output declared, but exposes no named fields.
No examples provided.
get_price_history Get a sailing's weekly fare history ~116
Every weekly fare snapshot recorded for one sailing, oldest first (captured each Monday since 2026-09-06), per cabin class in whole USD. Shows whether and when a fare went up or down. Snapshots, not live prices; a null fare means not offered or sold out. Needs the Business plan or above.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, from 1. |
| per_page | integer | – | Rows per page (default 50). |
| sailing_id | integer | yes | Sailing id (integer). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| meta | – | yes | – |
No examples provided.
port_month_capacity Get a port's monthly cruise ship capacity ~142
Cruise traffic at one port, month by month: ship-days in port, distinct ships, and total berths (ship capacity summed over every ship-day; a ship in port two days counts twice), with embark, disembark and turnaround ship-days and how many ship-days are estimated. Monthly totals only; there are deliberately no per-day figures. Berths are capacity, not passengers. Ids are canonical slugs. Needs the Business plan or above.
| Name | Type | Req | Description |
|---|---|---|---|
| from_month | string | – | First month as YYYY-MM (default: this month). |
| months | integer | – | Number of months (default 12). |
| port | string | yes | Port id. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | yes | – |
| meta | object | yes | – |
No examples provided.
resolve_entity Resolve a port, ship or cruise line ~133
Turn free text (a port, ship or cruise line name, misspelt or with old names and aliases) into the canonical ids every other tool takes. Returns up to five candidates, best first, with a confidence from 0 to 1 (1.0 exact name; below about 0.6 is a weak match). Available on every plan.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The name to look up, up to 120 characters, e.g. "Port Canaveral", "Symphony of the Seas", "NCL". |
| type | string | – | Restrict to one kind of entity. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| meta | – | yes | – |
No examples provided.
search_sailings Search upcoming sailings ~329
Find upcoming cruise sailings by ship, cruise line, port of call, departure port, region, departure dates, length and fare, with each sailing's latest weekly fares (inside, outside, balcony, suite). Ids are canonical slugs. Fares are weekly snapshots in USD, not live prices; a null fare means not offered or sold out. Coverage is strongest for North American cruise lines. TUI Cruises/Marella, AIDA, Saga, Fred. Olsen and Hapag-Lloyd are not covered. Needs the Developer plan or above.
| Name | Type | Req | Description |
|---|---|---|---|
| cabin | string | – | Only sailings with a fare in this cabin class; also the cabin max_fare and sort=fare use. |
| embark_port | string | – | Departure port id. |
| from | string | – | Earliest departure date (YYYY-MM-DD). |
| line | string | – | Cruise line id. |
| max_fare | integer | – | Highest fare in whole USD (in cabin, or in any cabin when cabin is absent). |
| max_nights | integer | – | Maximum length in nights. |
| min_nights | integer | – | Minimum length in nights. |
| page | integer | – | Page number, from 1. |
| per_page | integer | – | Rows per page (default 20). |
| port | string | – | Port id: sailings that call there. |
| region | string | – | Region id. |
| ship | string | – | Ship id. |
| sort | string | – | departure (default) or fare, lowest first. |
| to | string | – | Latest departure date (YYYY-MM-DD). |
| Name | Type | Req | Description |
|---|---|---|---|
| data | array | yes | – |
| meta | – | yes | – |
No examples provided.
How do I install the Cruise Itinerary MCP server?
Cruise Itinerary is a hosted endpoint at https://cruise-itinerary.com/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 · cruise-itinerary.com
claude mcp add --transport http com-cruise-itinerary-mcp 'https://cruise-itinerary.com/mcp'
What is the Cruise Itinerary MCP server?
Cruise Itinerary is an MCP server listed in the public MCP registry as com.cruise-itinerary/mcp. Cruise sailings, itineraries, weekly fare history, port capacity and the Cruise Price Index. This page covers its hosted endpoint (https://cruise-itinerary.com/mcp).
Is the Cruise Itinerary MCP server safe to use?
Cruise Itinerary scores 39 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 Cruise Itinerary MCP server expose?
Cruise Itinerary exposes 6 tools: resolve_entity, search_sailings, get_itinerary, get_price_history, port_month_capacity, cruise_price_index. Their descriptions and schemas cost roughly 1,157 tokens of context every time the server is loaded.
Does the Cruise Itinerary MCP server require authentication?
Yes. Cruise Itinerary asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Cruise Itinerary MCP server still maintained?
Cruise Itinerary 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.