# MolTravel (remote · mcp.moltravel.com)

Aggregated travel MCP — flights, tours, activities, price checks, visas, and more.

- Trust score: 63/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

- Endpoint: `https://mcp.moltravel.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- 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-08-03.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 53 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 51/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 9765 tokens (~184/item across 53 items; 53 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
  - Structured output schemas are declared (23% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-moltravel-travel https://mcp.moltravel.com/mcp
```

### Codex

```toml
[mcp_servers.com-moltravel-travel]
url = "https://mcp.moltravel.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-moltravel-travel --url https://mcp.moltravel.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-moltravel-travel:
    url: "https://mcp.moltravel.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-moltravel-travel": {
      "type": "http",
      "url": "https://mcp.moltravel.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-08-03 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 62, 0)

- [security] Tool “trivago_trivago-accommodation-radius-search” rewrote its description, which is the text the model reads
- [security] Tool “trivago_trivago-accommodation-search” rewrote its description, which is the text the model reads
- [cosmetic] “trivago_trivago-accommodation-search” reworded the description of “departure”
- [cosmetic] “trivago_trivago-accommodation-radius-search” reworded the description of “departure”
- [cosmetic] “trivago_trivago-accommodation-radius-search” reworded the description of “arrival”
- [cosmetic] “trivago_trivago-accommodation-search” reworded the description of “arrival”

### 2026-08-01 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 61, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-29 (score 59, 0)

- [security] Tool “trivago_trivago-accommodation-search” rewrote its description, which is the text the model reads
- [security] Tool “trivago_trivago-accommodation-radius-search” rewrote its description, which is the text the model reads
- [cosmetic] “trivago_trivago-accommodation-search” reworded the description of “departure”
- [cosmetic] “trivago_trivago-accommodation-search” reworded the description of “arrival”
- [cosmetic] “trivago_trivago-accommodation-radius-search” reworded the description of “departure”
- [cosmetic] “trivago_trivago-accommodation-radius-search” reworded the description of “arrival”

### 2026-07-28 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 58, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (53)

### `restcountries_country_info` (~42 tokens)

[restcountries] Look up country information from REST Countries.

Input parameters:

- `fields`
- `query` (string, required)
- `search_by` (string)

Output parameters:

- `result` (string)

### `fcdo_travel_advice` (~46 tokens)

[fcdo] Get UK FCDO travel advice for a specific country. Includes safety, entry requirements, health, and warnings.

Input parameters:

- `country` (string, required)

Output parameters:

- `result` (string)

### `fcdo_list_countries` (~26 tokens)

[fcdo] List all countries with UK FCDO travel advice.

Output parameters:

- `result` (string)

### `airports_lookup` (~42 tokens)

Look up an airport by IATA (3-char) or ICAO (4-char) code. Returns full details including runways.

Input parameters:

- `code` (string, required)

Output parameters:

- `result` (string)

### `airports_search` (~43 tokens)

Search airports by name or city. Returns up to 20 results sorted by size.

Input parameters:

- `country`
- `query` (string, required)
- `type_filter`

Output parameters:

- `result` (string)

### `airports_near` (~60 tokens)

Find airports near a geographic point. Returns results sorted by distance.

Input parameters:

- `include_small` (boolean)
- `latitude` (number, required)
- `limit` (integer)
- `longitude` (number, required)
- `radius_km` (number)

Output parameters:

- `result` (string)

### `airlines_lookup` (~35 tokens)

Look up an airline by IATA (2-char) or ICAO (3-char) code.

Input parameters:

- `code` (string, required)

Output parameters:

- `result` (string)

### `airlines_search` (~40 tokens)

Search airlines by name. Returns up to 20 results.

Input parameters:

- `active_only` (boolean)
- `country`
- `query` (string, required)

Output parameters:

- `result` (string)

### `visa_check` (~33 tokens)

Check visa requirement for a passport country visiting a destination.

Input parameters:

- `destination` (string, required)
- `passport` (string, required)

Output parameters:

- `result` (string)

### `visa_summary` (~29 tokens)

Overview of visa-free access for a passport country — counts by category.

Input parameters:

- `passport` (string, required)

Output parameters:

- `result` (string)

### `data_status` (~27 tokens)

Check which static datasets (airports, airlines, visas) are loaded and their row counts.

Output parameters:

- `result` (string)

### `peek_experience_availability` (~117 tokens)

[peek] Get availability information for a specific experience including dates, times, and pricing

Input parameters:

- `endDate` (string, required): End date inclusive in YYYY-MM-DD format (e.g., '2025-06-20' would return things taking place ON or BEFORE the 20th)
- `id` (string, required): The ID of the experience
- `quantity` (integer, required): Number of travelers
- `startDate` (string, required): Start date inclusive YYYY-MM-DD format (e.g., '2025-06-19')

### `peek_experience_details` (~37 tokens)

[peek] Get detailed information about a specific experience by ID

Input parameters:

- `id` (string, required): The ID of the experience to retrieve

### `peek_list_tags` (~17 tokens)

[peek] List all category tags

### `peek_render_activity_tiles` (~50 tokens)

[peek] Render activity tiles for a list of activity IDs, returning an embeddable widget URI

Input parameters:

- `id` (string, required): ID or comma separate list of activity IDs to render as tiles

### `peek_search_experiences` (~328 tokens)

[peek] Search for travel experiences with comprehensive filtering options. Returns available categories, tags, and regions with IDs for further filtering.

Input parameters:

- `categoryId` (string): Limit to only a specific activity category
- `endDate` (string): Return experiences that are available on or before this date in YYYY-MM-DD format (e.g., '2025-06-20' would return things taking place ON or BEFORE the 20th)
- `latLng` (string): When the user wants something NEAR a specific place, but not necessarily IN a specific place, limit to only those near a given lat_lng. ex: "37.7799,-122.2822". Don't use this for regions, instead us…
- `query` (string): When the user wants something w/ a specific keyword (bike, beer, art, etc) limit to experiences whose title contain a keyword. Never include location information.
- `regionId` (string): When you have determined the user wants something in a specific region (found w/ search_regions) limit to only a specific region ID
- `startDate` (string): Return experiences that are available on or after this date. YYYY-MM-DD format (e.g., '2025-06-19')
- `tagId` (string): When you have determined the user is interest in a specific vibe of activity (family friendly, romantic, etc) limit to only experiences with a specific tag (single tag ID)

### `peek_search_regions` (~50 tokens)

[peek] Search for regions by name

Input parameters:

- `limit` (integer): Maximum number of regions to return (default: 50)
- `query` (string, required): Search query to match against region names

### `tourradar_b2b-operator-details` (~65 tokens)

[tourradar] Use this when the user wants information about a tour operator, such as their terms and policies.

Fetches operator details including name, code, and terms & conditions based on operator ID.

Input parameters:

- `operatorId` (integer, required)

### `tourradar_b2b-cities-search` (~198 tokens)

[tourradar] Use this when you need to find city IDs for tour search filters like start city, end city, or cities to visit.

Searches for cities by name within a specific country. Supports multiple name variants to handle different spellings (e.g., Krakow, Kraków, Cracow).

Input parameters:

- `country_code` (string, required): ISO 3166-1 alpha-2 country code (e.g., 'US' for USA, 'GB' for United Kingdom, 'DE' for Germany).
- `search` (array, required): City name filter. It is recommended to use this filter to narrow down the search results. Please use english only names. How to search: If you are looking for Kraków city, please pass potential candi…

### `tourradar_b2b-continents-list` (~53 tokens)

[tourradar] Use this when you need continent IDs for filtering tours by region.

Returns a list of all supported continents with their IDs and names for use in tour search filters.

### `tourradar_b2b-countries-list` (~57 tokens)

[tourradar] Use this when you need to look up country IDs for filtering tours or validating country names.

Returns a complete list of all supported countries with their IDs, names, and ISO country codes.

### `tourradar_b2b-currencies-list` (~59 tokens)

[tourradar] Use this when you need to check supported currencies or get currency details like symbols.

Returns a list of all supported currencies with their codes (USD, EUR), names, and symbols ($, €).

### `tourradar_b2b-languages-list` (~56 tokens)

[tourradar] Use this when you need language IDs for filtering tours by guide language.

Returns a list of all supported languages with their IDs, codes, and names for use in tour search filters.

### `tourradar_b2b-tour-types-list` (~58 tokens)

[tourradar] Use this when you need tour type IDs for filtering tours by category like adventure, cultural, or wildlife.

Returns a hierarchical list of tour type groups and their individual types with IDs and names.

### `tourradar_b2b-tour-departures` (~149 tokens)

[tourradar] Use this when the user asks about available departure dates, pricing for specific dates, or needs to validate if a departure date is available.

Returns a list of departures for a specific tour within a date range, including availability status, pricing, and booking information.

Input parameters:

- `currency` (string): Currency to return prices in. Use this only when the user explicitly asks for a specific currency. Otherwise the user's default (based on location) is used.
- `dateRange` (object, required): Returns only departure dates in the desired range
- `page` (integer): Page number. Default is 1
- `tourId` (integer, required): Tour ID

### `tourradar_b2b-tour-details` (~102 tokens)

[tourradar] Use this when the user wants to see detailed information about a specific tour.

Fetches comprehensive tour details including itinerary, pricing, operator info, images, and booking links based on tour ID.

Input parameters:

- `currency` (string): Currency to return prices in. Use this only when the user explicitly asks for a specific currency. Otherwise the user's default (based on location) is used.
- `tourId` (integer, required)

### `tourradar_b2b-tour-faq` (~88 tokens)

[tourradar] Use this when the user has questions about a tour that might be answered in the FAQ section.

Returns a paginated list of frequently asked questions and answers about a specific tour, covering topics like inclusions, requirements, and policies.

Input parameters:

- `page` (integer): Page number. Default is 1
- `tourId` (integer, required)

### `tourradar_b2b-tour-map` (~112 tokens)

[tourradar] Use this when the user wants to see tour routes on a map or compare itineraries visually.

Fetches tour details for one or more tours and prepares map data with all itinerary locations, coordinates, and day-by-day information for visual display.

Input parameters:

- `currency` (string): Currency to return prices in. Use this only when the user explicitly asks for a specific currency. Otherwise the user's default (based on location) is used.
- `tourIds` (array, required)

### `tourradar_general-current-date` (~55 tokens)

[tourradar] Use this when you need to know the current date, especially before setting departure date filters.

Returns the current date and time in ISO format. Essential for calculating valid date ranges for tour searches.

### `tourradar_vertex-tour-search` (~1985 tokens)

[tourradar] Use this when the user describes what they want in natural language and you need AI-powered semantic search to understand their intent.

Before use this tool, please READ all possible filters.
PLESE USE FILTERS, when can be used, to make search faster and much more precise.
Please use start_city, end_city, cities, countries, start_country, end_country filters if possible.  You can use multiple of them.

AI-powered semantic search for tours using natural language queries combined with optional filters. Uses Google Vertex AI to understand intent and find relevant tours based on descriptions, themes, or specific requests.

Use `vertex-tour-search` when:

\- The user describes what they want in natural language
\- You need semantic/AI-powered search to understand intent
\- Combining natural language with filters for refined results

Examples:

\- "Family-friendly safari with kids under 12"
\- "Romantic honeymoon trip with beach and mountains"
\- "Adventure tour with hiking and camping for beginners"
\- "Cultural immersion experience with local homestays"
\- "Wine tasting tour through European countryside"

\## Input

\### Required

\- `textSearch`: Natural language description of what the user is looking for
\- `display_mode`: How to display results — `"listing"` (default, carousel of tour cards) or `"map"` (interactive map view)

\### Optional Filters

\#### Location Filters

\| Filter          | Type     | Description                                                                |
\| --------------- | -------- | -------------------------------------------------------------------------- |
\| `start_country` | string[] | Country where tour BEGINS (ISO 3166-1 alpha-2 codes). OR logic.            |
\| `end_country`   | string[] | Country where tour ENDS (ISO 3166-1 alpha-2 codes). OR logic.              |
\| `start_city`    | number[] | City IDs where tour starts. Use `b2b-cities-search` to find IDs. OR logic. |
\| `end_city`      | number[] | City IDs where tour ends. Use `b2b…

