Skip to content

air-routes.com

by idragulin · remote · no sign-in to list tools · v1.28.1 · published by GitHub user idragulin

Global scheduled passenger flight routes: which exist, direct or connecting, and days flown.

Changes · 1
CompareRegistry entry

4 tools: 1 change things and 3 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http air-routes https://air-routes.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Changes things 1Claude Code: ask
  • route_detailDetail for one route (e.g.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Detail for one route (e.g. 'OTP-BCN'): airlines, schedule and seasonality. Data: scheduled passenger routes operating now, with seasonality labels — not fares, not booking, not date-specific schedules.
Only reads 3Claude Code: allow
  • airport_destinationsList every direct flight from an airport (airport code), with full schedule detail per destination: airlines, schedule (day + times), flying_min, seasonality, booking URL.No findings

    Why it is in this group

    • The description's first verb is "list": a word for reading.
    Description, as the server wrote it
    List every direct flight from an airport (airport code), with full schedule detail per destination: airlines, schedule (day + times), flying_min, seasonality, booking URL. Prefer this over N× route_detail when planning from one hub. Data: scheduled passenger routes operating now, with seasonality labels — not fares, not booking, not date-specific schedules.
  • find_connectionsFind flight connections between two airports (airport codes).No findings

    Why it is in this group

    • The name "find_connections" says "find": a word for reading.
    Description, as the server wrote it
    Find flight connections between two airports (airport codes). Returns the fewest-stops tier that has any option: direct if available, else one-stop, else two-stop (up to max_stops), never a mix. Options sort by flying time; layover tiers cap at 7. Charter flights (tour-operator capacity, not bookable seat-only with the airline) are excluded unless include_charter=true, and never appear inside multi-leg itineraries. Data: scheduled passenger routes operating now, with seasonality labels — not fares, not booking, not date-specific schedules.
  • resolve_airportResolve a free-text city or airport name to airport codes (e.g.No findings

    Why it is in this group

    • The name "resolve_airport" says "resolve": a word for reading.
    Description, as the server wrote it
    Resolve a free-text city or airport name to airport codes (e.g. 'london' → LHR, LGW, STN, LTN, LCY). Use before other tools when the user gives city names. airport_code is the 3-letter IATA airport code.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.28.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http air-routes https://air-routes.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__air-routes__find_connections",
      "mcp__air-routes__airport_destinations",
      "mcp__air-routes__resolve_airport"
    ],
    "ask": [
      "mcp__air-routes__route_detail"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as air-routes. Review it before you use it.