AirTreks MCP
NPM · AIRTREKS-MCP · 2 COMPONENTS · SCANNED SEP 20
Multi-city flight routing intelligence — plan RTW trips, validate alliances, get carrier picks.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Airtreks/airtreks-mcp). View diagnostics → Pass
- Clear OSI-approved license (AGPL-3.0-only).Pass
- Actively maintained (last published 26 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2166 tokens (~196/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the AirTreks MCP server?
AirTreks MCP runs locally as an npm package, launched with npx -y airtreks-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · airtreks-mcp
claude mcp add airtreks-airtreks-mcp -- npx -y airtreks-mcp
{
"mcpServers": {
"airtreks-airtreks-mcp": {
"command": "npx",
"args": [
"-y",
"airtreks-mcp"
]
}
}
} {
"servers": {
"airtreks-airtreks-mcp": {
"command": "npx",
"args": [
"-y",
"airtreks-mcp"
]
}
}
} codex mcp add airtreks-airtreks-mcp -- npx -y airtreks-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"airtreks-airtreks-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"airtreks-mcp"
],
"enabled": true
}
}
} openclaw mcp add airtreks-airtreks-mcp --command npx --arg -y --arg airtreks-mcp
mcp_servers:
airtreks-airtreks-mcp:
command: "npx"
args: ["-y", "airtreks-mcp"] {
"McpServers": {
"airtreks-airtreks-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"airtreks-mcp"
]
}
}
} assistant mcp add airtreks-airtreks-mcp -t stdio -c npx -a -y airtreks-mcp
{
"mcpServers": {
"airtreks-airtreks-mcp": {
"command": "npx",
"args": [
"-y",
"airtreks-mcp"
]
}
}
} 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.
- 20 Sept 26 +1
- Stability: 0.97 → pass security
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Analysed npm/airtreks-mcp@1.2.3
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Airtreks/airtreks-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Airtreks/airtreks-mcp/.github/workflows/release.yml@refs/tags/v1.2.3 |
| Rekor log index | 2580030593 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:0858537d7d783812d83358e30de0d628f0b6cb6324ea41562db5ac79101ea203dea3665f699221bb3081a0f976e40ec1c21e24818ae65692db5bc56bc |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
custom_route_build Build a Custom Segmented Route ~198
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | Budget tier: 'budget' prioritizes LCCs, 'business' prioritizes J-class product quality |
| cities | array | yes | Ordered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'CMB', 'NBO', 'LIS', 'LAX']) |
| pax | number | – | Number of passengers |
| preferences | array | – | Preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok' |
No output schema declared.
No examples provided.
fare_product_match Match the Right Fare Product ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| cities | array | yes | Ordered list of IATA city/airport codes |
| includeBacktracking | boolean | – | Does the route backtrack or zigzag between regions? |
| isOneDirection | boolean | – | Is the route traveling continuously in one direction (east or west)? |
No output schema declared.
No examples provided.
fare_quote Price a Specific Itinerary with Live Fares ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Adult travellers. Defaults to 1. |
| cabin | string | – | Cabin to price. Defaults to economy. 'premium' means premium economy. |
| children | integer | – | Children aged 2-11. |
| cities | array | yes | 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. |
| dates | array | yes | Departure date for each FLOWN leg, in travel order, as YYYY-MM-DD. Overland legs marked with '000' do not take a date. |
| infants | integer | – | Infants under 2. |
| maxOptions | integer | – | How many fare options to return. Defaults to 5. |
No output schema declared.
No examples provided.
hub_check Check Airport Hub Connections ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| alliance | string | – | Preferred alliance: 'star' or 'oneworld' |
| from | string | yes | Origin IATA airport code (e.g. 'SYD') |
| to | string | yes | Destination IATA airport code (e.g. 'JFK') |
No output schema declared.
No examples provided.
itinerary_quote Price a Whole Multi-Stop Trip ~261
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 and you fetch the result with itinerary_quote_status. Keep that reference — it is the only way to retrieve the quote.
| Name | Type | Req | Description |
|---|---|---|---|
| adults | integer | – | Adult travellers. Defaults to 1. |
| cabin | string | – | Cabin to price. Defaults to economy. 'premium' means premium economy. |
| children | integer | – | Children aged 2-11. |
| cities | array | yes | 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. |
| dates | array | yes | Departure date for each FLOWN leg, in travel order, as YYYY-MM-DD. |
| infants | integer | – | Infants under 2. |
No output schema declared.
No examples provided.
itinerary_quote_status Retrieve a Multi-Stop Trip Quote ~71
Fetch the result of an itinerary_quote using the quoteReference it returned. Returns status 'pending' with how long to wait, or the finished options. Costs nothing and does no searching, so poll it rather than starting a second quote.
| Name | Type | Req | Description |
|---|---|---|---|
| quoteReference | string | yes | The quoteReference returned by itinerary_quote. |
No output schema declared.
No examples provided.
plan_route Plan a Multi-City Route ~182
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.
| Name | Type | Req | Description |
|---|---|---|---|
| budget | string | – | Budget tier — affects carrier selection and fare strategy |
| cities | array | yes | Ordered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'LIS', 'LAX']) |
| pax | number | – | Number of passengers |
| preferences | array | – | Travel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok' |
No output schema declared.
No examples provided.
route_estimate Estimate the Price of a Multi-City Route ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| cabin | string | – | Cabin to price. Defaults to economy. 'premium' means premium economy. |
| cities | array | yes | 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','00… |
No output schema declared.
No examples provided.
route_suggest Suggest Multi-Stop Routings ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| alliance | string | – | Preferred alliance: 'star' or 'oneworld' |
| direction | string | – | Travel direction preference |
| maxStops | number | – | Maximum number of stops (legs). 3-6 recommended for best bookability. |
| regions | array | yes | Regions to visit: 'asia', 'europe', 'oceania', 'americas', 'africa', 'middle east', 'south america' |
| tripType | string | – | Trip type hint: 'honeymoon', 'backpacker', 'business', 'family', etc. |
No output schema declared.
No examples provided.
route_validate Validate a Multi-City Routing ~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.
| Name | Type | Req | Description |
|---|---|---|---|
| alliance | string | – | Preferred alliance: 'star' or 'oneworld' |
| carriers | array | – | Optional carrier codes for each leg (e.g. ['NH', 'TG', 'BA', 'BA']) |
| cities | array | yes | Ordered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'LHR', 'LAX']) |
No output schema declared.
No examples provided.
trip_idea_create Submit a Trip Request (Consultant Handoff) ~444
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agentContext | string | – | Summary of what the AI agent learned about this trip (auto-generated routing analysis, customer preferences discussed, etc.) |
| budget | string | – | Budget tier |
| cabin | string | – | Cabin class preference |
| cities | array | yes | Ordered list of 3-letter IATA city/airport codes (e.g. ['SFO', 'NRT', 'BKK']) |
| dates | array | yes | 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. |
| string | yes | Customer email address (required) | |
| flexibleDates | boolean | – | Are travel dates flexible? |
| name | string | yes | Customer full name (required — the consultant contacts them by name) |
| notes | string | – | Additional notes or special requests from the customer |
| passengers | number | – | Number of passengers (default 1) |
| phone | string | – | Customer phone number |
| preferences | array | – | 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"}). A JSON-encoded string of the same object is also accepted. Re… |
No output schema declared.
No examples provided.
What is the AirTreks MCP server?
AirTreks MCP is listed in the public MCP registry as io.github.Airtreks/airtreks-mcp. Multi-city flight routing intelligence, plan RTW trips, validate alliances, get carrier picks. This page covers its npm package (airtreks-mcp).
Is the AirTreks MCP server safe to use?
AirTreks MCP scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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,166 tokens of context every time the server is loaded.
Is the AirTreks MCP server still maintained?
AirTreks MCP is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the AirTreks MCP server under?
AirTreks MCP declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.