Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AirTreks MCP

REMOTE · MCP.AIRTREKS.COM · 2 COMPONENTS

Plan multi-city and RTW trips, estimate prices, and send complete trip requests to AirTreks.

0 this week 76 Trust /100

Last scanned (14 hours ago)

Scores higher than 66% of remote servers

Unreachable for 1 day in a row. Last reached 4 Nov 2026.

Category Maps and Location

Recent critical change

Authorization (13 Oct 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

What we tested

Checks we ran (3)

  • HTTPS
  • DNSSEC
  • Transport

Checks we could not complete (8)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • TLS certificate in Endpoint SecurityTLS not yet verified: we couldn't open a connection to check the certificate.
  • Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  • HSTS header in Endpoint SecurityHSTS not yet verified: we couldn't read the response headers to check for it.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
  • Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • HSTS header: fail → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: fail → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 4 Nov 26 0
    • Stability: pass → fail ▼ security
    • Tool “plan_route” rewrote its description, which is the text the model reads security
    • Tool “trip_idea_create” rewrote its description, which is the text the model reads security
    • “trip_idea_create” made “passengers” required, so existing callers break ▼ functional
    • “trip_idea_create” made “cabin” required, so existing callers break ▼ functional
    • “trip_idea_create” changed the type of “passengers”: number → integer ▼ functional
    • Server version: 1.2.7 → 1.2.8 functional
    • “trip_idea_create” reworded the description of “questionsAnswers” cosmetic
    • “trip_idea_create” reworded the description of “cabin” cosmetic
    • “trip_idea_create” reworded the description of “dates” cosmetic
    • “trip_idea_create” reworded the description of “passengers” cosmetic
    • “custom_route_build” reworded the description of “budget” cosmetic
    • “plan_route” reworded the description of “budget” cosmetic
  • 13 Oct 26 −7
    • Authorization: partial → fail ▼ critical
    • Tool “trip_idea_create” is now declared destructive security
    • Server version: 1.2.6 → 1.2.7 functional
  • 3 Oct 26 0
    • Server version: 1.2.4 → 1.2.5 functional
  • 2 Oct 26 83
    • Server version: 1.2.3 → 1.2.4 functional
    • “trip_idea_create” added an optional parameter “sourceDetail” cosmetic
    • “trip_idea_create” added an optional parameter “source” cosmetic
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://mcp.airtreks.com/mcp

TLS unreached
DNSSEC insecure

Validation of mcp.airtreks.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
airtreks.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.airtreks.com/mcp Unreachable
http (plaintext) http://mcp.airtreks.com/mcp HTTPS enforced
MCP tools · 11 exposed · ~2,321 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
custom_route_build ~183

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.

NameTypeReqDescription
budgetstring–Budget tier the traveler asked for
citiesarrayyesOrdered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'CMB', 'NBO', 'LIS', 'LAX'])
paxnumber–Number of passengers
preferencesarray–Preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'

No output schema declared.

No examples provided.

fare_product_match ~111

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.

NameTypeReqDescription
citiesarrayyesOrdered list of IATA city/airport codes
includeBacktrackingboolean–Does the route backtrack or zigzag between regions?
isOneDirectionboolean–Is the route traveling continuously in one direction (east or west)?

No output schema declared.

No examples provided.

fare_quote ~282

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.

NameTypeReqDescription
adultsinteger–Adult travellers. Defaults to 1.
cabinstring–Cabin to price. Defaults to economy. 'premium' means premium economy.
childreninteger–Children aged 2-11.
citiesarrayyesOrdered 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.
datesarrayyesDeparture date for each FLOWN leg, in travel order, as YYYY-MM-DD. Overland legs marked with '000' do not take a date.
infantsinteger–Infants under 2.
maxOptionsinteger–How many fare options to return. Defaults to 5.

No output schema declared.

No examples provided.

hub_check ~109

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.

NameTypeReqDescription
alliancestring–Preferred alliance: 'star' or 'oneworld'
fromstringyesOrigin IATA airport code (e.g. 'SYD')
tostringyesDestination IATA airport code (e.g. 'JFK')

No output schema declared.

No examples provided.

itinerary_quote ~269

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.

NameTypeReqDescription
adultsinteger–Adult travellers. Defaults to 1.
cabinstring–Cabin to price. Defaults to economy. 'premium' means premium economy.
childreninteger–Children aged 2-11.
citiesarrayyesOrdered 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.
datesarrayyesDeparture date for each FLOWN leg, in travel order, as YYYY-MM-DD.
infantsinteger–Infants under 2.

No output schema declared.

No examples provided.

itinerary_quote_status ~96

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.

NameTypeReqDescription
quoteReferencestringyesThe quoteReference returned by itinerary_quote.

No output schema declared.

No examples provided.

