Amazon Location Service vs Airport Weather & Delays (METAR, TAF, FAA)
Amazon Location Service is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Airport Weather & Delays (METAR, TAF, FAA) is an MCP server published by pcp183. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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 |  Amazon Location Service | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a84810ffd306 Forks (GitHub): 1 823 Pulls (Docker Hub): 13 624 Stars (Docker Hub): 0 Stars (GitHub): 9 812 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.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 | Amazon Location Service | Airport Weather & Delays (METAR, TAF, FAA) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 812 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 13 624 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 823 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-17 |
| Where it runs (differs) | On your machine (mcp/aws-location-mcp-server) | Remote server (airport-weather-production.up.railway.app/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | Not published |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/pcp183/airport-weather |
| Changes in the last 7 days (differs) | 0 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-16 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (19 h 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
Amazon Location Service
Place search, geocoding, and route optimization.
Airport Weather & Delays (METAR, TAF, FAA)
Airport METAR/TAF weather and FAA delays by airport code. $0.003/call via x402.
How to run each
Amazon Location Service As a local MCP server: Docker image
claude mcp add --env "AWS_SECRET_ACCESS_KEY=<YOUR_AWS_SECRET_ACCESS_KEY>" --env "AWS_SESSION_TOKEN=<YOUR_AWS_SESSION_TOKEN>" --transport stdio aws-location -- docker run -i --rm -e AWS_SECRET_ACCESS_KEY -e AWS_SESSION_TOKEN mcp/aws-location-mcp-serverRequires: AWS_SECRET_ACCESS_KEY (secret), AWS_SESSION_TOKEN (secret)
Airport Weather & Delays (METAR, TAF, FAA) As a remote MCP server
claude mcp add --transport http airport-weather https://airport-weather-production.up.railway.app/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Airport Weather & Delays (METAR, TAF, FAA) has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Airport Weather & Delays (METAR, TAF, FAA) publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Airport Weather & Delays (METAR, TAF, FAA) publish no settings it asks for, so we do not compare settings.
What it can do: Amazon Location Service · What it can do: Airport Weather & Delays (METAR, TAF, FAA) · 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.