Skip to content

MCP servers › com.getvuelo › travel

MCP server · registry snapshot 2026-10-30 · last tested 2026-10-30

travel MCP server

Registry name com.getvuelo/travel

Vuelo Travel — the publisher's title

by getvuelo.com · domain (the registry's namespace rule)Website ↗

Search and book live flights and hotels. No API key; the traveller confirms on their phone. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-30version 1.0.1streamable HTTP20 tools

Summary

com.getvuelo/travel is a remote MCP server listed in the official MCP registry at version 1.0.1, under the namespace of the domain getvuelo.com. On 2026-10-30 ProtocolProbe connected to it in read-only mode and read its inventory: 20 tools, 2 resources and 0 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason

Operate this server? Correct a fact · README badge · Run the checks yourself

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Your own values
none declared (not a guarantee)
Sign-in
none needed to open a session
Tools
20
Last tested
2026-10-30

Tool list size

12,612 tokens on Claude Opus 5.5

Added to every request that loads this server's tools (20 tools). Counted with Anthropic's token counter on 2026-10-30, from the tool list we read on 2026-10-30. Median across 25,738 counted servers: 2,858 tokens. How it is counted

How a client gets in

Connects without signing in

Read from the server's public metadata on 2026-10-30 (mcp.getvuelo.com), in our read-only connection; no tool was called. It may have changed since. How it is read

Tool list at the three APIs

Not sent yet for this version (1.0.1).

Add to your client

Observed fact

This server accepted a session without any credential and lists 4 tools whose name or declaration suggests they change data (update_travellers, send_to_payer, cancel_booking, send_receipt). That is our reading of the names; we did not call them. Source: our connection, 2026-10-30.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-30
Mode
read-only (no tool calls)
Latest version
1.0.1, published 2026-10-29 (registry, as of the 2026-10-30 snapshot)
First listed version
2026-10-29 (earliest version still in the registry; older removed versions would be earlier)
Version history
2 versions listed, all on 2026-10-29; 2 in the 90 days before the 2026-10-30 snapshot.
Most recent 2 versions
  • 1.0.1 · 2026-10-29
  • 1.0.0 · 2026-10-29
(versions still listed in the registry only)
Registry data
snapshot 2026-10-30
Package and repository
checked 2026-10-30
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Dead or stale signals

None found in the records we hold

Looked for and not found: deprecated in the registry. Does not apply: listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.

Changes since the last refresh

New in the registry: not in the list of 2026-10-29, listed on 2026-10-30 with version 1.0.1 (published 2026-10-29).

Source: the official MCP Registry list on 2026-10-29 and on 2026-10-30.

What it is

What does this server offer?

Observed inventory
20tools
2resources
0prompts

None of its 20 tools are described as changing anything. For 20 the reading was uncertain, so no mark is shown.

  • search_tripson 6 other servers

    “Find hotels, flights and flight-and-hotel packages on Vuelo for a destination, dates and number of travellers, within a budget.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    15 inputs, 4 required
    • destinationstringrequired“Town or city, with its country when the name is shared or could be ambiguous: "Lisbon", "Zurich, Switzerland", "Cambridge, UK".”
    • fromstringrequired“Check-in date, YYYY-MM-DD”
    • tostringrequired“Check-out or return date, YYYY-MM-DD.”
    • travellersintegerrequired“Number of travellers”
    • budgetnumber“Maximum total in pounds”
    • originstring“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…”
    • destinationAirportstring“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…”
    • onlystring“What the traveller asked for.”
    • refundableOnlyboolean“Only stays with a refundable rate, when the traveller asks for refundable or free cancellation.”
    • minStarsinteger“Minimum hotel star rating, when the traveller asks for one (for example 5 for "5-star").”
    • hotelstring“The hotel, when the traveller names one ("the Pulitzer", "The Savoy"): its name only, with the town in destination.”
    • cabinstring“Which cabin to price flights in, when the traveller asks for one ("business class", "premium economy", "first").”
    • passengersarray“Pass this whenever you know it: the results page and checkout then need nothing typed.”
    • mobilestring“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 o…”
    • travellerobject“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 postc…”
  • get_hotel_availabilityon 2 other servers

    “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    4 inputs, 4 required
    • propertystringrequired“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.”
    • fromstringrequired“Check-in date, YYYY-MM-DD”
    • tostringrequired“Check-out date, YYYY-MM-DD”
    • travellersintegerrequired“Number of adults”
  • “Details, terms, photos and the payment options for one Vuelo offer, repriced live.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • offerIdstringrequired
  • change_package_flight

    “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…”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world yes

    1 input, 1 required
    • offerIdstringrequired“The package offerId from search_trips”
  • “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.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    14 inputs, 2 required
    • offerIdstringrequired
    • paymentOptionstringrequired“One of the options search_trips returned as eligible”
    • travellersarray“Each passenger, as on their passport, with their title and gender where you know them (airlines need both).”
    • travellersConfirmedboolean“Set true when the traveller has confirmed the passengers Vuelo filled in and named back to you.”
    • consumer_refstring“The vc_ reference Vuelo gave you after this traveller authorised you to book for them within limits.”
    • mobilestring“Mobile number to text the link to (any country; international format outside the UK).”
    • leadTravellerobject“The traveller booking: name, email, date of birth and home postcode, town and county, as far as you know them.”
    • deliverystring“How the confirmation reaches the traveller.”
    • conversationIdstring
    • from_cardboolean“Set only by the Vuelo card.”
    • hoststring“Which assistant this is, so the Vuelo page names it and matches its look.”
    • payerobject“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.”
    • notify_urlstring“Your own https address.”
    • notify_tokenstring“A secret of yours.”
  • get_booking_progress

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

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    1 input
    • offerIdstring
  • change_payment_option

    “When the traveller wants to pay a different way (for example reserve now instead of paying in full) before they have confirmed.”

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    2 inputs, 2 required
    • taskIdstringrequired
    • paymentOptionstringrequired
  • update_travellers

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

    Publisher declares: read-only no · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • taskIdstringrequired“The taskId book_trip returned.”
    • leadTravellerobject“The booking traveller's email, date of birth and home postcode, town and county, to fill in their Vuelo account on the pay page.”
    • travellersarray
  • resend_link

    “When the traveller says the secure link has not arrived, or asks for another: Vuelo texts it again, to the same number.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    1 input, 1 required
    • taskIdstringrequired
  • send_to_payer

    “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.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 2 required
    • taskIdstringrequired“The taskId book_trip returned.”
    • namestringrequired“The name of the person paying, as the traveller gave it.”
    • mobilestring“Their mobile, to text the link.”
    • emailstring“Their email, to email the link.”
  • cancel_bookingon 51 other servers

    “Cancel a Vuelo booking, before or after the traveller confirms.”

    Publisher declares: read-only no · destructive yes · idempotent yes · open-world yes

    6 inputs
    • taskIdstring“The taskId book_trip returned, when the booking was made in this conversation.”
    • referencestring“Otherwise: the Vuelo booking reference (VU-...).”
    • emailstring“With reference: the email the traveller booked with.”
    • mobilestring“With reference, instead of email: the mobile on the booking.”
    • previewboolean“true: only say what cancelling would refund, changing nothing.”
    • codestring“For a paid booking: the six-digit code Vuelo texted the traveller, as they gave it to you.”
  • contact_supporton 4 other servers

    “Send the traveller's request to Vuelo's support team, who will be in touch with them.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    6 inputs, 2 required
    • taskIdstring“The taskId book_trip returned, when the booking was made in this conversation.”
    • referencestring“The Vuelo booking reference (VU-...), when there is no taskId.”
    • emailstring“The email the traveller booked with: needed when there is no taskId, or when this tool asks for it.”
    • mobilestring“With reference, instead of email: the mobile on the booking.”
    • topicstringrequired“What the request is about.”
    • messagestringrequired“What the traveller wants, in their words.”
Show 8 more tools
  • find_my_booking

    “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.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs
    • referencestring“The Vuelo booking reference, VU-...”
    • emailstring“The email the traveller booked with.”
    • mobilestring“The mobile on the booking: with the reference instead of the email, or alone without the reference.”
    • countrystring“For a mobile typed the local way (06 12 34 56 78), the country it is from, as an ISO code (FR).”
  • list_my_bookingson 6 other servers

    “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.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    3 inputs, 1 required
    • mobilestringrequired“The mobile the traveller booked with.”
    • countrystring“For a mobile typed the local way (06 12 34 56 78), the country it is from, as an ISO code (FR).”
    • codestring“The 6-digit code Vuelo texted, once the traveller has read it out.”
  • send_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 …”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs
    • referencestring“The Vuelo booking reference, VU-...”
    • emailstring“The email the traveller booked with.”
    • mobilestring“Or the mobile on the booking.”
    • taskIdstring“The booking's taskId, if it was made in this conversation.”
  • “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.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    3 inputs, 1 required
    • referencestringrequired“The Vuelo booking reference, VU-...”
    • emailstring“The email the traveller booked with.”
    • mobilestring“Or the mobile on the booking, instead of the email.”
  • request_changeon 3 other servers

    “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.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    4 inputs, 2 required
    • referencestringrequired“The Vuelo booking reference, VU-...”
    • emailstring“The email the traveller booked with.”
    • mobilestring“Or the mobile on the booking, instead of the email.”
    • changeobjectrequired“What should change.”
  • follow_up_ticket

    “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.”

    Publisher declares: read-only no · destructive no · idempotent no · open-world yes

    5 inputs, 1 required
    • ticketstringrequired“The ticket reference, SUP-...”
    • in_hoursnumber“Hours from now to check.”
    • taskIdstring“The booking's taskId, if it was made in this conversation.”
    • emailstring“The email the request was raised with.”
    • mobilestring“Or the mobile on the request.”
  • get_support_ticketon 4 other servers

    “Where a request to Vuelo's support team stands: with the team, replied (the reply is in the traveller's email), or resolved.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    4 inputs, 1 required
    • ticketstringrequired“The ticket reference, SUP-...”
    • taskIdstring“The booking's taskId, if it was made in this conversation.”
    • emailstring“The email the traveller gave for the reply.”
    • mobilestring“Or the mobile on the request.”
  • get_booking_statuson 22 other servers

    “The current state of a Vuelo booking started with book_trip.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    2 inputs, 1 required
    • taskIdstringrequired
    • wait_secondsinteger“Hold the answer until the booking changes, up to this many seconds.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-30.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