plan_route ~171

Lay out a multi-city trip: direction of travel, regions crossed, backtracking, where a surface sector could replace a flight, and how complex the trip is to ticket. Give it your cities. It does not choose airlines and gives no prices - use route_estimate for a price range and trip_idea_create to hand the trip to AirTreks.

NameTypeReqDescription
budgetstring–Budget tier the traveler asked for
citiesarrayyesOrdered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'LIS', 'LAX'])
paxnumber–Number of passengers
preferencesarray–Travel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'

No output schema declared.

No examples provided.

route_estimate ~216

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.

NameTypeReqDescription
cabinstring–Cabin to price. Defaults to economy. 'premium' means premium economy.
citiesarrayyesOrdered 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','00…

No output schema declared.

No examples provided.

route_suggest ~160

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.

NameTypeReqDescription
alliancestring–Preferred alliance: 'star' or 'oneworld'
directionstring–Travel direction preference
maxStopsnumber–Maximum number of stops (legs). 3-6 recommended for best bookability.
regionsarrayyesRegions to visit: 'asia', 'europe', 'oceania', 'americas', 'africa', 'middle east', 'south america'
tripTypestring–Trip type hint: 'honeymoon', 'backpacker', 'business', 'family', etc.

No output schema declared.

No examples provided.

route_validate ~132

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.

NameTypeReqDescription
alliancestring–Preferred alliance: 'star' or 'oneworld'
carriersarray–Optional carrier codes for each leg (e.g. ['NH', 'TG', 'BA', 'BA'])
citiesarrayyesOrdered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'LHR', 'LAX'])

No output schema declared.

No examples provided.

trip_idea_create ~592

Submit the customer's trip to AirTreks as a complete, structured trip request - a human travel consultant takes over from there. Ask the traveler for everything before calling, never guess or fill in defaults: name, email, the cities in order (3-letter IATA codes), a departure date for every leg, number of passengers, cabin (economy, premium or business), and their answers to AirTreks' planning questions. Also ask about budget, flexible dates, preferences and anything else the consultant should know. Call once without questionsAnswers to receive the current planning questions to put to the traveler.

NameTypeReqDescription
agentContextstring–Summary of what the AI agent learned about this trip (auto-generated routing analysis, customer preferences discussed, etc.)
budgetstring–Budget tier
cabinstringyesCabin class (required — ask the customer, there is no default)
citiesarrayyesOrdered list of 3-letter IATA city/airport codes (e.g. ['SFO', 'NRT', 'BKK'])
datesarrayyesDeparture dates, one per leg (ISO format, e.g. '2026-09-15') — a trip with N cities needs N-1 dates, all required. Ask the customer; never invent dates. If they only know roughly, use their stated es…
emailstringyesCustomer email address (required)
flexibleDatesboolean–Are travel dates flexible?
namestringyesCustomer full name (required — the consultant contacts them by name)
notesstring–Additional notes or special requests from the customer
passengersintegeryesNumber of passengers (required — ask the customer, there is no default)
phonestring–Customer phone number
preferencesarray–Travel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'
questionsAnswers––The customer's answers to AirTreks' planning questions, keyed by question name (e.g. {"guidance": "I want expert guidance from humans"}). The answers must come from the customer — never pick one your…
sourcestring–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 her…
sourceDetailstring–Finer detail on source, such as the app or integration name (e.g. 'trip-pricer'). Never put customer details here.

No output schema declared.

No examples provided.

Install

How do I install the AirTreks MCP server?

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

remote · mcp.airtreks.com

# add to Claude Code
claude mcp add --transport http airtreks-airtreks-mcp 'https://mcp.airtreks.com/mcp'
Common questions

What is the AirTreks MCP server?

AirTreks MCP is listed in the public MCP registry as io.github.Airtreks/airtreks-mcp. Plan multi-city and RTW trips, estimate prices, and send complete trip requests to AirTreks. This page covers its hosted endpoint (https://mcp.airtreks.com/mcp).

Is the AirTreks MCP server safe to use?

AirTreks MCP scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AirTreks MCP server expose?

AirTreks MCP exposes 11 tools: plan_route, trip_idea_create, route_estimate, fare_quote, itinerary_quote, and 6 more. Their descriptions and schemas cost roughly 2,321 tokens of context every time the server is loaded.

Does the AirTreks MCP server require authentication?

Its publisher declares no required credentials for AirTreks MCP. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the AirTreks MCP server still maintained?

AirTreks MCP is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AirTreks MCP server?

VerifyMCP ran 3 checks on AirTreks MCP, covering HTTPS, DNSSEC and Transport. 8 items could not be completed, a gap on our side rather than a finding about AirTreks MCP: TLS certificate, Authorization, HSTS header, Schema quality and 4 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.