# AirTreks MCP (remote · mcp.airtreks.com)

Multi-city flight routing intelligence — plan RTW trips, validate alliances, get carrier picks.

- Trust score: 77/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `mcp.airtreks.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/airtreks-airtreks-mcp/mcp.md), [page](https://verifymcp.io/servers/airtreks-airtreks-mcp/mcp)
- npm · `airtreks-mcp`: 93/100, [markdown](https://verifymcp.io/servers/airtreks-airtreks-mcp/airtreks-mcp.md), [page](https://verifymcp.io/servers/airtreks-airtreks-mcp/airtreks-mcp)

## Channel facts

- Endpoint: `https://mcp.airtreks.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.3`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 10 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http airtreks-airtreks-mcp 'https://mcp.airtreks.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "airtreks-airtreks-mcp": {
      "url": "https://mcp.airtreks.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "airtreks-airtreks-mcp": {
      "type": "http",
      "url": "https://mcp.airtreks.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.airtreks-airtreks-mcp]
url = "https://mcp.airtreks.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "airtreks-airtreks-mcp": {
      "type": "remote",
      "url": "https://mcp.airtreks.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add airtreks-airtreks-mcp --url 'https://mcp.airtreks.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  airtreks-airtreks-mcp:
    url: "https://mcp.airtreks.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "airtreks-airtreks-mcp": {
      "Transport": "http",
      "Url": "https://mcp.airtreks.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add airtreks-airtreks-mcp -t streamable-http -u 'https://mcp.airtreks.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "airtreks-airtreks-mcp": {
      "type": "http",
      "url": "https://mcp.airtreks.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 77, +1)

- [security] Stability: 0.97 → pass

### 2026-09-18 (score 76, +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.

### 2026-09-16 (score 75, +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.

### 2026-09-14 (score 74, +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.

### 2026-09-12 (score 73, +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.

### 2026-09-10 (score 72, +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.

### 2026-09-08 (score 71, +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.

### 2026-09-05 (score 70, +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.

## MCP tools (11)

### `plan_route` (~182 tokens)

Plan a Multi-City Route

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.

Input parameters:

- `budget` (string): Budget tier — affects carrier selection and fare strategy
- `cities` (array, required): 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'

### `trip_idea_create` (~444 tokens)

Submit a Trip Request (Consultant Handoff)

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.

Input parameters:

- `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, required): Ordered list of 3-letter IATA city/airport codes (e.g. ['SFO', 'NRT', 'BKK'])
- `dates` (array, required): 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, required): Customer email address (required)
- `flexibleDates` (boolean): Are travel dates flexible?
- `name` (string, required): 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…

### `route_estimate` (~216 tokens)

Estimate the Price of a Multi-City Route

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.

Input parameters:

- `cabin` (string): Cabin to price. Defaults to economy. 'premium' means premium economy.
- `cities` (array, required): 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…

### `fare_quote` (~282 tokens)

Price a Specific Itinerary with Live Fares

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.

Input parameters:

- `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, required): 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, required): 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.

### `itinerary_quote` (~261 tokens)

Price a Whole Multi-Stop Trip

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.

Input parameters:

- `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, required): 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, required): Departure date for each FLOWN leg, in travel order, as YYYY-MM-DD.
- `infants` (integer): Infants under 2.

### `itinerary_quote_status` (~71 tokens)

Retrieve a Multi-Stop Trip Quote

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.

Input parameters:

- `quoteReference` (string, required): The quoteReference returned by itinerary_quote.

### `route_validate` (~132 tokens)

Validate a Multi-City Routing

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.

Input parameters:

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

### `route_suggest` (~160 tokens)

Suggest Multi-Stop Routings

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.

Input parameters:

- `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, required): Regions to visit: 'asia', 'europe', 'oceania', 'americas', 'africa', 'middle east', 'south america'
- `tripType` (string): Trip type hint: 'honeymoon', 'backpacker', 'business', 'family', etc.

### `hub_check` (~109 tokens)

Check Airport Hub Connections

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.

Input parameters:

- `alliance` (string): Preferred alliance: 'star' or 'oneworld'
- `from` (string, required): Origin IATA airport code (e.g. 'SYD')
- `to` (string, required): Destination IATA airport code (e.g. 'JFK')

### `fare_product_match` (~111 tokens)

Match the Right Fare Product

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.

Input parameters:

- `cities` (array, required): 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)?

### `custom_route_build` (~198 tokens)

Build a Custom Segmented Route

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.

Input parameters:

- `budget` (string): Budget tier: 'budget' prioritizes LCCs, 'business' prioritizes J-class product quality
- `cities` (array, required): 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'

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/airtreks-airtreks-mcp/mcp#diagnostics

## Score history

- 2026-09-20: 77
- 2026-09-19: 76
- 2026-09-18: 76
- 2026-09-17: 75
- 2026-09-16: 75
- 2026-09-15: 74
- 2026-09-14: 74
- 2026-09-13: 73
- 2026-09-12: 73
- 2026-09-11: 72
- 2026-09-10: 72
- 2026-09-09: 71
- 2026-09-08: 71
- 2026-09-07: 70
- 2026-09-06: 70
- 2026-09-05: 70
- 2026-09-04: 69
- 2026-09-03: 69
- 2026-09-02: 68
- 2026-09-01: 68
- 2026-08-31: 67
- 2026-08-30: 67
- 2026-08-29: 66
- 2026-08-28: 66
- 2026-08-27: 65
- 2026-08-26: 65
- 2026-08-25: 63
- 2026-08-24: 62
- 2026-08-23: 62
- 2026-08-22: 61

## Common questions

### 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 hosted endpoint (https://mcp.airtreks.com/mcp).

### Is the AirTreks MCP server safe to use?

AirTreks MCP scores 77 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,166 tokens of context every time the server is loaded.

### Does the AirTreks MCP server require authentication?

No. We connected to AirTreks MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### 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.

## Links

- Remote endpoint: https://mcp.airtreks.com/mcp
- Repository: https://github.com/Airtreks/airtreks-mcp
- Website: https://airtreks.com/
- Changelog RSS feed: https://verifymcp.io/servers/airtreks-airtreks-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/airtreks-airtreks-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/airtreks-airtreks-mcp/mcp