Amazon Location Service vs Transport Nsw
Amazon Location Service is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Transport Nsw is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  Transport Nsw |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a84810ffd306 Forks (GitHub): 1 855 Pulls (Docker Hub): 14 128 Stars (Docker Hub): 0 Stars (GitHub): 9 889 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 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 | Transport Nsw |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 889 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 14 128 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 855 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-11-05 |
| Where it runs (differs) | On your machine (mcp/aws-location-mcp-server) | Remote server (gateway.pipeworx.io/transport-nsw/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 8 | Not published |
| Environment variables it asks for (differs) | 5, secrets among them: 2 | 1, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/mcp | github.com/pipeworx-io/mcp-transport-nsw |
| Changes in the last 7 days (differs) | 0 | 1 |
| 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 41 h ago returned HTTP 200 |
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.
Transport Nsw
Transport for NSW MCP — journey planning, live departures, service alerts and commuter car-park…
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)
Transport Nsw As a remote MCP server
claude mcp add --transport http transport-nsw https://gateway.pipeworx.io/transport-nsw/mcpRequires: PIPEWORX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Transport Nsw has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Transport Nsw publish no list of tools, so we do not compare tools.
Settings each asks for
Only Amazon Location Service asks for
AWS_ACCESS_KEY_IDAWS_PROFILEAWS_REGIONAWS_SECRET_ACCESS_KEY (secret)AWS_SESSION_TOKEN (secret)
Only Transport Nsw asks for
PIPEWORX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Amazon Location Service · What it can do: Transport Nsw · 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.