Ext Ops Panel
Open dashboard
Comparison

Google Flights vs FareDice

Google Flights is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). FareDice is an MCP server published by faredice.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
MarketplaceGoogle FlightsFareDice
Docker MCP Catalog Listed
Version: sha256:8ecfd55f5aff
Forks (GitHub): 0
Pulls (Docker Hub): 28 175
Stars (Docker Hub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.0
No figure published
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

Google Flights vs FareDice
FactGoogle FlightsFareDice
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Pulls (Docker Hub) (differs)28 175No figure on Docker Hub
Forks (GitHub) (differs)0No figure on GitHub
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (mcp/google-flights)Remote server (faredice.com/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)3Not published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/kgprs/google-flights-mcp-serverNot stated
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

Google Flights

In its own words, on Docker MCP Catalog:

Interact with Google Flights data to search for one-way, round-trip, and date range flight options between airports.

FareDice

In its own words, on Official MCP Registry:

Cheap multi-country trips and non-stop fares by day in Europe and Southeast Asia

How to run each

Google Flights As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio google-flights -- docker run -i --rm mcp/google-flights

FareDice As a remote MCP server

Claude Code
claude mcp add --transport http trips https://faredice.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only FareDice has a remote endpoint we check. How we check endpoints

Tools each declares

Only Google Flights has

  • find_all_flights_in_range
  • get_flights_on_date
  • get_round_trip_flights

Only FareDice has

  • find_trips
  • nonstop_fares
  • nonstop_from

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (FareDice as of 2026-10-14). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: Google Flights · What it can do: FareDice · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built