# Google Flights MCP (remote · mcp.wondel.ai)

Live Google Flights fares: search routes, discover cheap deals from an origin.

- Trust score: 56/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.wondel.ai`: 56/100 (this document), [markdown](https://verifymcp.io/servers/ai-wondel-google-flights/google-flights-mcp.md), [page](https://verifymcp.io/servers/ai-wondel-google-flights/google-flights-mcp)

## Channel facts

- Endpoint: `https://mcp.wondel.ai/google-flights/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 43/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2823 tokens (~1411/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Google Flights MCP server?

Google Flights MCP is a hosted endpoint at https://mcp.wondel.ai/google-flights/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http ai-wondel-google-flights 'https://mcp.wondel.ai/google-flights/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "ai-wondel-google-flights": {
      "url": "https://mcp.wondel.ai/google-flights/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ai-wondel-google-flights": {
      "type": "http",
      "url": "https://mcp.wondel.ai/google-flights/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.ai-wondel-google-flights]
url = "https://mcp.wondel.ai/google-flights/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-wondel-google-flights": {
      "type": "remote",
      "url": "https://mcp.wondel.ai/google-flights/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-wondel-google-flights --url 'https://mcp.wondel.ai/google-flights/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-wondel-google-flights:
    url: "https://mcp.wondel.ai/google-flights/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "ai-wondel-google-flights": {
      "Transport": "http",
      "Url": "https://mcp.wondel.ai/google-flights/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add ai-wondel-google-flights -t streamable-http -u 'https://mcp.wondel.ai/google-flights/mcp'
```

### Other

```json
{
  "mcpServers": {
    "ai-wondel-google-flights": {
      "type": "http",
      "url": "https://mcp.wondel.ai/google-flights/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 56, +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.

### 2026-11-03 (score 55, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 54)

First indexed and scored.

## MCP tools (2)

### `google_flights_search` (~1751 tokens)

Search Google Flights (SerpAPI)

Search Google Flights live via SerpAPI. Returns best_flights and other_flights (each with legs, airlines, times, duration, layovers, price and carbon emissions), plus price_insights and airport info. Supports round trip (type=1, needs return_date), one way (type=2) and multi-city (type=3 via multi_city_json). Two-step flows: pass a departure_token from a prior result to get the returning flights / next leg, or a booking_token to get booking options — re-send the original search params alongside either token. Prices are in `currency` (default USD). IDs are AIRPORT codes, never city/metro codes: TYO, NYC, LON, PAR, MIL, ROM, OSA, CHI, WAS return NO results (live-verified) — send the airports instead (TYO → 'HND,NRT'; NYC → 'JFK,EWR,LGA'; LON → 'LHR,LGW,STN,LTN'; PAR → 'CDG,ORY'; MIL → 'MXP,LIN,BGY'; ROM → 'FCO,CIA') or the city's Google kgmid (e.g. '/m/07dfk' for Tokyo). Result shape: { note?, source, fetchedAt, query, search_metadata: { google_flights_url }, search_parameters, best_flights: [...], other_flights: [...], price_insights, airports } — the two itinerary lists are `best_flights` and `other_flights` (there is no `flights` or `deals` key at the top level, and an itinerary is never a bare flight). Each itinerary: { flights: [{ departure_airport: { name, id, time }, arrival_airport: { name, id, time }, duration, airplane, airline, airline_logo, travel_class, flight_number, legroom, extensions }], layovers: [{ duration, name, id, overnight }], total_duration, carbon_emissions, price, type, airline_logo, departure_token, booking_token } — `price` is the whole-itinerary price in `currency`, `duration`/`total_duration` are minutes, and the per-leg times are local 'YYYY-MM-DD HH:MM' strings. Feed `departure_token` back for the return leg and `booking_token` for booking options. A top-level `note` appears only when stops=1 found no nonstop flight and the server retried without the stop filter: the itineraries are then connecting flights, and their tokens need the s…

Input parameters:

- `adults` (integer): Number of adults. Default 1.
- `arrival_id` (string): Arrival AIRPORT IATA code(s) (e.g. 'HND,NRT') or a Google location kgmid (e.g. '/m/07dfk' for Tokyo). Comma-separate multiple. NOT a city/metro code — TYO, LON, PAR, MIL, ROM, OSA return no results;…
- `bags` (integer): Number of carry-on bags. Default 0.
- `booking_token` (string): Token from a prior result, used to fetch booking options for a selected itinerary. Re-send the same search params alongside it. Mutually exclusive with departure_token.
- `children` (integer): Number of children. Default 0.
- `currency` (string): Currency of returned prices (ISO code, e.g. 'USD', 'EUR'). Default USD.
- `deep_search` (boolean): Run a deeper search that matches the Google Flights browser results more closely (slower). Default false.
- `departure_id` (string): Departure AIRPORT IATA code(s) (3-letter, uppercase, e.g. 'WAW' or 'WAW,WMI') or a Google location kgmid (/m/… or /g/…). Comma-separate multiple. NOT a city/metro code — TYO, NYC, LON, PAR, MIL, ROM…
- `departure_token` (string): Token from a prior result, used to select an outbound flight and fetch the returning flights (round trip) or the next leg (multi-city). Re-send the same search params alongside it. Mutually exclusive…
- `emissions` (integer): Emissions filter: 1 = less emissions only. Omit for no filter.
- `exclude_airlines` (string): Exclude these airlines: comma-separated 2-letter IATA codes, or an alliance (STAR_ALLIANCE, SKYTEAM, ONEWORLD). Mutually exclusive with include_airlines.
- `exclude_basic` (boolean): Exclude basic-economy fares. Only for domestic US flights with travel_class=1. Default false.
- `exclude_conns` (string): Connecting airports to exclude: comma-separated 3-letter IATA codes (e.g. 'CDG,LHR').
- `gl` (string): Country code for the search, e.g. 'us', 'uk', 'de'.
- `hl` (string): Language code, e.g. 'en', 'es', 'fr'.
- `include_airlines` (string): Only these airlines: comma-separated 2-letter IATA codes, or an alliance: STAR_ALLIANCE, SKYTEAM, ONEWORLD. Mutually exclusive with exclude_airlines.
- `infants_in_seat` (integer): Number of infants in seat. Default 0.
- `infants_on_lap` (integer): Number of infants on lap. Default 0.
- `layover_duration` (string): Layover duration range in minutes, 'min,max' (e.g. '90,330' for 1.5-5.5h).
- `max_duration` (integer): Maximum total trip duration in minutes (e.g. 1500 for 25h).
- `max_price` (integer): Maximum ticket price in the selected currency.
- `multi_city_json` (string): Multi-city itinerary (required when type=3): a JSON-string array of legs, e.g. '[{"departure_id":"CDG","arrival_id":"NRT","date":"2026-06-27"},{"departure_id":"NRT","arrival_id":"LAX","date":"2026-07…
- `no_cache` (boolean): Force a fresh SerpAPI fetch and bypass this server's result cache. Default false.
- `outbound_date` (string): Outbound date, YYYY-MM-DD.
- `outbound_times` (string): Outbound time window as comma-separated hours (0-23). 2 values = departure range 'min,max' (e.g. '4,18'); 4 values add an arrival range (e.g. '4,18,3,19').
- `return_date` (string): Return date, YYYY-MM-DD. Required when type=1 (round trip).
- `return_times` (string): Return time window, same format as outbound_times. Only valid when type=1.
- `show_hidden` (boolean): Include hidden flight results. Default false.
- `sort_by` (integer): Sort order: 1 = top flights (default), 2 = price, 3 = departure time, 4 = arrival time, 5 = duration, 6 = emissions.
- `stops` (integer): Max stops: 0 = any (default), 1 = nonstop only, 2 = 1 stop or fewer, 3 = 2 stops or fewer. When stops=1 finds no nonstop flight, the server automatically retries without the filter and returns connec…
- `travel_class` (integer): Travel class: 1 = economy (default), 2 = premium economy, 3 = business, 4 = first.
- `type` (integer): Trip type: 1 = round trip (default), 2 = one way, 3 = multi-city.
- `zero_trace` (boolean): Enterprise-only ZeroTrace mode: don't store search params/metadata on SerpAPI. Default false.

Output parameters:

- `airports`
- `best_flights` (array)
- `fetchedAt` (string)
- `note`: Present only when stops=1 found no nonstop flight and best_flights/other_flights are connecting flights from a search without the stop filter. Tell the user that no direct flights were found, so conn…
- `other_flights` (array)
- `price_insights`
- `query` (object)
- `search_metadata` (object)
- `search_parameters`
- `source` (string)

### `google_flights_deals_search` (~968 tokens)

Search Google Flights Deals (SerpAPI)

Discover cheap flight destinations from an origin via SerpAPI's Google Flights Deals engine (google_flights_deals). Unlike google_flights_search there is no arrival_id — the engine explores destinations for you — and there are no pagination or navigation tokens. Dates accept a single YYYY-MM-DD or a 'start,end' range (e.g. '2026-06-27,2026-07-03') to widen the window. Supports round trip (type=1, needs return_date) and one way (type=2). Prices are in `currency` (default USD). Result shape: { source, fetchedAt, query, search_metadata, search_parameters, departure_informations, deals: [...] } — the list key is `deals` (there are no best_flights/other_flights here). Each deal: { destination_id, name, country, price, average_price, discount_percentage, flight_link, serpapi_flight_link, thumbnail, outbound_date, return_date, departure_airport_code, arrival_airport_code, flight_duration, stops, airline, airline_code, description, highlights }. The dates are `outbound_date` / `return_date` (YYYY-MM-DD) — the live engine returns those, not the `start_date`/`end_date` of SerpAPI's docs — and a deal carries NO departure or return time.

Input parameters:

- `adults` (integer): Number of adults. Default 1.
- `children` (integer): Number of children. Default 0.
- `currency` (string): Currency of returned prices (ISO code, e.g. 'USD', 'EUR'). Default USD.
- `departure_id` (string): Departure AIRPORT IATA code(s) (3-letter, uppercase, e.g. 'WAW' or 'WAW,WMI') or a Google location kgmid (/m/… or /g/…). Comma-separate multiple. NOT a city/metro code (NYC, LON, PAR return no result…
- `exclude_airlines` (string): Exclude these airlines: comma-separated 2-letter IATA codes, or an alliance (STAR_ALLIANCE, SKYTEAM, ONEWORLD). Mutually exclusive with include_airlines.
- `gl` (string): Country code for the search, e.g. 'us', 'uk', 'de'.
- `hl` (string): Language code, e.g. 'en', 'es', 'fr'.
- `include_airlines` (string): Only these airlines: comma-separated 2-letter IATA codes, or an alliance: STAR_ALLIANCE, SKYTEAM, ONEWORLD. Mutually exclusive with exclude_airlines.
- `infants_in_seat` (integer): Number of infants in seat. Default 0.
- `infants_on_lap` (integer): Number of infants on lap. Default 0.
- `max_duration` (integer): Maximum total trip duration in minutes (e.g. 1500 for 25h).
- `max_price` (integer): Maximum ticket price in the selected currency.
- `no_cache` (boolean): Force a fresh SerpAPI fetch and bypass this server's result cache. Default false.
- `outbound_date` (string): Outbound date as a single YYYY-MM-DD, or a 'start,end' range (e.g. '2026-06-27,2026-07-03') to search a window.
- `return_date` (string): Return date as a single YYYY-MM-DD, or a 'start,end' range. Required when type=1 (round trip). When outbound_date is a range it must be a 'start,end' range too (or drop it and use trip_length/travel_…
- `stops` (integer): Max stops: 0 = any (default), 1 = nonstop only, 2 = 1 stop or fewer, 3 = 2 stops or fewer.
- `travel_class` (integer): Travel class: 1 = economy (default), 2 = premium economy, 3 = business, 4 = first.
- `travel_duration` (integer): Travel duration preset: 1 = one week, 2 = weekend, 3 = two weeks.
- `trip_length`: Trip length in days: a single number, or a 'min,max' day range (e.g. '3,5').
- `type` (integer): Trip type: 1 = round trip (default, needs return_date), 2 = one way.
- `zero_trace` (boolean): Enterprise-only ZeroTrace mode: don't store search params/metadata on SerpAPI. Default false.

Output parameters:

- `deals` (array)
- `departure_informations`
- `fetchedAt` (string)
- `query` (object)
- `search_metadata`
- `search_parameters`
- `source` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-wondel-google-flights/google-flights-mcp#diagnostics

## Score history

- 2026-11-05: 56
- 2026-11-04: 55
- 2026-11-03: 55
- 2026-11-02: 54

## Common questions

### What is the Google Flights MCP server?

Google Flights MCP is listed in the public MCP registry as ai.wondel/google-flights. Live Google Flights fares: search routes, discover cheap deals from an origin. This page covers its hosted endpoint (https://mcp.wondel.ai/google-flights/mcp).

### Is the Google Flights MCP server safe to use?

Google Flights MCP scores 56 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Google Flights MCP server expose?

Google Flights MCP exposes 2 tools: google_flights_search, google_flights_deals_search. Their descriptions and schemas cost roughly 2,719 tokens of context every time the server is loaded.

### Does the Google Flights MCP server require authentication?

No. We connected to Google Flights MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Google Flights MCP server still maintained?

Google Flights MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.wondel.ai/google-flights/mcp
- Website: https://mcps.wondel.ai/servers/google-flights/
- Changelog RSS feed: https://verifymcp.io/servers/ai-wondel-google-flights/google-flights-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-wondel-google-flights/google-flights-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ai-wondel-google-flights/google-flights-mcp