Input parameters:

- `cities` (object): Filter tours by cities visited on the itinerary. City IDs can be obtained from the b2b-cities-search tool
- `countries` (object): Filter by countries visited DURING the tour itinerary. Use 'start_country'/'end_country' for departure/destination countries.
- `currency` (string): Currency to return prices in. Use this only when the user explicitly asks for a specific currency. Otherwise the user's default (based on location) is used.
- `departures` (object): Filter tours by available departure months
- `discount` (object): Filter tours by discount percentage. E.g., { min: 10, max: 50 } finds tours with 10% to 50% off. Min and max value cannot be the same.
- `display_mode` (string): How to display the search results. 'listing' shows a carousel of tour cards. 'map' shows tours on an interactive map.
- `duration` (object): Filter tours by duration in days. Example: set min: 5 , max: 8 to find duration between those days. Include this filter when is needed
- `end_city` (array): City IDs where the tour ends (e.g., [1234, 5678]). Use b2b-cities-search to find city IDs. If passing multiple values, will find tours ending in any of the given cities
- `end_country` (array): Filter by the country where the tour ENDS (final destination). ISO 3166-1 alpha-2 codes (e.g., ['IT', 'FR']). Multiple values = OR logic. Use 'countries' filter for countries visited during the itine…
- `max_age` (object): Filter by tour's maximum age limit. E.g., { min: 18, max: 39 } finds tours limited to young adults. Use to find age-restricted tours like youth or senior-specific trips. Min and max value cannot be t…
- `max_group_size` (object): Filter by tour's maximum group size. E.g., { min: 1, max: 20 } finds small group tours with max 20 participants. Min and max value cannot be this same.
- `min_age` (object): Filter by tour's minimum age requirement. E.g., { min: 1, max: 12 } finds tours that accept children under 12. Use to find family-friendly tours or tours with low age requirements. Min and max value…
- `min_group_size` (object): Filter by tour's minimum group size. E.g., { min: 1, max: 1 } finds tours that accept solo travelers. Min and max value cannot be this same.
- `operator_ids` (array): Filter tours by specific operator ids. You can add multiple operator ids, then OR operator will be used. For lookup for partner by name, please use algolia-operator-search tool.
- `price` (object): Filter by tour price in the selected currency. E.g., { min: 500, max: 2000, currency: 'EUR' } finds tours priced between €500 and €2000. Min and max value cannot be this same.
- `start_city` (array): City IDs where the tour starts (e.g., [1234, 5678]). Use b2b-cities-search to find city IDs. If passing multiple values, will find tours starting in any of the given cities
- `start_country` (array): Filter by the country where the tour BEGINS (departure point). ISO 3166-1 alpha-2 codes (e.g., ['DE', 'AT']). Multiple values = OR logic. Use 'countries' filter for countries visited during the itine…
- `textSearch` (string, required)
- `tourIds` (array): Filter by specific tour IDs. Use this to narrow search results to known tours.

