com.flightpowers/google-flights

Est-ce que com.flightpowers/google-flights est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.flightpowers/google-flights » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 2 outils

• search_oneway_flights≈ 4069 tokens

  FlightPowers one-way fare search: live prices read from Google Flights. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- plus either one departure date or a date range. Returns each flight's price, airline, duration, stops, a bookable buy_link, and Google's historical price range (price_insights_low / price_insights_high) so you can say whether a fare is actually a good deal. Use it for any one-way fare question, including open-ended ones. For a flexible search make ONE call with a date range and/or several destinations -- do NOT call it once per date. 'Cheapest flight to Sri Lanka anywhere in October' is one call, not thirty. Each date/destination combination is one billed request; the count and the plan's remaining quota come back in `api_usage`. `by_destination` carries one entry per destination you asked for -- empty ones included, each with a `reason` -- so read it before telling a user a destination has no flights. Requires the caller's own RapidAPI key for the Google Flights Live API. Get one (free tier available) at https://rapidapi.com/mtnrabi/api/google-flights-live-api, then pass it as an `x-rapidapi-key` header (preferred), a `?rapidapi_key=` query parameter on the server URL, or your client's own API key field -- first non-empty wins. Usage counts against the caller's own RapidAPI plan, not ours; every response reports what it spent and what is left in `api_usage`. No key? Sign in with Google and the first 10 searches each day are free on this server -- ad-free, nothing to paste. Connect your own RapidAPI key at https://flights.flightpowers.com/connect to remove the cap.

  Paramètres, retour & exemple (21)

  Paramètres

  • limit · integer · optionnel
    Maximum flights to return, after merging and sorting.
  • sort_by · string · optionnel
    "best", "price", or "duration". Applied across all results.
  • verbose · boolean · optionnel
    Return every field the upstream sends on each fare, and every fare that was selected, with no row bound. Off by default: a result carries the best rows by your sort_by in a compact shape (dates, destination, airline, stops, duration, price, trip length and the booking link), because a wide search over a month and several destinations otherwise produces a megabyte of JSON that some hosts refuse to put in the conversation at all. Turn it on when you need the arrival times, the per-leg stop counts, the raw stop details or more rows than results_returned; results_total always says how many there were.
  • currency · string · optionnel
    ISO currency code, default "usd".
  • max_price · ? · optionnel
    Only return flights at or below this price.
  • max_stops · ? · optionnel
    Maximum stops per flight. 0 means non-stop only.
  • seat_type · ? · optionnel
    1 economy, 2 premium economy, 3 business, 4 first.
  • passengers · ? · optionnel
    One entry per traveller, not a count: 1 adult, 2 child (aged 2-11), 3 infant on lap, 4 infant in seat, e.g. [1, 1, 2] for two adults and a child. At least one adult, each infant on lap needs its own adult, at most 9. Omit for one adult. A counts list [adults, children, infants], e.g. [2, 1, 0], or a bare [2] for two adults, is recognised and converted to codes before the search; a list that is valid as codes is searched as codes.
  • to_airport · ? · requis
    Destination airport. One IATA code ("BCN"), several separated by commas ("BCN,LIS,ATH"), or a list (["BCN","LIS","ATH"]) -- every shape is accepted and the destinations are compared in the same search.
  • from_airport · string · requis
    Origin IATA code, e.g. "TLV". One origin per search; a second one is refused rather than searched.
  • max_searches · ? · optionnel
    The billed requests this call may make, up or down. Leave it out for the normal behaviour: the cap covers the request when the request is reasonable (a whole month at three trip lengths is 93 combinations and a whole month x 3 nights x 3 destinations is 279; both run in full) and anything past it is sampled evenly across the range rather than cut short. Set it lower to spend less of the plan's quota on a wide search, or higher -- to a hard maximum of 300 -- for a grid wider than that.
  • use_fallback · ? · optionnel
    Leave unset. Switches the search to a second, independent flight data source instead of the usual Google Flights page read. Unset already escalates to that source once, automatically, after a search's retries have failed. true forces it inline on every attempt -- much slower, and it can time out. false disables it entirely, that automatic retry included.
  • airline_codes · ? · optionnel
    Restrict to these airline codes, e.g. ["LY"].
  • departure_date · ? · optionnel
    Single departure date, "YYYY-MM-DD".
  • arrival_time_max · ? · optionnel
    Latest arrival hour, 0-23.
  • arrival_time_min · ? · optionnel
    Earliest arrival hour, 0-23.
  • departure_date_to · ? · optionnel
    Last date of a departure range.
  • departure_time_max · ? · optionnel
    Latest departure hour, 0-23.
  • departure_time_min · ? · optionnel
    Earliest departure hour, 0-23.
  • departure_date_from · ? · optionnel
    First date of a departure range.
  • exclude_airline_codes · ? · optionnel
    Exclude these airline codes.

  Exemple d'appel

  {"name": "search_oneway_flights", "arguments": {"to_airport": "texte", "from_airport": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"message": "texte", "partial": "texte", "results": [], "api_usage": {}, "signup_url": "texte", "from_airport": "texte", "result_count": 1, "needs_api_key": true, "results_total": 1, "search_status": "ok", "by_destination": {}, "quota_exhausted": true}}

