Google Flights vs com.fostay/hotels
Google Flights is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.fostay/hotels is an MCP server published by fostay.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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
| Marketplace |   Google Flights |  com.fostay/hotels |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:8ecfd55f5aff Forks (GitHub): 0 Pulls (Docker Hub): 29 925 Stars (Docker Hub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 2.2.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
| Fact | Google Flights | com.fostay/hotels |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 29 925 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | On your machine (mcp/google-flights) | Remote server (fostay.com/api/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 3 | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/kgprs/google-flights-mcp-server | Not stated |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 43 h ago returned HTTP 405 |
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
Interact with Google Flights data to search for one-way, round-trip, and date range flight options between airports.
com.fostay/hotels
Hotel search, live prices and rate holds in 9 cities incl. Dubai, Sydney, Madrid; pay on fostay.com
How to run each
Google Flights As a local MCP server: Docker image
claude mcp add --transport stdio google-flights -- docker run -i --rm mcp/google-flightscom.fostay/hotels As a remote MCP server
claude mcp add --transport http hotels https://fostay.com/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only com.fostay/hotels has a remote endpoint we check. How we check endpoints
Tools each declares
Only Google Flights has
find_all_flights_in_rangeget_flights_on_dateget_round_trip_flights
Only com.fostay/hotels has
booking_statusdemand_calendarget_live_ratesprepare_bookingsearch_stayswhen_to_go
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (com.fostay/hotels as of 2026-10-13). 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: com.fostay/hotels · 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.