### `tourradar_vertex-tour-title-search` (~87 tokens)

[tourradar] Search for tours by title using AI-powered semantic search. Returns a list of matching tour IDs and titles. Use this when you need to look up a tour by name. When you know tour id, use b2b-tour-details tool to display details about specific tour

Input parameters:

- `query` (string, required): Tour title or partial title to search for

### `tourradar_vertex-review-search` (~396 tokens)

[tourradar] Search tour reviews using AI-powered semantic search. Requires tourIds to scope results to specific tours. Use this when the user asks about reviews, feedback, or experiences for specific tours. Combine with an optional text query to find reviews mentioning specific topics (e.g., 'food', 'guide', 'accommodation'). When you don't have tour IDs, use vertex-tour-search or vertex-tour-title-search first to find them.

Input parameters:

- `createdAfter` (string): Only return reviews created on or after this date (YYYY-MM-DD). Use to bias toward recent reviews.
- `keywords` (array): Array of keyword phrases to search reviews for. These are joined with OR logic to find reviews matching any of the given topics. Use short phrases (e.g., ['food quality', 'meals', 'restaurant']). Whe…
- `minRating` (number): Only return reviews with a star rating >= this value (1-5). Use to surface only strong reviews.
- `pageSize` (integer): Number of reviews to return (1-20, default 10)
- `pageToken` (string): Token for fetching the next page of results. Use the nextPageToken value from a previous response.
- `query` (string): Short natural language search query to find specific review topics. Keep it concise — do NOT expand into keyword lists. Use simple phrases like 'food quality', 'guide', 'hotel issues'. The search eng…
- `tourIds` (array): Tour IDs to scope reviews to specific tours. Use vertex-tour-title-search to find tour IDs if needed.
- `travelledAfter` (string): Only return reviews whose trip departed on or after this date (YYYY-MM-DD). Use to surface reviews from recent travellers.

