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

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

- Trust score: 66/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

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

## Channel facts

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

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

- **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 6 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**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 892 tokens (~148/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

```json
{
  "mcpServers": {
    "sekeener-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-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server
- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 63, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 62)

First indexed and scored.

## MCP tools (6)

### `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'

### `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/sekeener-airtreks-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 65
- 2026-07-31: 65
- 2026-07-29: 64
- 2026-07-28: 63
- 2026-07-27: 63
- 2026-07-26: 62

## Links

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