No AI reading was available for this server's tools (the two runs did not agree, or the listing was not reviewed).

Counted from the listing

Parameters with a description
90% of 87
Tools with a description
100% of 20
Typical description length
654 characters

The tool set

Counted from the listing

Tools
20
Size of the list
about 9,662 tokens for an agent to load (characters ÷ 4)
Naming
20 of 20 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 0 of 20 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-30 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://mcp.getvuelo.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "travel": {
      "url": "https://mcp.getvuelo.com/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "travel": {
      "type": "http",
      "url": "https://mcp.getvuelo.com/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"travel","type":"http","url":"https://mcp.getvuelo.com/mcp"}'
Claude Code
claude mcp add --transport http travel https://mcp.getvuelo.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
  "mcpServers": {
    "travel": {
      "type": "streamableHttp",
      "url": "https://mcp.getvuelo.com/mcp",
      "disabled": false,
      "autoApprove": []
    }
  }
}
Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
  "mcpServers": {
    "travel": {
      "httpUrl": "https://mcp.getvuelo.com/mcp"
    }
  }
}
OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.travel]
url = "https://mcp.getvuelo.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
  "context_servers": {
    "travel": {
      "url": "https://mcp.getvuelo.com/mcp"
    }
  }
}
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.getvuelo.com/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint mcp.getvuelo.com/mcpSession openedmatchesour test · 2026-10-30
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-30

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.What changes this check: This check opens the repository link in the registry entry. GitHub's documentation describes changing a repository's visibility in its Settings, under Danger Zone, Change visibility. GitHub: setting repository visibility
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-30. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral

