_ registry / mcp http-sse · checked 45m ago

airtreks

https://mcp.airtreks.com

Registry code: 70b71b7e8a2d6a81

api record

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

from a public catalogue that lists it, not from the operator

endpoint
https://mcp.airtreks.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is airtreks live?
Yes — it answered the hub's last check (checked 45m ago). It answered 100% of checks over the last 30 days.
Is airtreks free to use?
Yes — the hub reached it with no key and no payment.
What tools does airtreks have?
11 tools: hub_check, custom_route_build, route_estimate, route_suggest, trip_idea_create, itinerary_quote, fare_product_match, route_validate, ….
Is airtreks safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.5%

90 days 99.7%· all time 99.7%

latency
397ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 312 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • unknown → live
_ what it is for
topic
maps travel & places travel & transport
used for
  • plan a round-the-world flight route
  • validate a multi-city routing
  • get fares for a multi-stop itinerary
  • estimate price of a multi-city trip
  • hand a trip to a travel consultant
takes → gives
data → data
tools
10 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 11 tools
11 never probed 0 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • hub_check reads unknown 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "from",
    "to"
  ],
  "properties": {
    "to": {
      "type": "string",
      "description": "Destination IATA airport code (e.g. 'JFK')"
    },
    "from": {
      "type": "string",
      "description": "Origin IATA airport code (e.g. 'SYD')"
    },
    "alliance": {
      "type": "string",
      "description": "Preferred alliance: 'star' or 'oneworld'"
    }
  }
}
    arguments 22 lines
  • custom_route_build reads unknown 19h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "cities"
  ],
  "properties": {
    "pax": {
      "type": "number",
      "description": "Number of passengers"
    },
    "budget": {
      "enum": [
        "budget",
        "mid",
        "premium",
        "business"
      ],
      "type": "string",
      "description": "Budget tier: 'budget' prioritizes LCCs, 'business' prioritizes J-class product quality"
    },
    "cities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ordered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'CMB', 'NBO', 'LIS', 'LAX'])"
    },
    "preferences": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'"
    }
  }
}
    arguments 37 lines
  • route_estimate reads unknown 19h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "cities"
  ],
  "properties": {
    "cabin": {
      "enum": [
        "economy",
        "premium",
        "business",
        "first"
      ],
      "type": "string",
      "description": "Cabin to price. Defaults to economy. 'premium' means premium economy."
    },
    "cities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 14,
      "minItems": 2,
      "description": "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','000','SGN','SYD']."
    }
  }
}
    arguments 28 lines
  • route_suggest reads unknown 19h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "regions"
  ],
  "properties": {
    "regions": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Regions to visit: 'asia', 'europe', 'oceania', 'americas', 'africa', 'middle east', 'south america'"
    },
    "alliance": {
      "type": "string",
      "description": "Preferred alliance: 'star' or 'oneworld'"
    },
    "maxStops": {
      "type": "number",
      "description": "Maximum number of stops (legs). 3-6 recommended for best bookability."
    },
    "tripType": {
      "type": "string",
      "description": "Trip type hint: 'honeymoon', 'backpacker', 'business', 'family', etc."
    },
    "direction": {
      "enum": [
        "eastbound",
        "westbound",
        "either"
      ],
      "type": "string",
      "description": "Travel direction preference"
    }
  }
}
    arguments 37 lines
  • trip_idea_create changes data unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "email",
    "name",
    "cities",
    "dates"
  ],
  "properties": {
    "name": {
      "type": "string",
      "description": "Customer full name (required — the consultant contacts them by name)"
    },
    "cabin": {
      "enum": [
        "economy",
        "premium",
        "business"
      ],
      "type": "string",
      "description": "Cabin class preference"
    },
    "dates": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "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": {
      "type": "string",
      "description": "Customer email address (required)"
    },
    "notes": {
      "type": "string",
      "description": "Additional notes or special requests from the customer"
    },
    "phone": {
      "type": "string",
      "description": "Customer phone number"
    },
    "budget": {
      "enum": [
        "budget",
        "mid",
        "premium",
        "business"
      ],
      "type": "string",
      "description": "Budget tier"
    },
    "cities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ordered list of 3-letter IATA city/airport codes (e.g. ['SFO', 'NRT', 'BKK'])"
    },
    "source": {
      "type": "string",
      "description": "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 here. Omit it if you don't know."
    },
    "passengers": {
      "type": "number",
      "description": "Number of passengers (default 1)"
    },
    "preferences": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Travel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'"
    },
    "agentContext": {
      "type": "string",
      "description": "Summary of what the AI agent learned about this trip (auto-generated routing analysis, customer preferences discussed, etc.)"
    },
    "sourceDetail": {
      "type": "string",
      "description": "Finer detail on source, such as the app or integration name (e.g. 'trip-pricer'). Never put customer details here."
    },
    "flexibleDates": {
      "type": "boolean",
      "description": "Are travel dates flexible?"
    },
    "questionsAnswers": {
      "anyOf": [
        {
          "type": "object",
          "propertyNames": {
            "type": "string"
          },
          "additionalProperties": {
            "type": "string"
          }
        },
        {
          "type": "string"
        }
      ],
      "description": "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. Required, but don't guess the questions: call once without this — the response lists the current questions and their options to ask the customer."
    }
  }
}
    arguments 106 lines
  • itinerary_quote reads unknown 28d ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "cities",
    "dates"
  ],
  "properties": {
    "cabin": {
      "enum": [
        "economy",
        "premium",
        "business",
        "first"
      ],
      "type": "string",
      "description": "Cabin to price. Defaults to economy. 'premium' means premium economy."
    },
    "dates": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Departure date for each FLOWN leg, in travel order, as YYYY-MM-DD."
    },
    "adults": {
      "type": "integer",
      "maximum": 9,
      "minimum": 1,
      "description": "Adult travellers. Defaults to 1."
    },
    "cities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 12,
      "minItems": 2,
      "description": "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."
    },
    "infants": {
      "type": "integer",
      "maximum": 8,
      "minimum": 0,
      "description": "Infants under 2."
    },
    "children": {
      "type": "integer",
      "maximum": 8,
      "minimum": 0,
      "description": "Children aged 2-11."
    }
  }
}
    arguments 55 lines
  • fare_product_match reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "cities"
  ],
  "properties": {
    "cities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ordered list of IATA city/airport codes"
    },
    "isOneDirection": {
      "type": "boolean",
      "description": "Is the route traveling continuously in one direction (east or west)?"
    },
    "includeBacktracking": {
      "type": "boolean",
      "description": "Does the route backtrack or zigzag between regions?"
    }
  }
}
    arguments 24 lines
  • route_validate reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "cities"
  ],
  "properties": {
    "cities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ordered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'LHR', 'LAX'])"
    },
    "alliance": {
      "type": "string",
      "description": "Preferred alliance: 'star' or 'oneworld'"
    },
    "carriers": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Optional carrier codes for each leg (e.g. ['NH', 'TG', 'BA', 'BA'])"
    }
  }
}
    arguments 27 lines
  • itinerary_quote_status reads unknown 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "quoteReference"
  ],
  "properties": {
    "quoteReference": {
      "type": "string",
      "minLength": 20,
      "description": "The quoteReference returned by itinerary_quote."
    }
  }
}
    arguments 14 lines
  • plan_route reads unknown 4h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "cities"
  ],
  "properties": {
    "pax": {
      "type": "number",
      "description": "Number of passengers"
    },
    "budget": {
      "enum": [
        "budget",
        "mid",
        "premium",
        "business"
      ],
      "type": "string",
      "description": "Budget tier — affects carrier selection and fare strategy"
    },
    "cities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Ordered list of IATA city/airport codes (e.g. ['LAX', 'NRT', 'BKK', 'LIS', 'LAX'])"
    },
    "preferences": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "description": "Travel preferences: 'no-lcc', 'lounge-access', 'short-layovers', 'surface-ok'"
    }
  }
}
    arguments 37 lines
  • fare_quote reads unknown 15h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "cities",
    "dates"
  ],
  "properties": {
    "cabin": {
      "enum": [
        "economy",
        "premium",
        "business",
        "first"
      ],
      "type": "string",
      "description": "Cabin to price. Defaults to economy. 'premium' means premium economy."
    },
    "dates": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "minItems": 1,
      "description": "Departure date for each FLOWN leg, in travel order, as YYYY-MM-DD. Overland legs marked with '000' do not take a date."
    },
    "adults": {
      "type": "integer",
      "maximum": 9,
      "minimum": 1,
      "description": "Adult travellers. Defaults to 1."
    },
    "cities": {
      "type": "array",
      "items": {
        "type": "string"
      },
      "maxItems": 10,
      "minItems": 2,
      "description": "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."
    },
    "infants": {
      "type": "integer",
      "maximum": 8,
      "minimum": 0,
      "description": "Infants under 2."
    },
    "children": {
      "type": "integer",
      "maximum": 8,
      "minimum": 0,
      "description": "Children aged 2-11."
    },
    "maxOptions": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "How many fare options to return. Defaults to 5."
    }
  }
}
    arguments 61 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 70b71b7e8a2d6a81.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/70b71b7e8a2d6a81/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/70b71b7e8a2d6a81/badge.svg)](https://brick.blue/agent/70b71b7e8a2d6a81?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.