Amazon Location Service vs Ziplore: US ZIP Code API (county, time zone, demographics, radius)
Amazon Location Service is an MCP server published by awslabs. Marketplaces we read that list it: 1 (Docker MCP Catalog). Ziplore: US ZIP Code API (county, time zone, demographics, radius) is an MCP server published by CyberMax-tools. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  Ziplore: US ZIP Code API (county, time zone, demographics, radius) |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:a84810ffd306 Forks (GitHub): 1 805 Pulls (Docker Hub): 13 400 Stars (Docker Hub): 0 Stars (GitHub): 9 773 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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 | Ziplore: US ZIP Code API (county, time zone, demographics, radius) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 773 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 13 400 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 1 805 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/aws-location-mcp-server) | Remote server (ziplore.cybermax-tools.workers.dev/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/cybermax-tools/product-factory |
| 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 | not checked yet |
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.
Ziplore: US ZIP Code API (county, time zone, demographics, radius)
Ziplore: US ZIP to county, FIPS, time zone, Census demographics; radius and city ZIPs. Free, no key.
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)
Ziplore: US ZIP Code API (county, time zone, demographics, radius)
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Ziplore: US ZIP Code API (county, time zone, demographics, radius) publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Ziplore: US ZIP Code API (county, time zone, demographics, radius) publish no settings it asks for, so we do not compare settings.
What it can do: Amazon Location Service · What it can do: Ziplore: US ZIP Code API (county, time zone, demographics, radius) · 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.