### `tourradar_web-ask-question` (~359 tokens)

[tourradar] Use this when the user wants to ASK A QUESTION about a tour or operator WITHOUT committing to a booking.

Two modes:
\- mode "tour": a question about a specific tour. Requires `tourId`. The `departureDate` is OPTIONAL here — if the customer has not picked a date, omit it and the backend will pick the nearest real departure. Do NOT fabricate a date.
\- mode "operator": a general/operator-level question. Requires `operatorId` and no tour.

Always provide the customer's real contact details (email, first/last name; phone optional) and their actual question text. Never fabricate or assume user data — ask for missing information.

Input parameters:

- `agentInformation` (string): Optional agent context about the customer's needs/preferences. Helps Customer Support. The customer's question stays primary; this is appended as extra context.
- `email` (string, required): Customer email address. If email is not given by the customer, please ask before executing this tool. Never generate an email yourself.
- `entity` (required): What the question is about. Pick exactly one mode: "tour" (carries `tourId` + optional departure/pax) or "operator" (carries `operatorId`). A tour question cannot carry an operator id and vice versa.
- `firstName` (string, required): Customer first name.
- `lastName` (string, required): Customer last name.
- `phoneNumber` (string): Customer phone number in E-164 format. Optional but recommended. Never put a fake phone number; if the customer does not provide one, skip this field.
- `question` (string, required): The customer's actual question text. Required and must be non-empty. This is the question the customer wants answered.

