AirTreks MCP
REMOTE · MCP.AIRTREKS.COM · 2 COMPONENTS · SCANNED AUG 3
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 against the live server, and we only credit what we can confirm. How we score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · mcp.airtreks.com
claude mcp add --transport http sekeener-airtreks-mcp https://mcp.airtreks.com/mcp
[mcp_servers.sekeener-airtreks-mcp] url = "https://mcp.airtreks.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sekeener-airtreks-mcp": {
"type": "remote",
"url": "https://mcp.airtreks.com/mcp",
"enabled": true
}
}
} openclaw mcp add sekeener-airtreks-mcp --url https://mcp.airtreks.com/mcp --transport streamable-http
mcp_servers:
sekeener-airtreks-mcp:
url: "https://mcp.airtreks.com/mcp" {
"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.
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.
- 3 Aug 26 +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.
- 31 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 +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.
- 27 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 62
First indexed and scored.
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 3 Aug 2026 · Probed https://mcp.airtreks.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.airtreks.com | CN=YR2,O=Let's Encrypt,C=US | 1 Aug 2026 | 30 Oct 2026 | RSA 2048 | SHA256-RSA | 5525a7551472c72018af1f26238d6f8f307 |
| SANs: mcp.airtreks.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
DNSSEC insecure
Validation of mcp.airtreks.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| airtreks.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.airtreks.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.airtreks.com/mcp | HTTPS enforced | 301 | https://mcp.airtreks.com/mcp |
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.
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.
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.
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_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.