io.github.Airtreks/airtreks-mcp

Est-ce que io.github.Airtreks/airtreks-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.Airtreks/airtreks-mcp » 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 11 outils

• custom_route_build≈ 318 tokens

  Break a complex multi-city itinerary into individually-ticketable segments with carrier recommendations. Handles routes that don't fit alliance fare rules — mixed carriers, LCCs, Gulf bridge connections, surface sectors. This is how AirTreks consultants build 90% of itineraries. Use this for any route with 4+ stops, backtracking, or region combinations that alliance fares can't cover.

  Paramètres, retour & exemple (4)

  Paramètres

  • pax · number · optionnel
    Number of passengers
  • budget · string · optionnel · budget | mid | premium | business
    Budget tier: 'budget' prioritizes LCCs, 'business' prioritizes J-class product quality
  • cities · array · requis
    Ordered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'CMB', 'NBO', 'LIS', 'LAX'])
  • preferences · array · optionnel
    Preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'

  Exemple d'appel

  {"name": "custom_route_build", "arguments": {"cities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• fare_product_match≈ 220 tokens

  Recommend the best fare product type for a route — RTW, Circle Pacific, Circle Atlantic, Open Jaw, or Custom Multi-City. Considers stop count, direction, and backtracking to match the right alliance fare structure.

  Paramètres, retour & exemple (3)

  Paramètres

  • cities · array · requis
    Ordered list of IATA city/airport codes
  • isOneDirection · boolean · optionnel
    Is the route traveling continuously in one direction (east or west)?
  • includeBacktracking · boolean · optionnel
    Does the route backtrack or zigzag between regions?

  Exemple d'appel

  {"name": "fare_product_match", "arguments": {"cities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• fare_quote≈ 484 tokens

  Get live, bookable-quality fares for one specific itinerary — actual flights, actual prices, for the dates given. Needs a departure date for every flown leg. Use this once the customer has settled on cities and dates and wants real numbers rather than a ballpark; use route_estimate instead when dates are still open. It prices the itinerary as a single fare, so very long or awkward multi-continent trips may come back unpriceable — those genuinely need to be split across separate tickets, which is what AirTreks consultants do by hand.

  Paramètres, retour & exemple (7)

  Paramètres

  • cabin · string · optionnel · economy | premium | business | first
    Cabin to price. Defaults to economy. 'premium' means premium economy.
  • dates · array · requis
    Departure date for each FLOWN leg, in travel order, as YYYY-MM-DD. Overland legs marked with '000' do not take a date.
  • adults · integer · optionnel
    Adult travellers. Defaults to 1.
  • cities · array · requis
    Ordered list of IATA city/airport codes, e.g. ['LAX','NRT','BKK']. Put '000' between two codes to mark that leg as travelled overland rather than flown.
  • infants · integer · optionnel
    Infants under 2.
  • children · integer · optionnel
    Children aged 2-11.
  • maxOptions · integer · optionnel
    How many fare options to return. Defaults to 5.

  Exemple d'appel

  {"name": "fare_quote", "arguments": {"dates": [], "cities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• hub_check≈ 200 tokens

  Check the best connection between two airports. Identifies dead legs (routes that fail on alliance fares), suggests hub routing fixes, and shows proven carrier combinations. Essential for transpacific, kangaroo, and intra-Asia routing.

  Paramètres, retour & exemple (3)

  Paramètres

  • to · string · requis
    Destination IATA airport code (e.g. 'JFK')
  • from · string · requis
    Origin IATA airport code (e.g. 'SYD')
  • alliance · string · optionnel
    Preferred alliance: 'star' or 'oneworld'

  Exemple d'appel

  {"name": "hub_check", "arguments": {"to": "texte", "from": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• itinerary_quote≈ 456 tokens

  Price a complete multi-stop or round-the-world trip and get back several ways of ticketing it — cheapest, fastest, fewest stops — with the actual tickets each one is built from. Use this for trips that will not go on a single fare, which is most itineraries with 3+ stops; use fare_quote when you want one specific itinerary on one ticket. It takes about a minute, so it returns a quoteReference immediately; call itinerary_quote_status with it straight away, and that call waits for the result. Keep that reference — it is the only way to retrieve the quote.

  Paramètres, retour & exemple (6)

  Paramètres

  • cabin · string · optionnel · economy | premium | business | first
    Cabin to price. Defaults to economy. 'premium' means premium economy.
  • dates · array · requis
    Departure date for each FLOWN leg, in travel order, as YYYY-MM-DD.
  • adults · integer · optionnel
    Adult travellers. Defaults to 1.
  • cities · array · requis
    Ordered list of IATA city/airport codes for the whole trip, e.g. ['LAX','NRT','BKK','LHR','LAX']. Put '000' between two codes to mark that leg as travelled overland rather than flown.
  • infants · integer · optionnel
    Infants under 2.
  • children · integer · optionnel
    Children aged 2-11.

  Exemple d'appel

  {"name": "itinerary_quote", "arguments": {"dates": [], "cities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• itinerary_quote_status≈ 198 tokens

  Fetch the result of an itinerary_quote using the quoteReference it returned. Call it straight away: it waits up to about 40 seconds for a quote that is still pricing, then returns the finished options, or status 'pending' if the quote needs one more call. Costs nothing and does no searching, so call it again rather than starting a second quote.

  Paramètres, retour & exemple (1)

  Paramètres

  • quoteReference · string · requis
    The quoteReference returned by itinerary_quote.

  Exemple d'appel

  {"name": "itinerary_quote_status", "arguments": {"quoteReference": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• plan_route≈ 311 tokens

  The primary entry point for any multi-city trip. Give it your cities — it automatically evaluates Star Alliance RTW, oneworld RTW, AND custom mixed-carrier builds, then recommends the best approach. Handles direction detection, backtracking analysis, alliance feasibility, surface sectors, and carrier selection. The customer doesn't need to know if their trip is alliance or custom — this tool figures it out.

  Paramètres, retour & exemple (4)

  Paramètres

  • pax · number · optionnel
    Number of passengers
  • budget · string · optionnel · budget | mid | premium | business
    Budget tier — affects carrier selection and fare strategy
  • cities · array · requis
    Ordered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'LIS', 'LAX'])
  • preferences · array · optionnel
    Travel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'

  Exemple d'appel

  {"name": "plan_route", "arguments": {"cities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• route_estimate≈ 335 tokens

  Get a price range for a multi-city or round-the-world trip, drawn from what AirTreks customers have actually paid on those routes. Give it the cities and it returns a per-person range in USD with how much history sits behind it. Use it when someone asks what a trip will cost and you don't have exact dates yet — it needs no dates and no passenger details. It is a range from past bookings, not a live quote, so it will not reflect today's availability or seasonality; it tells you the right ballpark before anyone commits to dates.

  Paramètres, retour & exemple (2)

  Paramètres

  • cabin · string · optionnel · economy | premium | business | first
    Cabin to price. Defaults to economy. 'premium' means premium economy.
  • cities · array · requis
    Ordered list of IATA city/airport codes for the whole trip, e.g. ['LAX','NRT','BKK','LHR','LAX']. Put '000' between two codes to mark that leg as travelled overland rather than flown, e.g. ['HAN','000','SGN','SYD'].

  Exemple d'appel

  {"name": "route_estimate", "arguments": {"cities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• route_suggest≈ 284 tokens

  Get suggested multi-stop flight routings based on regions, direction, and alliance preference. Returns up to 3 proven routing templates with bookability ratings. Great for trip planning inspiration.

  Paramètres, retour & exemple (5)

  Paramètres

  • regions · array · requis
    Regions to visit: 'asia', 'europe', 'oceania', 'americas', 'africa', 'middle east', 'south america'
  • alliance · string · optionnel
    Preferred alliance: 'star' or 'oneworld'
  • maxStops · number · optionnel
    Maximum number of stops (legs). 3-6 recommended for best bookability.
  • tripType · string · optionnel
    Trip type hint: 'honeymoon', 'backpacker', 'business', 'family', etc.
  • direction · string · optionnel · eastbound | westbound | either
    Travel direction preference

  Exemple d'appel

  {"name": "route_suggest", "arguments": {"regions": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• route_validate≈ 234 tokens

  Validate a multi-city flight routing for feasibility. Checks alliance carrier rules, identifies dead legs, warns about poison carriers, and estimates bookability. Use this before building an itinerary to catch routing problems early.

  Paramètres, retour & exemple (3)

  Paramètres

  • cities · array · requis
    Ordered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'LHR', 'LAX'])
  • alliance · string · optionnel
    Preferred alliance: 'star' or 'oneworld'
  • carriers · array · optionnel
    Optional carrier codes for each leg (e.g. ['NH', 'TG', 'BA', 'BA'])

  Exemple d'appel

  {"name": "route_validate", "arguments": {"cities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• trip_idea_create≈ 851 tokens

  Submit the customer's trip to AirTreks — a human travel consultant takes over from there. Automatically runs plan_route to attach the full routing analysis and carrier recommendations to the trip request, so the consultant starts informed, not cold. Use this when the customer is ready to get a real quote. Requires the customer's name, email, at least 2 cities (3-letter IATA codes), a departure date for every leg, and answers to AirTreks' planning questions — call once without questionsAnswers to receive the current questions to ask.

  Paramètres, retour & exemple (15)

  Paramètres

  • name · string · requis
    Customer full name (required — the consultant contacts them by name)
  • cabin · string · optionnel · economy | premium | business
    Cabin class preference
  • dates · array · requis
    Departure dates, one per leg (ISO format, e.g. '2026-09-15') — a trip with N cities needs N-1 dates, all required. If the customer is unsure, use their best estimates and set flexibleDates.
  • email · string · requis
    Customer email address (required)
  • notes · string · optionnel
    Additional notes or special requests from the customer
  • phone · string · optionnel
    Customer phone number
  • budget · string · optionnel · budget | mid | premium | business
    Budget tier
  • cities · array · requis
    Ordered list of 3-letter IATA city/airport codes (e.g. ['SFO', 'NRT', 'BKK'])
  • source · string · optionnel
    The AI platform or app this conversation is running in, lowercase (e.g. 'chatgpt', 'claude', 'perplexity'). Only tells AirTreks which channel the request came through — never put customer details here. Omit it if you don't know.
  • passengers · number · optionnel
    Number of passengers (default 1)
  • preferences · array · optionnel
    Travel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'
  • agentContext · string · optionnel
    Summary of what the AI agent learned about this trip (auto-generated routing analysis, customer preferences discussed, etc.)
  • sourceDetail · string · optionnel
    Finer detail on source, such as the app or integration name (e.g. 'trip-pricer'). Never put customer details here.
  • flexibleDates · boolean · optionnel
    Are travel dates flexible?
  • questionsAnswers · ? · optionnel
    The customer's answers to AirTreks' planning questions, keyed by question name (e.g. {"guidance": "I want expert guidance from humans"}). A JSON-encoded string of the same object is also accepted. Required, but don't guess the questions: call once without this — the response lists the current questions and their options to ask the customer.

  Exemple d'appel

  {"name": "trip_idea_create", "arguments": {"name": "texte", "dates": [], "email": "texte", "cities": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

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://mcp.airtreks.com/mcp