Amazon Location Service vs TripWays
Amazon Location Service is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). TripWays is an MCP server published by tripways.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  TripWays |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a84810ffd306 Forks (GitHub): 1 857 Pulls (Docker Hub): 14 162 Stars (Docker Hub): 0 Stars (GitHub): 9 892 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.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 | TripWays |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 892 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 14 162 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 857 | No figure on GitHub |
| Last release (differs) | Not published | 2026-10-29 |
| Where it runs (differs) | On your machine (mcp/aws-location-mcp-server) | Remote server (mcp.tripways.com/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 | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded less than an hour 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.
TripWays
Find, price, and book tours, day trips, and activities worldwide, with live dates and prices.
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)
TripWays As a remote MCP server
claude mcp add --transport http tours https://mcp.tripways.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only TripWays has a remote endpoint we check. How we check endpoints
Tools each declares
Only Amazon Location Service has
calculate_routegeocodeget_placeoptimize_waypointsreverse_geocodesearch_nearbysearch_placessearch_places_open_now
Only TripWays has
check_availabilitycompare_toursfind_alternativesget_booking_linkget_cancellation_policyget_destination_infoget_itinerary_ideasget_meeting_pointget_price_quoteget_tour_detailsget_tour_reviewssearch_tours
Both have
None
Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (TripWays as of 2026-10-17). More tools is not better in itself: compare what each needs for the job.
Settings each asks for
The marketplaces of TripWays publish no settings it asks for, so we do not compare settings.
What it can do: Amazon Location Service · What it can do: TripWays · 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.