Ext Ops Panel
Open dashboard
Comparison

Google Flights vs nexusfeed-ltl-fuel-surcharges

Google Flights is an MCP server published by kgprs. Marketplaces we read that list it: 1 (Docker MCP Catalog). nexusfeed-ltl-fuel-surcharges is a plugin bundle for AI coding tools published by NexusFeed. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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 Flightsnexusfeed-ltl-fuel-surcharges
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
Claude Code: claude-plugins-community Not listed Listed
Version: 5fe1895
Forks (GitHub): 0
Stars (GitHub): 1
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 nexusfeed-ltl-fuel-surcharges
FactGoogle Flightsnexusfeed-ltl-fuel-surcharges
Marketplaces that list it11
Stars (GitHub)11
Pulls (Docker Hub) (differs)28 175No figure on Docker Hub
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/google-flights)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)3Not published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)Not a bundle2
Licence (differs)MITNot stated
Repository (differs)github.com/kgprs/google-flights-mcp-servergithub.com/nexusfeed/nexusfeed-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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.

nexusfeed-ltl-fuel-surcharges

In its own words, on Claude Code: claude-plugins-community:

Real-time LTL freight carrier fuel surcharge rates for AI agents. Covers 11 carriers (ODFL, Saia, Estes, ABF, R+L, TForce, XPO, SEFL, Averitt, FedEx, UPS). Every response includes a _verifiability block with extraction confidence, source timestamp, and evidence URL. Installed via uvx, authenticated with MCP_API_KEY env var.

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

nexusfeed-ltl-fuel-surcharges As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install nexusfeed-ltl-fuel-surcharges@claude-community

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

Tools each declares

The marketplaces of nexusfeed-ltl-fuel-surcharges publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Google Flights publish no settings it asks for, so we do not compare settings.

What it can do: Google Flights · What it can do: nexusfeed-ltl-fuel-surcharges · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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