# Vuelo Travel (remote · mcp.getvuelo.com)

Search and book live flights and hotels. No API key; the traveller confirms on their phone.

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

## Components

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

## Channel facts

- Endpoint: `https://mcp.getvuelo.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (cancel_booking).
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 37/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 6057 tokens (~263/item across 23 items; 21 tools + 2 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Vuelo Travel MCP server?

Vuelo Travel is a hosted endpoint at https://mcp.getvuelo.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

```json
{
  "mcpServers": {
    "com-getvuelo-travel": {
      "url": "https://mcp.getvuelo.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

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

### 2026-11-03 (score 62, +1)

- [functional] New tool “get_flight_extras”
- [cosmetic] “book_trip” added an optional parameter “extras”
- [cosmetic] “search_trips” added an optional parameter “airline”
- [cosmetic] “search_trips” added an optional parameter “directOnly”

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

- [security] Tool “find_my_booking” rewrote its description, which is the text the model reads
- [security] Tool “get_booking” rewrote its description, which is the text the model reads
- [security] Tool “request_change” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 4710 → 5769
- [functional] New tool “follow_up_ticket”
- [functional] New tool “list_my_bookings”
- [functional] New tool “send_receipt”
- [cosmetic] “find_my_booking” added an optional parameter “country”
- [cosmetic] “get_support_ticket” added an optional parameter “mobile”
- [cosmetic] “find_my_booking” reworded the description of “mobile”
- [cosmetic] “find_my_booking” reworded the description of “reference”
- [cosmetic] “find_my_booking” made “reference” optional

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

- [functional regression] Schema quality: 4262 → 4710
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “get_booking”
- [functional] New tool “request_change”

### 2026-10-29 (score 59)

First indexed and scored.

## MCP tools (21)

### `search_trips` (~1022 tokens)

Search Vuelo trips

Find hotels, flights and flight-and-hotel packages on Vuelo for a destination, dates and number of travellers, within a budget. The results appear in the Vuelo card, where the traveller compares and books them: do not follow up with a question asking which one they want. Hotels are live; pass origin and destinationAirport (IATA codes) to include flights and packages. Flight fares are live and ticketed at purchase. Pass cabin for premium economy, business or first. Returns prices, photos and the payment options Vuelo offers for each trip. Show payment options exactly as returned and always show the full price. Call it ONCE for what the traveller asked: every call shows another Vuelo card in the chat. Do not run extra searches for other towns, dates or budgets on your own; if the request is broad ("somewhere near London"), pick the best single destination or ask the traveller, and search again only when they ask for something different.

Input parameters:

- `airline` (string): Flights: an airline the traveller names ("Virgin", "BA"): its flights are listed first. A name or its two-letter code.
- `budget` (number): Maximum total in pounds
- `cabin` (string): Which cabin to price flights in, when the traveller asks for one ("business class", "premium economy", "first"). Economy when not said. Only affects flights and packages.
- `destination` (string, required): Town or city, with its country when the name is shared or could be ambiguous: "Lisbon", "Zurich, Switzerland", "Cambridge, UK". A region (the Cotswolds) cannot be searched: use one town in it.
- `destinationAirport` (string): Arrival airport for the destination, for example LIS for Lisbon; for a city with several airports (London, Paris, New York, Milan, Rome, Tokyo, Stockholm) pass the city to search them all.
- `directOnly` (boolean): Flights: only nonstop flights, when the traveller asks for direct or nonstop.
- `from` (string, required): Check-in date, YYYY-MM-DD
- `hotel` (string): The hotel, when the traveller names one ("the Pulitzer", "The Savoy"): its name only, with the town in destination. Vuelo finds it by name and lists it first, with other hotels in the town after it.…
- `minStars` (integer): Minimum hotel star rating, when the traveller asks for one (for example 5 for "5-star").
- `mobile` (string): The traveller's mobile number (any country; international format such as +1 415 555 2671 outside the UK), whenever you already know it from this conversation or about the user. Always pass it if you…
- `only` (string): What the traveller asked for. Set "flights" whenever they ask for flights and not a hotel (for example "find me flights to Nice"), "stays" for a hotel only, "packages" for flight and hotel together.…
- `origin` (string): Where they fly from, to include live flights and packages: an airport code (LHR) or, when the traveller names a city, the city (London, or LON), which searches every airport there (Heathrow, Gatwick,…
- `passengers` (array): Pass this whenever you know it: the results page and checkout then need nothing typed. Who is flying, if the traveller has already told you or you know it: full names as on the passport, and dates of…
- `refundableOnly` (boolean): Only stays with a refundable rate, when the traveller asks for refundable or free cancellation. Flights are ticketed at booking, so none are refundable.
- `to` (string, required): Check-out or return date, YYYY-MM-DD. For a one-way flight, give the same date as from.
- `traveller` (object): The person booking, whenever you know them from this conversation or about the user: full name as on their ID, email, date of birth (YYYY-MM-DD) and home postcode. Vuelo keeps them for this conversat…
- `travellers` (integer, required): Number of travellers

### `get_hotel_availability` (~244 tokens)

Check one hotel on Vuelo

Live rooms and prices at ONE hotel the traveller already has in mind, for their dates and number of guests, without searching the whole town. Pass the reference you hold: a Vuelo hotel link (https://…/h/…), an offerId from an earlier Vuelo search, a Vuelo property_id (VHP_…) or a hotel id from a Vuelo search. Use it when the traveller shares a Vuelo hotel link or asks about the same hotel on other dates. The result appears in the Vuelo card. No result means the hotel has nothing for those dates or is not one Vuelo can sell: say so, and offer to search the town. Prices hold for about an hour: book soon after, or check again.

Input parameters:

- `from` (string, required): Check-in date, YYYY-MM-DD
- `property` (string, required): The hotel: a Vuelo hotel link, an offerId from a Vuelo search, a Vuelo property_id (VHP_…) or a hotel id from a Vuelo search.
- `to` (string, required): Check-out date, YYYY-MM-DD
- `travellers` (integer, required): Number of adults

### `get_offer` (~35 tokens)

Get a Vuelo offer

Details, terms, photos and the payment options for one Vuelo offer, repriced live.

Input parameters:

- `offerId` (string, required)

### `get_flight_extras` (~180 tokens)

Bags and seats for a flight

For a flight offer from search_trips, when the traveller asks about luggage or seats, or before book_trip if they want an extra bag: what the fare includes, the extra bags on sale (each with a choice_id, for which passenger by position, which way, its price and the most allowed), and for each flight how many seats can be chosen and their price range. To add bags, pass extras: [{ choice_id, quantity }] to book_trip; the traveller sees them ticked on the booking page and can change them. Seats are chosen by the traveller on the booking page, from the seat map, never here. Bags and seats cannot be added through Vuelo after booking. Prices are as listed now; the booking page shows the total.

Input parameters:

- `offerId` (string, required): A flight offerId from search_trips

### `change_package_flight` (~106 tokens)

Other flights for a package

For a flight-and-hotel package from search_trips: every other flight for the same route and dates, each priced as a package with the same stay, with what it costs each traveller more or less than the current flight. The Vuelo card uses this for its Change flight list; call it yourself when the traveller asks for other flights for a package, then book the offerId they choose.

Input parameters:

- `offerId` (string, required): The package offerId from search_trips

### `book_trip` (~1239 tokens)

Book a Vuelo trip

Bookings are made under Vuelo's Booking Terms and Conditions (https://getvuelo.com/uk/legal/terms-of-booking-service/); the Vuelo card and pay page show them. Start booking a Vuelo offer, by the offerId and paymentOption that search_trips returned; call it whenever the traveller asks in the chat to book one. The Vuelo card then shows the traveller a Pay button that opens Vuelo's secure page (Apple Pay, Google Pay or a card), or, where there is no card or they ask for one, Vuelo texts them a secure link; nothing is booked until they pay. Never show a link in the chat, except a passkey approval link Vuelo returns for you to show. Pre-fill: pass everything you already know about the traveller, from this conversation or what you know about the user, so checkout is a single tap with nothing to type: leadTraveller (full name as on their ID, email, date of birth, home postcode), mobile, and for flights each passenger's name, date of birth, title and gender. Never guess or invent any of it; ask only for what Vuelo says is missing, once, in one message. Flights cannot book without each passenger's name and date of birth. To change how an open booking is paid for, use change_payment_option (calling book_trip again with another paymentOption does the same). Do not wait for the traveller to tell you they have paid: pass notify_url to hear the moment they open the link, pay or cancel, or straight after sending the link call get_booking_status with wait_seconds: 50, which answers the moment they pay. Then tell them it is booked, with the reference.

Input parameters:

- `consumer_ref` (string): The vc_ reference Vuelo gave you after this traveller authorised you to book for them within limits. Only if you already hold one; never ask the traveller for it, or mention it to them: they do not h…
- `conversationId` (string)
- `delivery` (string): How the confirmation reaches the traveller. Leave it out: a card payment always goes by text to the traveller's mobile, and a no-card reservation by a Confirm button in the Vuelo card. qr and on_devi…
- `extras` (array): A flight only: extra bags the traveller asked for, by choice_id from get_flight_extras. They are ticked on the booking page for the traveller to check before paying; seats are chosen there. Leave out…
- `from_card` (boolean): Set only by the Vuelo card. Leave it out.
- `host` (string): Which assistant this is, so the Vuelo page names it and matches its look. One of: chatgpt, claude, gemini, meta, instinct, openclaw, perplexity, copilot, mistral, grok, poe, duckduckgo. Optional, and…
- `leadTraveller` (object): The traveller booking: name, email, date of birth and home postcode, town and county, as far as you know them. Pass whatever you already know from this conversation or about the user rather than aski…
- `mobile` (string): Mobile number to text the link to (any country; international format outside the UK). Not needed for returning customers, or if you already passed it to search_trips in this conversation. If you alre…
- `notify_token` (string): A secret of yours. Vuelo sends it back in X-Vuelo-Notify-Token and signs the event with it (X-Vuelo-Signature: sha256=HMAC). Optional.
- `notify_url` (string): Your own https address. The moment the traveller confirms on their phone, Vuelo POSTs it a booking.confirmed event (reference, trip, dates, amount), so you can tell them without being asked. Optional.
- `offerId` (string, required)
- `payer` (object): Only when the traveller says someone else is paying (a friend, a partner, a parent): their name and mobile or email, as the traveller gives them. Vuelo then sends the secure link to that person inste…
- `paymentOption` (string, required): One of the options search_trips returned as eligible
- `travellers` (array): Each passenger, as on their passport, with their title and gender where you know them (airlines need both). If the traveller has already told you who is flying, pass them rather than making them type…
- `travellersConfirmed` (boolean): Set true when the traveller has confirmed the passengers Vuelo filled in and named back to you. Vuelo asks for this once, before it starts a booking with saved passengers.

### `get_booking_progress` (~39 tokens)

Vuelo booking progress

Progress of the newest booking for an offer, or the newest booking of all, for the Vuelo widget.

Input parameters:

- `offerId` (string)

### `change_payment_option` (~90 tokens)

Change how a Vuelo booking is paid for

When the traveller wants to pay a different way (for example reserve now instead of paying in full) before they have confirmed. Switches the open booking to that paymentOption; the link already texted stays the same and opens with the new choice, so nothing new is sent. Only an option the trip lists as available.

Input parameters:

- `paymentOption` (string, required)
- `taskId` (string, required)

### `update_travellers` (~184 tokens)

Correct passengers on a Vuelo booking

Correct who is travelling on a booking the traveller has not paid for yet: a passenger's name or date of birth (names exactly as on the passport, dates YYYY-MM-DD). Give only what changes, by position: { passenger: 2, name: "Sophie Hougham", dateOfBirth: "1990-04-12" }. What you leave out stays as it was. The link already sent opens with the new names; nothing is resent. Refused once the traveller has paid: names on a ticket are changed with the airline through Vuelo support.

Input parameters:

- `leadTraveller` (object): The booking traveller's email, date of birth and home postcode, town and county, to fill in their Vuelo account on the pay page.
- `taskId` (string, required): The taskId book_trip returned.
- `travellers` (array)

### `resend_link` (~102 tokens)

Text the Vuelo link again

When the traveller says the secure link has not arrived, or asks for another: Vuelo texts it again, to the same number. The first time it resends the same link; after that, once it has been opened, or once it has expired, Vuelo cancels it and texts a fresh one, and only the newest works. Never pass the link on in the chat yourself. At most three links a booking.

Input parameters:

- `taskId` (string, required)

### `send_to_payer` (~246 tokens)

Send the pay link to someone else to pay

After a booking has started, when the traveller says someone else is paying (a friend, a partner, a parent, their company); if you know before booking, pass payer to book_trip instead. Vuelo sends that person a secure link of their own, by text, email or both. Only when the traveller asks, with the name and the mobile or email they give you: never guess or reuse a number, and confirm it with the traveller first. The payer sees the trip, the price and who asked, never the traveller's own details, and pays in full from their own Vuelo account (no payment plan). The traveller's own link stops working, so the trip cannot be paid twice; the traveller still gets the booking confirmation. The link lasts 24 hours and the price is checked when they pay. Never pass the link on in the chat yourself.

Input parameters:

- `email` (string): Their email, to email the link.
- `mobile` (string): Their mobile, to text the link.
- `name` (string, required): The name of the person paying, as the traveller gave it.
- `taskId` (string, required): The taskId book_trip returned.

### `cancel_booking` (~328 tokens)

Cancel a Vuelo booking

Cancel a Vuelo booking, before or after the traveller confirms. Pass the taskId if it was made in this conversation; from any other conversation, a made booking can be cancelled with its Vuelo reference (VU-...) and the email or mobile it was booked with. Not confirmed yet: it is called off at once, the texted link stops working and nothing was charged. Already booked: call it first with preview: true and tell the traveller what they would get back (refund.amount, summary). If they want to go ahead, call it again without preview. A reservation with nothing paid is cancelled at once. For anything paid, Vuelo texts the traveller a six-digit code and nothing is cancelled until it is given: ask them for it and call again with code (they can also enter it on their booking page). Never guess a code, and never say a paid booking is cancelled until this or get_booking_status says so.

Input parameters:

- `code` (string): For a paid booking: the six-digit code Vuelo texted the traveller, as they gave it to you. Finishes the cancellation and the refund.
- `email` (string): With reference: the email the traveller booked with.
- `mobile` (string): With reference, instead of email: the mobile on the booking.
- `preview` (boolean): true: only say what cancelling would refund, changing nothing.
- `reference` (string): Otherwise: the Vuelo booking reference (VU-...).
- `taskId` (string): The taskId book_trip returned, when the booking was made in this conversation.

### `contact_support` (~297 tokens)

Contact Vuelo support

Send the traveller's request to Vuelo's support team, who will be in touch with them. Use it whenever the traveller wants something done to a Vuelo booking that the other tools cannot do, or wants a person: change dates or names after paying, a refund question, a payment problem, a complaint, anything. It works in any conversation: pass the taskId if the booking was made in this chat; otherwise their Vuelo booking reference (VU-...) and the email or mobile they booked with, or just their email if they have no reference. To cancel a booking made in this chat, use cancel_booking first: it raises the request itself when Vuelo's team has to do it. Write the message in the traveller's words, with what they want and why. Tell them the ticket reference and reply time this returns.

Input parameters:

- `email` (string): The email the traveller booked with: needed when there is no taskId, or when this tool asks for it.
- `message` (string, required): What the traveller wants, in their words.
- `mobile` (string): With reference, instead of email: the mobile on the booking.
- `reference` (string): The Vuelo booking reference (VU-...), when there is no taskId.
- `taskId` (string): The taskId book_trip returned, when the booking was made in this conversation.
- `topic` (string, required): What the request is about.

### `find_my_booking` (~340 tokens)

Send the traveller their booking page

For a traveller who booked with Vuelo before, in another conversation, and wants to see, change, cancel or get help with it: Vuelo texts the booking's own page to the mobile on that booking. On that page they can cancel, add it to their calendar, and contact Vuelo's team. Pass their Vuelo booking reference (VU-...) and the email or mobile they booked with. If they do not have the reference, pass the mobile they booked with alone (with country if it is not written with +): Vuelo texts that number a link to each of its latest bookings. You never see a link or whether anything matched, so tell them: if the details match, Vuelo has texted the mobile on the booking. They can also see every booking on their mobile at Vuelo's bookings page (/bookings on the site their booking links open), with a code texted to it. Never search their email or messages for a reference instead: ask for the mobile. For anything else they want a person for, use contact_support.

Input parameters:

- `country` (string): For a mobile typed the local way (06 12 34 56 78), the country it is from, as an ISO code (FR). Not needed for a number with +.
- `email` (string): The email the traveller booked with.
- `mobile` (string): The mobile on the booking: with the reference instead of the email, or alone without the reference.
- `reference` (string): The Vuelo booking reference, VU-... Leave out if the traveller does not have it, and pass the mobile alone.

### `list_my_bookings` (~300 tokens)

The traveller's Vuelo bookings

For a traveller who wants to manage a booking here, in the chat, and does not have its reference: every booking on the mobile they booked with. Two calls. First pass the mobile alone (with country if it is not written with +): Vuelo texts that number a 6-digit code, and the answer is the same whether or not it has bookings. Ask the traveller for the code, then call again with the same mobile and the code: you get each booking's reference, what it is, its dates, its status (booked, reserved, cancelled, awaiting_payment, payment_link_expired), and the date to pay by or to cancel free by. Show them the list and ask which one. Then use get_booking, cancel_booking or request_change with that reference and this mobile. Never names, dates of birth or booking pages. If the code is not right, ask them to check the text; after five wrong tries, call again without the code for a new one.

Input parameters:

- `code` (string): The 6-digit code Vuelo texted, once the traveller has read it out. Leave out on the first call.
- `country` (string): For a mobile typed the local way (06 12 34 56 78), the country it is from, as an ISO code (FR). Not needed for a number with +.
- `mobile` (string, required): The mobile the traveller booked with.

### `send_receipt` (~196 tokens)

Email the traveller their receipt

When the traveller asks for a receipt, an invoice or proof of a booking: Vuelo emails it to the email on the booking (never to an address you give), with what was booked, the dates, and the money as it stands: paid, reserved with the date it is due, on a payment plan, or cancelled with its refund. You do not see the receipt. Pass the Vuelo reference (VU-...) and the email or mobile it was booked with, or the taskId of a booking made in this conversation. If the booking has no email, it says so: then use contact_support.

Input parameters:

- `email` (string): The email the traveller booked with.
- `mobile` (string): Or the mobile on the booking.
- `reference` (string): The Vuelo booking reference, VU-...
- `taskId` (string): The booking's taskId, if it was made in this conversation.

### `get_booking` (~276 tokens)

Where a Vuelo booking stands

For a booking made in another conversation, or through another assistant: where it stands, by its Vuelo reference (VU-...) and the email or mobile it was booked with. Says booked, reserved, cancelled, cancellation_in_progress or not_booked, with the item, dates, number of travellers, amount, free cancellation date, the stay (hotel, area, stars, room, nights, what is included, any tax paid at the hotel, and a public page about the hotel), the date a reservation must be paid by, any requests with Vuelo's team, and its history oldest first (booked or reserved, cancellation_requested, cancelled, refund_sent, request_raised, team_replied, changed with what changed, request_resolved). It never gives names, dates of birth or the booking page: to give the traveller their page, use find_my_booking. If nothing matches, say the details did not match a booking and ask them to check the reference and the email or mobile; never say which was wrong. For a booking made in this conversation, use get_booking_status.

Input parameters:

- `email` (string): The email the traveller booked with.
- `mobile` (string): Or the mobile on the booking, instead of the email.
- `reference` (string, required): The Vuelo booking reference, VU-...

### `request_change` (~328 tokens)

Ask Vuelo for a change after paying

A change to a paid booking, which no tool can make directly: a name on a ticket goes through the airline, and new dates or flights are re-booked by Vuelo's team. Sends the change typed, so the team acts on exactly what the traveller wants, and returns a ticket reference and reply time to tell them. Nothing changes until the team does it, so never say it has. kind passenger_details: passenger (position, from 1), field (name, date_of_birth, title or gender) and new_value (a name exactly as on the passport, or YYYY-MM-DD). kind dates: new_from and new_to. kind flight: which (outbound or return) and new_value. kind special_request (a request to the hotel): request (late_check_in, early_check_in, accessibility, cot, connecting_rooms, bed_type, dietary or other), new_value for a time or bed (e.g. 'arriving 23:30', 'twin beds') and notes; the hotel decides, so say it has been asked for, never that it is confirmed. kind room or other: notes. Before paying, use update_travellers or book again instead. By the Vuelo reference (VU-...) and the email or mobile it was booked with.

Input parameters:

- `change` (object, required): What should change.
- `email` (string): The email the traveller booked with.
- `mobile` (string): Or the mobile on the booking, instead of the email.
- `reference` (string, required): The Vuelo booking reference, VU-...

### `follow_up_ticket` (~239 tokens)

Check a support request later

When the traveller asks you to check a support request later ("check it later today", "let me know tomorrow"): you cannot come back by yourself, so Vuelo does. Pass the ticket reference (SUP-...), how many hours from now to check (in_hours, 1 to 72; 4 if they just say later today), and the taskId of the booking in this conversation or the email or mobile the request was raised with. At that time Vuelo checks the request and texts the traveller where it stands, with any refund or cancellation; if the team replies sooner, Vuelo texts them then. Tell the traveller when Vuelo will text. Up to three checks a day per request.

Input parameters:

- `email` (string): The email the request was raised with.
- `in_hours` (number): Hours from now to check. 4 for "later today", 24 for "tomorrow".
- `mobile` (string): Or the mobile on the request.
- `taskId` (string): The booking's taskId, if it was made in this conversation.
- `ticket` (string, required): The ticket reference, SUP-...

### `get_support_ticket` (~159 tokens)

Vuelo support request status

Where a request to Vuelo's support team stands: with the team, replied (the reply is in the traveller's email), or resolved. Pass the ticket reference (SUP-...) and either the taskId of the booking in this conversation or the email the traveller gave. Use it when the traveller asks for an update. To add to a request, call contact_support again with the same booking and reason: it joins the same conversation.

Input parameters:

- `email` (string): The email the traveller gave for the reply.
- `mobile` (string): Or the mobile on the request.
- `taskId` (string): The booking's taskId, if it was made in this conversation.
- `ticket` (string, required): The ticket reference, SUP-...

### `get_booking_status` (~92 tokens)

Vuelo booking status

The current state of a Vuelo booking started with book_trip. Pass wait_seconds (up to 50) straight after the traveller has the link: it answers the moment they open it, pay or cancel, so you can tell them it is booked without being told.

Input parameters:

- `taskId` (string, required)
- `wait_seconds` (integer): Hold the answer until the booking changes, up to this many seconds.

## Diagnostics

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

## Score history

- 2026-11-05: 63
- 2026-11-04: 62
- 2026-11-03: 62
- 2026-11-02: 61
- 2026-11-01: 61
- 2026-10-31: 61
- 2026-10-30: 60
- 2026-10-29: 59

## Common questions

### What is the Vuelo Travel MCP server?

Vuelo Travel is an MCP server listed in the public MCP registry as com.getvuelo/travel. Search and book live flights and hotels. No API key; the traveller confirms on their phone. This page covers its hosted endpoint (https://mcp.getvuelo.com/mcp).

### Is the Vuelo Travel MCP server safe to use?

Vuelo Travel scores 63 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 Vuelo Travel MCP server expose?

Vuelo Travel exposes 21 tools: search_trips, get_hotel_availability, get_offer, get_flight_extras, change_package_flight, and 16 more. Their descriptions and schemas cost roughly 6,042 tokens of context every time the server is loaded.

### Does the Vuelo Travel MCP server require authentication?

No. We connected to Vuelo Travel without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Vuelo Travel MCP server still maintained?

Vuelo Travel is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.getvuelo.com/mcp
- Website: https://getvuelo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-getvuelo-travel/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-getvuelo-travel/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-getvuelo-travel/mcp