### `tourradar_web-tour-booking` (~339 tokens)

[tourradar] Use this when the user explicitly wants to book a tour and has provided their contact details.

Creates a booking request for a specific tour. Requires real contact details (email, names; phone optional). Always confirm the departure date by checking departures first. Never fabricate or assume user data - always ask for missing information.

Input parameters:

- `agentInformation` (string, required): Agent information about the booking. Describe here what customer is looked for, preferences etc, what you can recognize. Will be helpful for our Customer Support team to understand the customer needs.
- `departureDate` (string, required): Departure date, from customer selection
- `email` (string, required): Customer email address. If email is not given by the customer, please ask him before executing this endpoint. Never generate email by yourself, always ask customer for give the email before calling t…
- `extraInformation` (string, required): Customer extra information from the customer or agent. Fill here if customer has provided any additional information about the booking. This is optional and can be empty.
- `firstName` (string, required)
- `lastName` (string, required)
- `paxAdults` (integer, required): Number of the adults. Always ask customer for this information, is important to have it
- `paxChildren` (integer, required): Number of the children
- `phoneNumber` (string): Customer phone number in E-164 format. Is optional, but recommended to provide it. Never put fake phone number, always ask customer for give the phone number before calling this tool. If customer do…
- `tourId` (integer, required): Tour ID

### `tourradar_web-tour-send-brochure` (~138 tokens)

[tourradar] Use this when the user requests a tour brochure or PDF to be sent to their email.

Sends a tour brochure (PDF file) to the specified email address. Before using this, ensure the user has provided their email address. If not provided, ask the user for it. Never generate or assume email addresses.

Input parameters:

- `email` (string, required): User email address. If email is not given by the user, please ask him before executing this endpoint. Never generate email by yourself, always ask user for give the email before calling this tool.
- `tourId` (integer, required): Tour ID

### `tourradar_algolia-operator-search` (~80 tokens)

[tourradar] Use this when you need to find a tour operator's ID by their name for filtering tours.

Searches tour operators by name and returns matching operators with their IDs. Use the returned operator ID with tour search filters.

Input parameters:

- `textSearch` (string, required): Operator name for search, for example `Topdeck`

### `trivago_trivago-accommodation-radius-search` (~530 tokens)

[trivago] Search for accommodations and hotels using coordinates on trivago.

Use this tool when you want to find accommodations near a specific location (landmark, neighborhood, or address).

Additional Information: {"knownInformation":{"currentYear":"2026","today":"2026-08-02"}}

Input parameters:

