Skip to content

Vuelo Travel MCP server

com.getvuelo/travelgetvuelo.comstreamable-httpv1.0.1Scanned

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

21 tools: 1 can delete or cancel things, 5 do something that can't be undone, 7 change things and 8 only read.

Tools: 1 delete, 5 irreversible, 7 write, 8 read.
  • Reads private data · 4
  • Reads text others write · 17
  • Can send data out · 4
  • 1 finding

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things and 5 do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Vuelo Travel MCP server can do

The Vuelo Travel MCP server is published by getvuelo.com, a domain the MCP Registry verified. It has 21 tools. It can delete or cancel things (1 tool: cancel_booking), do things that cannot be undone, such as sending, paying or publishing (change_payment_option, resend_link, send_to_payer, contact_support and 1 more) and create or change data (7 tools: change_package_flight, book_trip, update_travellers, find_my_booking and 3 more). 8 tools only read.

4 tools read private data (find_my_booking, list_my_bookings, get_booking and 1 more); 17 tools bring in text other people can write (search_trips, get_hotel_availability, get_offer and 14 more); 4 tools can send data out of your system (resend_link, send_to_payer, contact_support and 1 more). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 10, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

21 tools

Deletes or cancels 1Claude Code: deny
  • cancel_bookingCancel a Vuelo booking, before or after the traveller confirms.Reads text others writeNo findings

    Why it is in this group

    • The name "cancel_booking" says "cancel": a word for removing or ending something.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: true
    • openWorldHint: true
Can't be undone 5Claude Code: ask
  • change_payment_optionWhen the traveller wants to pay a different way (for example reserve now instead of paying in full) before they have confirmed.No findings

    Why it is in this group

    • The name "change_payment_option" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • contact_supportSend the traveller's request to Vuelo's support team, who will be in touch with them.Reads text others writeCan send data outNo findings

    Why it is in this group

    • The description's first verb is "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe description's first verb is "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • send_receiptWhen 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…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_receipt" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_receipt" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • send_to_payerAfter 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 inst…Reads text others writeCan send data outNo findings

    Why it is in this group

    • The name "send_to_payer" says "send": a word for sending, and what is sent cannot be taken back.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • outboundThe name "send_to_payer" says "send": it sends or publishes something to other people.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
Changes things 7Claude Code: ask
  • book_tripBookings 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • change_package_flightFor 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 mo…Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • find_my_bookingFor 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 tha…Reads private dataReads text others write1 finding

    Why it is in this group

    • The name "find_my_booking" says "find": a word for reading.
    • The server marks it as not read-only (readOnlyHint: false).

    What it can reach

    • private-dataThe description's first sentence says "conversation": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "conversation": it reads messages, which other people can write.

    Findings

    • Warn

      The server marks "find_my_booking" as not read-only (readOnlyHint: false), and its words say it reads.

      Matched text

      annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_my_booking" says "find": a word for reading.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • follow_up_ticketWhen 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.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • list_my_bookingsFor 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "list_my_bookings" says "list": a word for reading.
    • The input takes a statement or command to run (input.code), which can change anything it can reach.

    What it can reach

    • private-dataThe description's first sentence says "chat": it reads messages.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "chat": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • request_changeA 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.Reads text others writeNo findings

    Why it is in this group

    • The name "request_change" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
  • update_travellersCorrect 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).No findings

    Why it is in this group

    • The name "update_travellers" says "update": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 8Show 8 read-only tools
  • get_bookingFor 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.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_booking" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "conversation": it reads messages.
    • untrusted-inputThe description's first sentence says "conversation": it reads messages, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_booking_progressProgress of the newest booking for an offer, or the newest booking of all, for the Vuelo widget.No findings

    Why it is in this group

    • The name "get_booking_progress" says "get": a word for reading.
    Description, as the server wrote it
    Progress of the newest booking for an offer, or the newest booking of all, for the Vuelo widget.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_booking_statusThe current state of a Vuelo booking started with book_trip.No findings

    Why it is in this group

    • The name "get_booking_status" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • get_flight_extrasFor 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 …Reads text others writeNo findings

    Why it is in this group

    • The name "get_flight_extras" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_hotel_availabilityLive rooms and prices at ONE hotel the traveller already has in mind, for their dates and number of guests, without searching the whole town.Reads text others writeNo findings

    Why it is in this group

    • The name "get_hotel_availability" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_offerDetails, terms, photos and the payment options for one Vuelo offer, repriced live.Reads text others writeNo findings

    Why it is in this group

    • The name "get_offer" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Details, terms, photos and the payment options for one Vuelo offer, repriced live.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_support_ticketWhere a request to Vuelo's support team stands: with the team, replied (the reply is in the traveller's email), or resolved.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_support_ticket" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe name "get_support_ticket" says "get" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "reply": it reads comments, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • search_tripsFind hotels, flights and flight-and-hotel packages on Vuelo for a destination, dates and number of travellers, within a budget.Reads text others writeNo findings

    Why it is in this group

    • The name "search_trips" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

272 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 4 outbound tools breaks every one.

Reads private data4
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write17
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out4
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__travel__contact_support",
      "mcp__travel__resend_link",
      "mcp__travel__send_receipt",
      "mcp__travel__send_to_payer"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:23 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
13
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 13 tools that change things (1 destructive, 5 irreversible, 7 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.getvuelo.com/mcp: tools/list returned 21 tools to an anonymous client, including cancel_booking (destructive), change_payment_option (irreversible), resend_link (irreversible), send_to_payer (irreversible), contact_support (irreversible) and 8 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 9 to 13

Findings

Matches of fixed checks, with the text they matched.

1 warn
  • The server marks "find_my_booking" as not read-only (readOnlyHint: false), and its words say it reads.

    Matched text

    annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "find_my_booking" says "find": a word for reading.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools6 added, 4 changed.+6 added~4 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 9 -> 13.View diff
    • Tools that change things, listed without credentials: 9 to 13

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__travel__search_trips",
      "mcp__travel__get_hotel_availability",
      "mcp__travel__get_offer",
      "mcp__travel__get_flight_extras",
      "mcp__travel__get_booking_progress",
      "mcp__travel__get_booking",
      "mcp__travel__get_support_ticket",
      "mcp__travel__get_booking_status"
    ],
    "ask": [
      "mcp__travel__change_package_flight",
      "mcp__travel__book_trip",
      "mcp__travel__change_payment_option",
      "mcp__travel__update_travellers",
      "mcp__travel__resend_link",
      "mcp__travel__send_to_payer",
      "mcp__travel__contact_support",
      "mcp__travel__find_my_booking",
      "mcp__travel__list_my_bookings",
      "mcp__travel__send_receipt",
      "mcp__travel__request_change",
      "mcp__travel__follow_up_ticket"
    ],
    "deny": [
      "mcp__travel__cancel_booking"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as travel. Review it before you use it.

Capability tags behind 17 rules
  • mcp__travel__search_trips untrusted-input
  • mcp__travel__get_hotel_availability untrusted-input
  • mcp__travel__get_offer untrusted-input
  • mcp__travel__get_flight_extras untrusted-input
  • mcp__travel__change_package_flight untrusted-input
  • mcp__travel__book_trip untrusted-input
  • mcp__travel__resend_link untrusted-input, outbound
  • mcp__travel__send_to_payer untrusted-input, outbound
  • mcp__travel__cancel_booking untrusted-input
  • mcp__travel__contact_support untrusted-input, outbound
  • mcp__travel__find_my_booking private-data, untrusted-input
  • mcp__travel__list_my_bookings private-data, untrusted-input
  • mcp__travel__send_receipt untrusted-input, outbound
  • mcp__travel__get_booking private-data, untrusted-input
  • mcp__travel__request_change untrusted-input
  • mcp__travel__follow_up_ticket untrusted-input
  • mcp__travel__get_support_ticket private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.getvuelo/travel/verify?hash=54a76b0223e72a0a89ea048099fbbe8142ec54a74cfd60d69bb4e69f3e8023a8" | jq -e '.changed == false'

Pinned hash 54a76b0223e7, from Nov 10, 2026, 18:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.getvuelo/travel/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.getvuelo/travel
[![Anlyon Radar](https://radar.anlyon.com/badge/com.getvuelo/travel.svg)](https://radar.anlyon.com/servers/com.getvuelo/travel)

Source: MCP Registry. Synced Oct 29, 2026, 09:17 UTC.

Vuelo Travel MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Vuelo Travel MCP server safe?

No scan can promise that. What its definitions show: 21 tools, 13 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Vuelo Travel MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: cancel_booking.

Can the Vuelo Travel MCP server do things that cannot be undone?

Yes. 5 tools can send, pay, publish or merge: change_payment_option, resend_link, send_to_payer, contact_support and send_receipt.

What tools does the Vuelo Travel MCP server have?

21 tools: 1 destructive, 5 irreversible, 7 write, 8 read. cancel_booking, change_payment_option, resend_link, send_to_payer, contact_support, send_receipt, change_package_flight, book_trip and 13 more.

Does the Vuelo Travel MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Vuelo Travel MCP server send data to outside services?

4 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): resend_link, send_to_payer, contact_support and send_receipt.

Has the Vuelo Travel MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 10, 2026. Every change is on this page and in its Atom feed.