MolTravel
REMOTE · MCP.MOLTRAVEL.COM · SCANNED SEP 25
Aggregated travel MCP — flights, tours, activities, price checks, visas, and more.
Available components
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 Security60
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 56 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 10723 tokens (~191/item across 56 items; 56 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
- Structured output schemas are declared (21% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "tourradar_web-tour-send-brochure" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 57 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the MolTravel MCP server?
MolTravel is a hosted endpoint at https://mcp.moltravel.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 · mcp.moltravel.com
claude mcp add --transport http com-moltravel-travel 'https://mcp.moltravel.com/mcp'
{
"mcpServers": {
"com-moltravel-travel": {
"url": "https://mcp.moltravel.com/mcp"
}
}
} {
"servers": {
"com-moltravel-travel": {
"type": "http",
"url": "https://mcp.moltravel.com/mcp"
}
}
} [mcp_servers.com-moltravel-travel] url = "https://mcp.moltravel.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-moltravel-travel": {
"type": "remote",
"url": "https://mcp.moltravel.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-moltravel-travel --url 'https://mcp.moltravel.com/mcp' --transport streamable-http
mcp_servers:
com-moltravel-travel:
url: "https://mcp.moltravel.com/mcp" {
"McpServers": {
"com-moltravel-travel": {
"Transport": "http",
"Url": "https://mcp.moltravel.com/mcp"
}
}
} assistant mcp add com-moltravel-travel -t streamable-http -u 'https://mcp.moltravel.com/mcp'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 19 Sept 26 0
- Stability: fail → pass ▲ security
- 15 Sept 26 0
- 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 security
- Tool “trivago_trivago-destination-price-trends” rewrote its description, which is the text the model reads security
- Server version: 1.26.0 → 1.30.0 functional
- “trivago_trivago-accommodation-radius-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-radius-search” reworded the description of “departure” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “departure” cosmetic
- 14 Sept 26 0
- 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 security
- Tool “trivago_trivago-destination-price-trends” rewrote its description, which is the text the model reads security
- “trivago_trivago-accommodation-radius-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-radius-search” reworded the description of “departure” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “departure” cosmetic
- 11 Sept 26 0
- 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 security
- Tool “trivago_trivago-destination-price-trends” rewrote its description, which is the text the model reads security
- “trivago_trivago-accommodation-radius-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-radius-search” reworded the description of “departure” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “departure” cosmetic
- 9 Sept 26 0
- 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 security
- Tool “trivago_trivago-destination-price-trends” rewrote its description, which is the text the model reads security
- “trivago_trivago-accommodation-radius-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-radius-search” reworded the description of “departure” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “departure” cosmetic
- 6 Sept 26 0
- 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 security
- Tool “trivago_trivago-destination-price-trends” rewrote its description, which is the text the model reads security
- “trivago_trivago-accommodation-radius-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-radius-search” reworded the description of “departure” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “departure” cosmetic
- 4 Sept 26 0
- 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 security
- Tool “trivago_trivago-destination-price-trends” rewrote its description, which is the text the model reads security
- “trivago_trivago-accommodation-radius-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-radius-search” reworded the description of “departure” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “arrival” cosmetic
- “trivago_trivago-accommodation-search” reworded the description of “departure” cosmetic
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 25 Sept 2026 · Probed https://mcp.moltravel.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.moltravel.com | CN=WE1,O=Google Trust Services,C=US | 26 Aug 2026 | 24 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 890c854f6a1b3f9d0e1c3a7cda4ad600 |
| SANs: mcp.moltravel.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 secure
Validation of mcp.moltravel.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| moltravel.com. | present | 22784 | 13 | Verified |
| mcp.moltravel.com. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.moltravel.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.moltravel.com/mcp | HTTPS enforced | 301 | https://mcp.moltravel.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 →
airlines_lookup ~35
Look up an airline by IATA (2-char) or ICAO (3-char) code.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
airlines_search ~40
Search airlines by name. Returns up to 20 results.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| country | – | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
airports_lookup ~42
Look up an airport by IATA (3-char) or ICAO (4-char) code. Returns full details including runways.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
airports_near ~60
Find airports near a geographic point. Returns results sorted by distance.
| Name | Type | Req | Description |
|---|---|---|---|
| include_small | boolean | – | – |
| latitude | number | yes | – |
| limit | integer | – | – |
| longitude | number | yes | – |
| radius_km | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
airports_search ~43
Search airports by name or city. Returns up to 20 results sorted by size.
| Name | Type | Req | Description |
|---|---|---|---|
| country | – | – | – |
| query | string | yes | – |
| type_filter | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
data_status ~27
Check which static datasets (airports, airlines, visas) are loaded and their row counts.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
fcdo_list_countries ~26
[fcdo] List all countries with UK FCDO travel advice.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
fcdo_travel_advice ~46
[fcdo] Get UK FCDO travel advice for a specific country. Includes safety, entry requirements, health, and warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ferryhopper_get_direct_connections_for_ports ~63
[ferryhopper] Find all direct ferry routes and reachable destination ports from a given origin port without layovers or transfers.
| Name | Type | Req | Description |
|---|---|---|---|
| portLocation | string | yes | Location name or search term used to find matching ports (not limited to exact port codes). |
No output schema declared.
No examples provided.
ferryhopper_get_disruptions ~97
[ferryhopper] Find all ferry travel disruptions, including delays, weather alerts, and strikes for a given date and country.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | ISO 3166-1 alpha-2 country code to filter disruptions by country (e.g. "GR" for Greece). |
| tripDate | string | yes | Departure date in ISO format YYYY-MM-DD (e.g. 2026-03-15). |
No output schema declared.
No examples provided.
ferryhopper_get_ports ~34
[ferryhopper] Find ferry ports, harbors, maritime terminals, port IDs, codes, and geographic locations.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
ferryhopper_search_trips ~145
[ferryhopper] Deprecated: prefer search_trips_v2, which covers this tool plus round-trip search and per-segment availability flags. Get a list of available one-way ferry trips between two ports on a specific date.
| Name | Type | Req | Description |
|---|---|---|---|
| arrivalLocation | string | yes | Arrival location as a human-readable name or search term (e.g. city, port name), not a port code. |
| date | string | yes | Departure date in ISO format YYYY-MM-DD (e.g. 2026-03-15). |
| departureLocation | string | yes | Departure location as a human-readable name or search term (e.g. city, port name), not a port code. |
No output schema declared.
No examples provided.
ferryhopper_search_trips_v2 ~183
[ferryhopper] Get a list of available ferry trips between two ports on a specific date. Supports round-trip searches when a return date is provided. Availability flags (cabin, vehicles, pets, e-ticket) are reported per segment.
| Name | Type | Req | Description |
|---|---|---|---|
| arrivalLocation | string | yes | Arrival location as a human-readable name or search term (e.g. city, port name), not a port code. |
| date | string | yes | Departure date in ISO format YYYY-MM-DD (e.g. 2026-03-15). |
| departureLocation | string | yes | Departure location as a human-readable name or search term (e.g. city, port name), not a port code. |
| returnDate | string | – | Return date in ISO format YYYY-MM-DD. When provided, the search returns round-trip booking solutions pairing an outbound and return trip. |
No output schema declared.
No examples provided.
ferryhopper_trip_details ~368
[ferryhopper] Get full details for a single sailing leg, looked up by the tripId returned by search_trips_v2. Returns the trip's departure/arrival time, ports, and operating company, plus the vessel's technical specs, onboard amenities, and photos. Use this to answer questions about a vessel such as: does it have wifi / a restaurant / a snack bar / an open deck / a lift or elevator / wheelchair or disabled access / a designated smoking area? Is it pet-friendly, or does it allow pets on board? Does it have cabins, or a garage / vehicle deck for cars and motorbikes? How many passengers or vehicles does it carry (capacity)? How long is the vessel (length in meters)? What is its IMO number or MMSI (maritime identification numbers used for registry/tracking lookups)? Is this vessel accessible, family-friendly, or suitable for passengers who need mobility assistance? What does the vessel look like (photos)? If no detailed specs exist for the vessel in the source system, vessel.hasDetails is returned as false and every spec/amenity field is null — this means the data is unavailable, not that the vessel lacks that amenity. Also returns the trip's bookable accommodation tiers (seat/cabin classes) with their price and a photo of that accommodation, when available. Throws if the tripId is malformed or the trip is no longer bookable (e.g. it has already departed, was cancelled, or sold out) — re-run search_trips_v2 to get a fresh tripId in that case.
| Name | Type | Req | Description |
|---|---|---|---|
| tripId | string | yes | The trip identifier for a single sailing leg, as returned in tripsById/bookingSolutions by search_trips_v2. Do not fabricate this value. |
No output schema declared.
No examples provided.
peek_experience_availability ~117
[peek] Get availability information for a specific experience including dates, times, and pricing
| Name | Type | Req | Description |
|---|---|---|---|
| endDate | string | yes | 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 | yes | The ID of the experience |
| quantity | integer | yes | Number of travelers |
| startDate | string | yes | Start date inclusive YYYY-MM-DD format (e.g., '2025-06-19') |
No output schema declared.
No examples provided.
peek_experience_details ~37
[peek] Get detailed information about a specific experience by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The ID of the experience to retrieve |
No output schema declared.
No examples provided.
peek_list_tags ~17
[peek] List all category tags
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
peek_render_activity_tiles ~50
[peek] Render activity tiles for a list of activity IDs, returning an embeddable widget URI
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID or comma separate list of activity IDs to render as tiles |
No output schema declared.
No examples provided.
peek_search_experiences ~328
[peek] Search for travel experiences with comprehensive filtering options. Returns available categories, tags, and regions with IDs for further filtering.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
peek_search_regions ~50
[peek] Search for regions by name
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of regions to return (default: 50) |
| query | string | yes | Search query to match against region names |
No output schema declared.
No examples provided.
restcountries_country_info ~42
[restcountries] Look up country information from REST Countries.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | – | – | – |
| query | string | yes | – |
| search_by | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
skiplagged_sk_cars_search ~184
[skiplagged] Search Skiplagged for rental cars between pickup and dropoff locations/dates, returning prices, companies, and car details.
| Name | Type | Req | Description |
|---|---|---|---|
| dropoffDate | – | yes | Dropoff date (YYYY-MM-DD) |
| dropoffLocation | – | – | Dropoff city or airport code (defaults to pickup) |
| dropoffTime | – | – | 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 | yes | Pickup date (YYYY-MM-DD) |
| pickupLocation | string | yes | Pickup city or airport code |
| pickupTime | string | – | Pickup time (HH:mm or HH:mm:ss, default 10:00) |
No output schema declared.
No examples provided.
skiplagged_sk_destinations_anywhere ~142
[skiplagged] Find lower-priced destinations from a departure city when the user is flexible about where to go.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Number of adult passengers |
| children | integer | – | Number of child passengers |
| depart | string | yes | Departure date in YYYY-MM-DD format |
| fare_class | string | – | Fare class preference |
| from | string | yes | Departure IATA code or city name |
| infantsLap | integer | – | Number of lap infants |
| infantsSeat | integer | – | Number of seat infants |
| return | – | – | Return date in YYYY-MM-DD format (optional for one-way trips) |
No output schema declared.
No examples provided.
skiplagged_sk_faq_search ~83
[skiplagged] Search Skiplagged support articles for answers about its services, products, and policies.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Concise FAQ question for retrieval. Do not include personal identifiers, account IDs, or session details. |
| top_k | integer | – | Number of top FAQ sources to return (1-5) |
No output schema declared.
No examples provided.
skiplagged_sk_flex_departure_calendar ~247
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Number of adult passengers (default: 1, max: 9) |
| children | integer | – | Number of child passengers (default: 0, max: 8) |
| departureDate | string | yes | Preferred departure date (YYYY-MM-DD format) |
| destination | string | yes | 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 | yes | Departure city name or IATA code (will be resolved to IATA code automatically) |
| returnDate | – | – | Return date for matching trip length (optional, YYYY-MM-DD format) |
| sort | string | – | Sort results chronologically or by lowest price first |
No output schema declared.
No examples provided.
skiplagged_sk_flex_return_calendar ~254
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Number of adult passengers (default: 1, max: 9) |
| children | integer | – | Number of child passengers (default: 0, max: 8) |
| departureDate | string | yes | Preferred departure date (YYYY-MM-DD format) |
| destination | string | yes | 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 | yes | Departure city name or IATA code (will be resolved to IATA code automatically) |
| returnDate | – | yes | Return date for the reference trip (YYYY-MM-DD format) |
| sort | string | – | Sort results chronologically or by lowest price first |
No output schema declared.
No examples provided.
skiplagged_sk_flights_search ~552
[skiplagged] Search Skiplagged for flights between specific locations with filtering options for passengers, fare class, stops, airlines, and timing preferences
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| departureTimeEarliest | integer | – | Earliest departure time in minutes from midnight (0-1439) |
| departureTimeLatest | integer | – | Latest departure time in minutes from midnight (0-1439) |
| destination | string | yes | 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 | yes | Departure location - prefer IATA code |
| preferredAirlines | array | – | Array of preferred airline codes (e.g., ['UA', 'DL']) |
| returnDate | – | – | – |
| sort | string | – | Sort flights by price (cheapest first), duration (shortest first), or value (best price/time ratio, default) |
No output schema declared.
No examples provided.
skiplagged_sk_hotel_details ~172
[skiplagged] Fetch room-level availability, pricing, and amenities for a specific hotel and stay dates.
| Name | Type | Req | Description |
|---|---|---|---|
| checkin | string | yes | Check-in date (YYYY-MM-DD format) |
| checkout | – | yes | Check-out date (YYYY-MM-DD format) |
| hotelId | integer | yes | 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) |
No output schema declared.
No examples provided.
skiplagged_sk_hotels_search ~237
[skiplagged] Search Skiplagged for hotels in a city with specific check-in and check-out dates, including ratings and pricing.
| Name | Type | Req | Description |
|---|---|---|---|
| checkin | string | yes | Check-in date (YYYY-MM-DD format) |
| checkout | – | yes | Check-out date (YYYY-MM-DD format) |
| city | string | yes | 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) |
| 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) |
No output schema declared.
No examples provided.
skiplagged_sk_resolve_iata ~48
[skiplagged] Resolve a city name to a valid IATA code
| Name | Type | Req | Description |
|---|---|---|---|
| input | string | yes | City name code to resolve to IATA code |
No output schema declared.
No examples provided.
skiplagged_sk_resolve_location ~40
[skiplagged] Resolve coarse location metadata supplied by the client to the nearest airport. Takes no user-provided arguments.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tourradar_algolia-operator-search ~80
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| textSearch | string | yes | Operator name for search, for example `Topdeck` |
No output schema declared.
No examples provided.
tourradar_b2b-cities-search ~198
[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).
| Name | Type | Req | Description |
|---|---|---|---|
| country_code | string | yes | ISO 3166-1 alpha-2 country code (e.g., 'US' for USA, 'GB' for United Kingdom, 'DE' for Germany). |
| search | array | yes | 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… |
No output schema declared.
No examples provided.
tourradar_b2b-continents-list ~53
[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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tourradar_b2b-countries-list ~57
[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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tourradar_b2b-currencies-list ~59
[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 ($, €).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tourradar_b2b-languages-list ~56
[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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tourradar_b2b-operator-details ~65
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| operatorId | integer | yes | – |
No output schema declared.
No examples provided.
tourradar_b2b-tour-departures ~149
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Returns only departure dates in the desired range |
| page | integer | – | Page number. Default is 1 |
| tourId | integer | yes | Tour ID |
No output schema declared.
No examples provided.
tourradar_b2b-tour-details ~102
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
tourradar_b2b-tour-faq ~88
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number. Default is 1 |
| tourId | integer | yes | – |
No output schema declared.
No examples provided.
tourradar_b2b-tour-map ~112
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
tourradar_b2b-tour-types-list ~58
[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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tourradar_general-current-date ~55
[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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
tourradar_vertex-review-search ~396
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
tourradar_vertex-tour-search ~1,985
[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…
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| tourIds | array | – | Filter by specific tour IDs. Use this to narrow search results to known tours. |
No output schema declared.
No examples provided.
tourradar_vertex-tour-title-search ~87
[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
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Tour title or partial title to search for |
No output schema declared.
No examples provided.
tourradar_web-ask-question ~359
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| string | yes | Customer email address. If email is not given by the customer, please ask before executing this tool. Never generate an email yourself. | |
| entity | – | yes | 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 | yes | Customer first name. |
| lastName | string | yes | 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 | yes | The customer's actual question text. Required and must be non-empty. This is the question the customer wants answered. |
No output schema declared.
No examples provided.
tourradar_web-tour-booking ~339
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentInformation | string | yes | 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 | yes | Departure date, from customer selection |
| string | yes | 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 | yes | 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 | yes | – |
| lastName | string | yes | – |
| paxAdults | integer | yes | Number of the adults. Always ask customer for this information, is important to have it |
| paxChildren | integer | yes | 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 | yes | Tour ID |
No output schema declared.
No examples provided.
tourradar_web-tour-send-brochure ~138
[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.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | 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 | yes | Tour ID |
No output schema declared.
No examples provided.
What is the MolTravel MCP server?
MolTravel is an MCP server listed in the public MCP registry as com.moltravel/travel. Aggregated travel MCP, flights, tours, activities, price checks, visas, and more. This page covers its hosted endpoint (https://mcp.moltravel.com/mcp).
Is the MolTravel MCP server safe to use?
MolTravel scores 75 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 MolTravel MCP server expose?
MolTravel exposes 56 tools: restcountries_country_info, fcdo_travel_advice, fcdo_list_countries, airports_lookup, airports_search, and 51 more. Their descriptions and schemas cost roughly 9,927 tokens of context every time the server is loaded.
Does the MolTravel MCP server require authentication?
No. We connected to MolTravel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MolTravel MCP server still maintained?
MolTravel is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.