• search_roundtrip_flights≈ 4388 tokens

  FlightPowers round-trip fare search: live prices read from Google Flights, priced as paired legs rather than two separate one-ways. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- a departure date or range, and either a return date or a trip length in nights. Returns the total price for both legs, per-leg airline, stops and duration, and a single bookable buy_link for the trip. Use it for any return-trip fare question. For a flexible search make ONE call: pass departure_date_from / departure_date_to for the outbound range and `nights` instead of return_date to compare trip lengths -- '5 to 7 nights in Rome sometime in May' is one call. A WHOLE MONTH is one call too. departure_date_from "2026-10-01", departure_date_to "2026-10-31" and nights [3, 4, 5] prices every departure day in October at three trip lengths and tells you which combination is cheapest. That is 93 date/night combinations and the cap rises to cover them by itself -- do not narrow the question to make it fit, and do not split it into several calls. Each date/night/destination combination is ONE request billed to the caller's plan, so a month at three trip lengths costs 93 of them and the same month across two destinations costs 186. Say that number before running a search that large if the user has not asked for it in so many words. A search that fails with a server error is retried once and RapidAPI bills the retry, so the figure to quote back is `api_usage.hub_requests_billed` (what the plan was actually charged), not the combination count. Both come back in `api_usage`, with the plan's remaining quota. `by_destination` carries one entry per destination you asked for -- empty ones included, each with a `reason` -- so read it before telling a user a destination has no flights. Requires the caller's own RapidAPI key for the Google Flights Live API. Get one (free tier available) at https://rapidapi.com/mtnrabi/api/google-flights-live-api, then pass it as an `x-rapidapi-key` header (preferred), a `?rapidapi_key=` query parameter on the server URL, or your client's own API key field -- first non-empty wins. Usage counts against the caller's own RapidAPI plan, not ours; every response reports what it spent and what is left in `api_usage`. No key? Sign in with Google and the first 10 searches each day are free on this server -- ad-free, nothing to paste. Connect your own RapidAPI key at https://flights.flightpowers.com/connect to remove the cap.

  Paramètres, retour & exemple (21)

  Paramètres

  • limit · integer · optionnel
    Maximum trips to return, after merging and sorting.
  • nights · ? · optionnel
    Trip length in nights; a number, or a list like [5, 6, 7]. The return date is derived from each departure date.
  • sort_by · string · optionnel
    "best", "price", or "duration". Applied across all results.
  • verbose · boolean · optionnel
    Return every field the upstream sends on each fare, and every fare that was selected, with no row bound. Off by default: a result carries the best rows by your sort_by in a compact shape (dates, destination, airline, stops, duration, price, trip length and the booking link), because a wide search over a month and several destinations otherwise produces a megabyte of JSON that some hosts refuse to put in the conversation at all. Turn it on when you need the arrival times, the per-leg stop counts, the raw stop details or more rows than results_returned; results_total always says how many there were.
  • currency · string · optionnel
    ISO currency code, default "usd".
  • max_price · ? · optionnel
    Only return trips at or below this total price.
  • seat_type · ? · optionnel
    1 economy, 2 premium economy, 3 business, 4 first.
  • passengers · ? · optionnel
    One entry per traveller, not a count: 1 adult, 2 child (aged 2-11), 3 infant on lap, 4 infant in seat, e.g. [1, 1, 2] for two adults and a child. At least one adult, each infant on lap needs its own adult, at most 9. Omit for one adult. A counts list [adults, children, infants], e.g. [2, 1, 0], or a bare [2] for two adults, is recognised and converted to codes before the search; a list that is valid as codes is searched as codes.
  • to_airport · ? · requis
    Destination airport. One IATA code ("BCN"), several separated by commas ("BCN,LIS,ATH"), or a list (["BCN","LIS","ATH"]) -- every shape is accepted and the destinations are compared in the same search.
  • return_date · ? · optionnel
    Fixed return date. Use this OR nights, not both.
  • from_airport · string · requis
    Origin IATA code, e.g. "TLV". One origin per search; a second one is refused rather than searched.
  • max_searches · ? · optionnel
    The billed requests this call may make, up or down. Leave it out for the normal behaviour: the cap covers the request when the request is reasonable (a whole month at three trip lengths is 93 combinations and a whole month x 3 nights x 3 destinations is 279; both run in full) and anything past it is sampled evenly across the range rather than cut short. Set it lower to spend less of the plan's quota on a wide search, or higher -- to a hard maximum of 300 -- for a grid wider than that.
  • use_fallback · ? · optionnel
    Leave unset. Switches the search to a second, independent flight data source instead of the usual Google Flights page read. Unset already escalates to that source once, automatically, after a search's retries have failed. true forces it inline on every attempt -- much slower, and it can time out. false disables it entirely, that automatic retry included.
  • departure_date · ? · optionnel
    Single outbound date, "YYYY-MM-DD".
  • max_return_stops · ? · optionnel
    Maximum stops on the return leg.
  • departure_date_to · ? · optionnel
    Last date of an outbound range.
  • departure_date_from · ? · optionnel
    First date of an outbound range.
  • max_departure_stops · ? · optionnel
    Maximum stops on the outbound leg.
  • return_airline_codes · ? · optionnel
    Restrict the return leg to these airlines.
  • returns_per_outbound · ? · optionnel
    How many return flights to pair with each outbound flight, 1 to 5 (default 2). Each date/destination combination searched still returns at most 10 trips; at 5 they are picked from up to 50 pairings instead of 20. It adds no requests. Not applied when results come from the fallback source.
  • departure_airline_codes · ? · optionnel
    Restrict the outbound leg to these airlines.

  Exemple d'appel

  {"name": "search_roundtrip_flights", "arguments": {"to_airport": "texte", "from_airport": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"message": "texte", "partial": "texte", "results": [], "api_usage": {}, "signup_url": "texte", "from_airport": "texte", "result_count": 1, "needs_api_key": true, "results_total": 1, "search_status": "ok", "by_destination": {}, "quota_exhausted": true}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://flights.flightpowers.com/mcp