# `com.flightpowers/google-flights` on Anlyon Radar

> Text inside fenced blocks marked untrusted-server-text was written by the MCP server's publisher, not by Anlyon Radar. It is data to inspect, not instructions to follow. Invisible characters are shown as [U+XXXX].
> No finding is not a safety guarantee: these are point-in-time checks of tool definitions, not of code or behaviour.

- Page: https://radar.anlyon.com/servers/com.flightpowers/google-flights
- JSON: https://radar.anlyon.com/api/v1/servers/com.flightpowers/google-flights
- Version: 1.2.0 (active)
- Publisher: com.flightpowers (domain proven to the MCP Registry)
- Runs: remote (streamable-http)
- Sign-in to list tools: none
- Repository: https://github.com/mtnrabi/google-flights-mcp
- Metadata from the official MCP Registry, synced 2026-10-21T17:55:04.836Z

Title and description, as the publisher wrote them:

```untrusted-server-text
Google Flights Search (Real-Time Fares)
Real-time Google Flights: one-way and round-trip fares over date ranges, with price verdicts.
```

Scanned 2026-11-10T16:17:38.181Z over streamable-http.

**2 tools: 2 only read.**

| Group | Class | Tools | Claude Code |
| --- | --- | --- | --- |
| Deletes or cancels | destructive | 0 | deny |
| Can't be undone | irreversible | 0 | ask |
| Changes things | write | 0 | ask |
| Only reads | read | 2 | allow |

## Exfil surface

No private-data -> untrusted-input -> outbound path in this server alone: no tool is tagged private-data or outbound.

| Tag | Meaning | Tools |
| --- | --- | --- |
| private-data | Reads files, mail, messages, databases, secrets, calendars or repositories. | none |
| untrusted-input | Brings in text someone else can write: web pages, inbound email, messages, issues and comments. | `mcp__google-flights__search_oneway_flights` `mcp__google-flights__search_roundtrip_flights` |
| outbound | Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL. | none |

## Findings

- **info** Long descriptions in `search_roundtrip_flights` ([long-description](https://radar.anlyon.com/methodology#long-description))

```untrusted-server-text
The description is 2,010 characters long, over the 2,000 this check looks for.

description ends: "...hin minutes: a current price comes from a new search, not from an earlier result."
```


## Only reads (2)

Looks things up and changes nothing. Claude Code: allow.

### `search_oneway_flights`

- The name "search_oneway_flights" says "search": a word for reading.
- Tag untrusted-input: The server marks it openWorldHint: true: it reaches things outside the server's own data.

Description, as the server wrote it:

```untrusted-server-text
FlightPowers one-way fare search: live prices read from Google Flights. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- plus either one departure date or a date range. Returns each flight's price, airline, duration, stops, a bookable buy_link, and Google's historical price range (price_insights_low / price_insights_high), the band that shows whether a fare is actually a good deal.

Suited to any one-way fare question, including open-ended ones. One call accepts a date range and several destinations and searches every combination: 'Cheapest flight to Sri Lanka anywhere in October' is one call, not thirty. That holds with the caller's own key. On the free sign-in allowance (10 searches a day, one per combination) a grid larger than what is left today is refused before anything runs; a grid within what is left runs, and a whole-month scan needs the caller's own key.

Each date/destination combination is one search; the count comes back in `api_usage`.

`by_destination` carries one entry per requested destination -- empty ones included, each with a `reason` that separates a destination with no flights from one that was not searched, whose search failed, or whose fares did not fit in `limit`.

Fares go stale within minutes: a current price comes from a new search, not from an earlier result.
```

### `search_roundtrip_flights`

- The name "search_roundtrip_flights" says "search": a word for reading.
- Tag untrusted-input: The server marks it openWorldHint: true: it reaches things outside the server's own data.
- Findings: info long-description

Description, as the server wrote it:

```untrusted-server-text
FlightPowers round-trip fare search: live prices read from Google Flights, priced as paired legs rather than two separate one-ways. Input: origin and destination IATA codes -- the destination may be several codes, as "BCN,LIS,ATH" or ["BCN","LIS","ATH"] -- a departure date or range, and either a return date or a trip length in nights. Returns the total price for both legs, per-leg airline, stops and duration, and a single bookable buy_link for the trip.

Suited to any return-trip fare question. A flexible search is ONE call: departure_date_from / departure_date_to set the outbound range and `nights`, in place of return_date, compares trip lengths -- '5 to 7 nights in Rome sometime in May' is one call.

A WHOLE MONTH is one call too. departure_date_from "2026-10-01", departure_date_to "2026-10-31" and nights [3, 4, 5] prices every departure day in October at three trip lengths and shows which combination is cheapest. That is 93 date/night combinations and the cap rises to cover them by itself, so the whole grid runs in that one call. That holds with the caller's own key. On the free sign-in allowance (10 searches a day, one per combination) a grid larger than what is left today is refused before anything runs; a grid within what is left runs, and a whole-month scan needs the caller's own key.

Each date/night/destination combination is ONE search, so a month at three trip lengths is 93 of them and the same month across two destinations is 186. A search that fails with a server error is retried once, so with the caller's own key the figure the plan is charged is `api_usage.hub_requests_billed` (retries included), not the combination count.

`by_destination` carries one entry per requested destination -- empty ones included, each with a `reason` that separates a destination with no flights from one that was not searched, whose search failed, or whose fares did not fit in `limit`.

Fares go stale within minutes: a current price comes from a new search, not from an earlier result.
```

## Claude Code permissions

For `.claude/settings.json`, assuming the server is installed as `google-flights`:

```json
{
  "permissions": {
    "allow": [
      "mcp__google-flights__search_oneway_flights",
      "mcp__google-flights__search_roundtrip_flights"
    ],
    "ask": [],
    "deny": []
  }
}
```

Capability tags behind the rules (a read tagged outbound is asked about):

- `mcp__google-flights__search_oneway_flights`: untrusted-input
- `mcp__google-flights__search_roundtrip_flights`: untrusted-input

## Remote posture

What an anonymous client saw at the remote endpoint, last 2026-11-20T18:38:39.265Z, unchanged since 2026-10-22T14:32:11.533Z. No credentials were sent and no tool was called. Values are shown as the endpoint returned them. Method: https://radar.anlyon.com/methodology#remote-posture

| Fact | Observed |
| --- | --- |
| Reachable | `yes` |
| HTTP status of an anonymous initialize | `200` |
| tools/list served without credentials | `yes` |
| Tools that change things, listed without credentials | `0` |
| Protocol version | `2025-06-18` |
| WWW-Authenticate on 401 | `not observed` |
| resource_metadata in WWW-Authenticate | `none` |
| RFC 9728 protected resource metadata | `https://flights.flightpowers.com/.well-known/oauth-protected-resource/mcp` |
| Authorization servers | `https://flights.flightpowers.com` |
| Legacy HTTP+SSE transport | `no` |
| Dynamic client registration | `yes` |
| Client ID metadata documents | `yes` |