- `adults` (number): The number of adults.
- `arrival` (string, required): The arrival date in YYYY-MM-DD format, today is 2026-08-02. The arrival date MUST be before the departure date. If the arrival date is not in the future, notify the user that the arrival date i…
- `children` (number): The number of children.
- `children_ages` (string): Dashed separated list of children ages, e.g. 10-12-14
- `country` (string): ISO alpha-2 country code that determines market-specific pricing and content. Default: US.
- `currency` (string): ISO 4217 currency code used to display prices. Default: USD.
- `departure` (string, required): The departure date in YYYY-MM-DD format, today is 2026-08-02. The departure date MUST be after the arrival date. If the departure date is not after the arrival date, notify the user that the de…
- `filters` (object): The filters that you want to apply to the search. Set true or false for each filter. Multiple filters can be selected.
- `hotel_rating` (object): The hotel rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
- `language` (string): Language code for translated content (e.g. EN_US, DE_DE, ZH_HANS_CN). Default: EN_US.
- `latitude` (number, required): Latitude of the search target location (landmark, address, or neighborhood — not the user's location).
- `longitude` (number, required): Longitude of the search target location (landmark, address, or neighborhood — not the user's location).
- `review_rating` (object): The guest review rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
- `rooms` (number): The number of rooms, Number of rooms must be lower than or equal to the number of adults

### `trivago_trivago-accommodation-search` (~471 tokens)

[trivago] Search for accommodations and hotels by destination or point of interest on trivago. Additional Information: {"knownInformation":{"currentYear":"2026","today":"2026-08-02"}}

Input parameters:

- `adults` (number): The number of adults.
- `arrival` (string, required): The arrival date in YYYY-MM-DD format, today is 2026-08-02. The arrival date MUST be before the departure date. If the arrival date is not in the future, notify the user that the arrival date i…
- `children` (number): The number of children.
- `children_ages` (string): Dashed separated list of children ages, e.g. 10-12-14
- `country` (string): ISO alpha-2 country code that determines market-specific pricing and content. Default: US.
- `currency` (string): ISO 4217 currency code used to display prices. Default: USD.
- `departure` (string, required): The departure date in YYYY-MM-DD format, today is 2026-08-02. The departure date MUST be after the arrival date. If the departure date is not after the arrival date, notify the user that the de…
- `filters` (object): The filters that you want to apply to the search. Set true or false for each filter. Multiple filters can be selected.
- `hotel_rating` (object): The hotel rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
- `language` (string): Language code for translated content (e.g. EN_US, DE_DE, ZH_HANS_CN). Default: EN_US.
- `query` (string, required): Destination or point of interest.
- `review_rating` (object): The guest review rating that you want to filter by. Set true or false for each rating. Multiple ratings can be selected.
- `rooms` (number): The number of rooms, Number of rooms must be lower than or equal to the number of adults

### `skiplagged_sk_flights_search` (~572 tokens)

[skiplagged] Search Skiplagged for flights between specific locations with filtering options for passengers, fare class, stops, airlines, and timing preferences

Input parameters:

- `adults` (integer): Number of adult passengers (default: 1, max: 9)
- `arrivalAirports`: Array of specific arrival airport codes to include (when destination city has multiple airports)
- `arrivalTimeEarliest` (integer): Earliest arrival time in minutes from midnight (0-1439)
- `arrivalTimeLatest` (integer): Latest arrival time in minutes from midnight (0-1439)
- `children` (integer): Number of child passengers (default: 0, max: 8)
- `departureAirports`: Array of specific departure airport codes to include (when origin city has multiple airports)
- `departureDate` (string, required)
- `departureTimeEarliest` (integer): Earliest departure time in minutes from midnight (0-1439)
- `departureTimeLatest` (integer): Latest departure time in minutes from midnight (0-1439)
- `destination` (string, required): Arrival location - prefer IATA code
- `excludedAirlines` (array): Array of excluded airline codes (e.g., ['F9', 'NK'])
- `fareClass` (string): Fare class preference (default: economy)
- `includeHiddenCity` (boolean): Include hidden city flights (default: true)
- `includeStandard` (boolean): Include standard flights (default: true)
- `includeVirtualInterlining` (boolean): Include virtual interlining flights (default: true)
- `infantsLap` (integer): Number of lap infants (default: 0, max: 4)
- `infantsSeat` (integer): Number of seat infants (default: 0, max: 4)
- `limit` (integer): Maximum number of flights to return (default: 12, max: 100)
- `maxFlightDuration` (integer): Maximum total flight duration in minutes
- `maxLayoverDuration` (integer): Maximum layover duration in minutes
- `maxStops` (string): Maximum number of stops (none=nonstop, one=1 stop, many=2+ stops)
- `offset` (integer): Number of flights to skip for pagination (default: 0)
- `origin` (string, required): Departure location - prefer IATA code
- `preferredAirlines` (array): Array of preferred airline codes (e.g., ['UA', 'DL'])
- `renderMode` (string): Preferred render mode for tool output (ui or text).
- `returnDate` (string)
- `sort` (string): Sort flights by price (cheapest first), duration (shortest first), or value (best price/time ratio, default)

### `skiplagged_sk_destinations_anywhere` (~166 tokens)

[skiplagged] Find cheapest destinations from a departure city when flexible about where to go. Perfect for discovering travel opportunities and deals.

Input parameters:

- `adults` (integer): Number of adult passengers
- `children` (integer): Number of child passengers
- `depart` (string, required): Departure date in YYYY-MM-DD format
- `fare_class` (string): Fare class preference
- `from` (string, required): Departure IATA code or city name
- `infantsLap` (integer): Number of lap infants
- `infantsSeat` (integer): Number of seat infants
- `renderMode` (string): Preferred render mode for tool output (ui or text).
- `return` (string): Return date in YYYY-MM-DD format (optional for one-way trips)

### `skiplagged_sk_flex_departure_calendar` (~265 tokens)

[skiplagged] Generate a flexible calendar of the lowest one-way fares around a chosen departure, returning date → cheapest-price entries to help pick the best day to fly. Intended for flexible-date price discovery, not exact itinerary selection.

Input parameters:

- `adults` (integer): Number of adult passengers (default: 1, max: 9)
- `children` (integer): Number of child passengers (default: 0, max: 8)
- `departureDate` (string, required): Preferred departure date (YYYY-MM-DD format)
- `destination` (string, required): Arrival city name or IATA code (will be resolved to IATA code automatically)
- `infantsLap` (integer): Number of lap infants (default: 0, max: 4)
- `infantsSeat` (integer): Number of seat infants (default: 0, max: 4)
- `origin` (string, required): Departure city name or IATA code (will be resolved to IATA code automatically)
- `renderMode` (string): Preferred render mode for tool output (ui or text).
- `returnDate`: Return date for matching trip length (optional, YYYY-MM-DD format)
- `sort` (string): Sort results chronologically or by lowest price first

### `skiplagged_sk_flex_return_calendar` (~274 tokens)

[skiplagged] Generate a flexible round-trip price calendar for a fixed-length stay around a chosen travel window. Returns (depart date, return date, lowest total price) entries for nearby date pairs that preserve the original trip length; intended for price discovery, not exact itinerary selection.

Input parameters:

- `adults` (integer): Number of adult passengers (default: 1, max: 9)
- `children` (integer): Number of child passengers (default: 0, max: 8)
- `departureDate` (string, required): Preferred departure date (YYYY-MM-DD format)
- `destination` (string, required): Arrival city name or IATA code (will be resolved to IATA code automatically)
- `infantsLap` (integer): Number of lap infants (default: 0, max: 4)
- `infantsSeat` (integer): Number of seat infants (default: 0, max: 4)
- `origin` (string, required): Departure city name or IATA code (will be resolved to IATA code automatically)
- `renderMode` (string): Preferred render mode for tool output (ui or text).
- `returnDate` (string, required): Return date for the reference trip (YYYY-MM-DD format)
- `sort` (string): Sort results chronologically or by lowest price first

### `skiplagged_sk_hotels_search` (~257 tokens)

[skiplagged] Search Skiplagged for hotels in a city with specific check-in and check-out dates, including ratings and pricing.

Input parameters:

- `checkin` (string, required): Check-in date (YYYY-MM-DD format)
- `checkout` (string, required): Check-out date (YYYY-MM-DD format)
- `city` (string, required): City name to search for hotels (will be matched against available cities)
- `limit` (integer): Maximum number of hotels to return (default: 12, max: 100)
- `numAdults` (integer): Number of adults (default: 2, max: 10)
- `numChildren` (integer): Number of children (default: 0, max: 10)
- `numRooms` (integer): Number of rooms (default: 1, max: 9)
- `offset` (integer): Number of hotels to skip for pagination (default: 0)
- `renderMode` (string): Preferred render mode for tool output (ui or text).
- `sort` (string): Sort hotels by price (cheapest first), ranking (highest rated first), value (best value rating), or discount (best deals first, default when deals available)

### `skiplagged_sk_cars_search` (~213 tokens)

[skiplagged] Search Skiplagged for rental cars between pickup and dropoff locations/dates, returning prices, companies, and car details.

Input parameters:

- `dropoffDate` (string, required): Dropoff date (YYYY-MM-DD)
- `dropoffLocation` (string): Dropoff location (defaults to pickup)
- `dropoffTime` (string): Dropoff time (HH:mm or HH:mm:ss, default 10:00)
- `limit` (integer): Maximum number of car offers to return
- `offset` (integer): Number of car offers to skip for pagination (default: 0)
- `pickupDate` (string, required): Pickup date (YYYY-MM-DD)
- `pickupLocation` (string, required): Pickup location: airport code (preferred) or "lat,lng"
- `pickupTime` (string): Pickup time (HH:mm or HH:mm:ss, default 10:00)
- `renderMode` (string): Preferred render mode for tool output (ui or text).

### `skiplagged_sk_hotel_details` (~192 tokens)

[skiplagged] Fetch room-level availability, pricing, and amenities for a specific hotel and stay dates.

Input parameters:

- `checkin` (string, required): Check-in date (YYYY-MM-DD format)
- `checkout` (string, required): Check-out date (YYYY-MM-DD format)
- `hotelId` (integer, required): Hotel ID (from search results) to fetch detailed availability for
- `live` (boolean): Use live rates (includes booking links). Disable for faster, less accurate cached rates.
- `numAdults` (integer): Number of adults (default: 2, max: 10)
- `numChildren` (integer): Number of children (default: 0, max: 10)
- `numRooms` (integer): Number of rooms (default: 1, max: 5)
- `renderMode` (string): Preferred render mode for tool output (ui or text).

### `skiplagged_sk_faq_search` (~94 tokens)

[skiplagged] Search FAQ for relevant answers about Skiplagged - company, stuff, its products, and policies. Useful for customer support and general inquiries

Input parameters:

- `query` (string, required): The search query for FAQ retrieval
- `renderMode` (string): Preferred render mode for tool output (ui or text).
- `top_k` (integer): Number of top articles to return

### `skiplagged_sk_resolve_location` (~70 tokens)

[skiplagged] Resolve latitude and longitude to the IATA code of nearest airport and city information

Input parameters:

- `lat` (number, required): latitude
- `lng` (number, required): longitude
- `renderMode` (string): Preferred render mode for tool output (ui or text).

### `skiplagged_sk_resolve_iata` (~66 tokens)

[skiplagged] Resolve a city name to a valid IATA code

Input parameters:

- `input` (string, required): City name code to resolve to IATA code
- `renderMode` (string): Preferred render mode for tool output (ui or text).

### `ferryhopper_get_ports` (~25 tokens)

[ferryhopper] Get a list of global ports and their details

### `ferryhopper_get_disruptions` (~88 tokens)

[ferryhopper] Get a list of disruptions for a given date and country

Input parameters:

- `country` (string, required): ISO 3166-1 alpha-2 country code to filter disruptions by country (e.g. "GR" for Greece).
- `tripDate` (string, required): Departure date in ISO format YYYY-MM-DD (e.g. 2026-03-15).

### `ferryhopper_get_direct_connections_for_ports` (~54 tokens)

[ferryhopper] Get a list of all the direct connections between ports

Input parameters:

- `portLocation` (string, required): Location name or search term used to find matching ports (not limited to exact port codes).

### `ferryhopper_search_trips` (~118 tokens)

[ferryhopper] Get a list available ferry trips between two ports on a specific date

Input parameters:

- `arrivalLocation` (string, required): Arrival location as a human-readable name or search term (e.g. city, port name), not a port code.
- `date` (string, required): Departure date in ISO format YYYY-MM-DD (e.g. 2026-03-15).
- `departureLocation` (string, required): Departure location as a human-readable name or search term (e.g. city, port name), not a port code.

### `travel_agent` (~56 tokens)

Ask a travel question in natural language. Routes to the right tools automatically and returns a combined answer. Example: 'Cheapest flights from Zurich to Rome next week, and do I need a visa?'

Input parameters:

- `query` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-08-03: 63
- 2026-08-02: 62
- 2026-08-01: 62
- 2026-07-31: 61
- 2026-07-30: 60
- 2026-07-29: 59
- 2026-07-28: 59
- 2026-07-27: 58
- 2026-07-26: 57

## Links

- Remote endpoint: https://mcp.moltravel.com/mcp
- Repository: https://github.com/navifare/moltravel-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-moltravel-travel/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-moltravel-travel/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-moltravel-travel/mcp