amazon-location-service vs DaedalMap Geography Tools (loc_id)
amazon-location-service is a plugin bundle for AI coding tools published by awslabs. Marketplaces we read that list it: 3 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community, Community GitHub marketplaces). DaedalMap Geography Tools (loc_id) is an MCP server published by daedalmap.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  amazon-location-service |  DaedalMap Geography Tools (loc_id) |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 1.1.0 Forks (GitHub): 162 Stars (GitHub): 918 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 1.0.0 Forks (GitHub): 162 Stars (GitHub): 918 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.6.2 Forks (GitHub): 0 Stars (GitHub): 2 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 | DaedalMap Geography Tools (loc_id) |
|---|---|---|
| Marketplaces that list it (differs) | 3 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 918 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 162 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-proxy-for-aws) | Remote server (app.daedalmap.com/mcp/geography) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/awslabs/agent-plugins | github.com/xyver/daedal-map |
| 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
Guide developers through adding maps, places search, geocoding, routing, and other geospatial features with Amazon Location Service, including authentication setup, SDK integration, and best practices.
DaedalMap Geography Tools (loc_id)
Resolve coordinates and geographic identifiers to loc_id, crosswalks, and bounded shapes.
How to run each
amazon-location-service As a Claude Code plugin
/plugin install amazon-location-service@claude-plugins-officialDaedalMap Geography Tools (loc_id) As a remote MCP server
claude mcp add --transport http geocoding https://app.daedalmap.com/mcp/geographyCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: amazon-location-service · What it can do: DaedalMap Geography Tools (loc_id) · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. 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.