// SCAN REPORT

Fly Where To?

8 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated: 20 Aug 2026

0 can modify or destroy data

8 read-only

8 tools total

Community server · catalogue entry checked 20/08/2026 · full schemas captured for 8 of 8 tools

How to control Fly Where To? ↓

TOOL MAP

What Fly Where To? exposes to your agents

Read (8) Write / Execute (0) Destructive / Financial (0)

Running more than one server? Check your whole stack →

CONTEXT-WINDOW COST

What Fly Where To? costs in tokens

1,784 tokens of tool definitions, loaded on every request

0.9% of a 200k context window

474 heaviest tool: find_meetup

Full per-tool breakdown → Model it in the token calculator →

THE RISK

What can go wrong

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

POLICY

How to control Fly Where To?

PolicyLayer is an MCP gateway — it sits between your AI agents and Fly Where To?, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "airline_routes": {
    "limits": [
      {
        "counter": "airline_routes_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Fly Where To? — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON FLY WHERE TO? →

Instant setup, no code required.

FULL CATALOGUE

All 8 Fly Where To? tools

READ 8 tools

Read airline_routes The full network one airline flies: every origin with its nonstop destinations, as IATA codes. Look up by IATA Read destinations_from All airports reachable nonstop from a given origin, with the service kinds (scheduled, seasonal, charter, susp Read find_airport Look up airports by IATA/ICAO code or by name fragment. Returns code, name, country, coordinates and how many Read find_connections Multi-stop itineraries from an origin airport to either a destination airport or to any airport in a country. Read find_meetup Best meet-up airports for travellers from multiple origins, ranked by combined travel effort using the same sc Read most_connected_airports Airports ranked by number of nonstop destinations served, worldwide or within one country. Read reachable_from How far the network stretches from one airport within a stop budget: totals, breakdown by stop count and by co Read route_details Which airlines fly nonstop between two airports, with alliance, homepage and the service periods of each. Only

FAQ

Questions about Fly Where To?

Is the Fly Where To? MCP server safe to use without restrictions? +

The Fly Where To? server is primarily read-only with 8 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Fly Where To? MCP server expose? +

8 tools across 1 categories: Read. 8 are read-only. 0 can modify, create, or delete data.

How do I enforce a policy on Fly Where To?? +

Register the Fly Where To? MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Fly Where To? tool call.

Deterministic rules across all 8 Fly Where To? tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON FLY WHERE TO? →

Instant setup, no code required.

8 Fly Where To? tools catalogued and risk-classified — across an index of 46,500+ MCP servers.

// WHERE THIS COMES FROM

These policies come from Fly Where To?'s registry record.

The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →