# Cruise Itinerary (remote · cruise-itinerary.com)

Cruise sailings, itineraries, weekly fare history, port capacity and the Cruise Price Index.

- Trust score: 39/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `cruise-itinerary.com`: 39/100 (this document), [markdown](https://verifymcp.io/servers/com-cruise-itinerary-mcp/cruise-itinerary.md), [page](https://verifymcp.io/servers/com-cruise-itinerary-mcp/cruise-itinerary)

## Channel facts

- Endpoint: `https://cruise-itinerary.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 97/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism.
- **Transport & Reachability**: 0/100
  - Transport blocked by authentication: the endpoint requires auth we don't have to verify streamable-http.
- **Schema Quality & AI Usability**: 0/100
  - Schema blocked by authentication: the endpoint requires auth we don't have to read it.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Tool Safety**: 0/100
  - Tool safety blocked by authentication: the endpoint requires auth we don't have to read its tools.
- **Capabilities**: 0/100
  - Capabilities blocked by authentication: the endpoint requires auth we don't have to read them.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-cruise-itinerary-mcp 'https://cruise-itinerary.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cruise-itinerary-mcp": {
      "url": "https://cruise-itinerary.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cruise-itinerary-mcp": {
      "type": "http",
      "url": "https://cruise-itinerary.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cruise-itinerary-mcp]
url = "https://cruise-itinerary.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cruise-itinerary-mcp": {
      "type": "remote",
      "url": "https://cruise-itinerary.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cruise-itinerary-mcp --url 'https://cruise-itinerary.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cruise-itinerary-mcp:
    url: "https://cruise-itinerary.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cruise-itinerary-mcp": {
      "Transport": "http",
      "Url": "https://cruise-itinerary.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cruise-itinerary-mcp -t streamable-http -u 'https://cruise-itinerary.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cruise-itinerary-mcp": {
      "type": "http",
      "url": "https://cruise-itinerary.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-04 (score 39, −40)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security regression] Transport: pass → unverified
- [security] Authorization: The endpoint enforces authorisation, advertised via RFC 9728 protected-resource metadata.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-10-03 (score 79)

First indexed and scored.

## MCP tools (6)

### `resolve_entity` (~133 tokens)

Resolve a port, ship or cruise line

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.

Input parameters:

- `query` (string, required): 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.

Output parameters:

- `data` (array)
- `meta`

### `search_sailings` (~329 tokens)

Search upcoming sailings

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.

Input parameters:

- `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).

Output parameters:

- `data` (array)
- `meta`

### `get_itinerary` (~167 tokens)

Get a sailing's or cruise's itinerary

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.

Input parameters:

- `cruise_id` (string): Cruise id (slug), e.g. from a sailing's cruise.id.
- `sailing_id` (integer): Sailing id (integer).

### `get_price_history` (~116 tokens)

Get a sailing's weekly fare history

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.

Input parameters:

- `page` (integer): Page number, from 1.
- `per_page` (integer): Rows per page (default 50).
- `sailing_id` (integer, required): Sailing id (integer).

Output parameters:

- `data` (array)
- `meta`

### `port_month_capacity` (~142 tokens)

Get a port's monthly cruise ship capacity

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.

Input parameters:

- `from_month` (string): First month as YYYY-MM (default: this month).
- `months` (integer): Number of months (default 12).
- `port` (string, required): Port id.

Output parameters:

- `data` (object)
- `meta` (object)

### `cruise_price_index` (~270 tokens)

Get the Cruise Price Index

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).

Input parameters:

- `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.

Output parameters:

- `data` (array)
- `meta`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cruise-itinerary-mcp/cruise-itinerary#diagnostics

## Score history

- 2026-11-05: 39
- 2026-11-04: 39
- 2026-11-03: 39
- 2026-11-02: 39
- 2026-11-01: 39
- 2026-10-31: 39
- 2026-10-30: 39
- 2026-10-29: 39
- 2026-10-28: 39
- 2026-10-27: 39
- 2026-10-26: 39
- 2026-10-25: 39
- 2026-10-24: 39
- 2026-10-23: 39
- 2026-10-22: 39
- 2026-10-21: 39
- 2026-10-20: 39
- 2026-10-19: 39
- 2026-10-18: 39
- 2026-10-17: 39
- 2026-10-16: 39
- 2026-10-15: 39
- 2026-10-14: 39
- 2026-10-13: 39
- 2026-10-12: 39
- 2026-10-10: 39
- 2026-10-07: 39
- 2026-10-04: 39
- 2026-10-03: 79

## Common questions

### 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.

## Links

- Remote endpoint: https://cruise-itinerary.com/mcp
- Repository: https://github.com/BigBalli/cruise-itinerary-mcp
- Website: https://cruise-itinerary.com/docs#mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-cruise-itinerary-mcp/cruise-itinerary.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cruise-itinerary-mcp/cruise-itinerary.json
- HTML version of this page: https://verifymcp.io/servers/com-cruise-itinerary-mcp/cruise-itinerary