Common questions about com.getvuelo/travel

Answered from the data above

Who publishes com.getvuelo/travel?

The registry ties the namespace com.getvuelo to the domain getvuelo.com; only its owner can publish under it. These are facts from the registry and GitHub, not a rating.

Does com.getvuelo/travel need an API key or sign-in?

It opened a session without any credential on 2026-10-30. The registry entry declares no required credential; no declaration is not a guarantee.

Has com.getvuelo/travel been security tested?

Partly. 3 of the 14 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. ProtocolProbe publishes no security verdict for a named server.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-30
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: not applicable
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: not applicable

3 exercised11 not run (reason given)4 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 14 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 4
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.The server exposes no prompts.not applicable
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable

Source: our own test, 2026-10-30, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 3,040 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 20 tools, 2 resources, 0 prompts.
  4. 10,037 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
pending: added in a later update
listed 2026-10-30; not classified yet
Pricing modelAI-classified
pending: added in a later update
the website is not read yet
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-30
MCP capability
resources, tools
our test · 2026-10-30
Transport
streamable HTTP
registry · 2026-10-30
Required credentials
none declared
registry · 2026-10-30 · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-30
Lifecycle status
registry · 2026-10-30
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type · 2026-10-30

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “com.getvuelo/travel: MCP server record.” Data checked 2026-10-30. https://protocolprobe.com/mcp/servers/com.getvuelo/travel

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/com.getvuelo/travel)](https://protocolprobe.com/mcp/servers/com.getvuelo/travel)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology