DaedalMap Reverse Geocoding (coordinates to loc_id) vs AtlasFetch
DaedalMap Reverse Geocoding (coordinates to loc_id) is an MCP server published by daedalmap.com. Marketplaces we read that list it: 1 (Official MCP Registry). AtlasFetch is an MCP server published by atlasfetch.xyz. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-11. 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 |  DaedalMap Reverse Geocoding (coordinates to loc_id) |  AtlasFetch |
|---|---|---|
| Official MCP Registry | Listed Version: 1.4.2 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.4.4 Downloads/month (npm): 1 169 Downloads/week (npm): 148 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.4.4 Downloads/month (npm): 1 169 Downloads/week (npm): 148 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 | DaedalMap Reverse Geocoding (coordinates to loc_id) | AtlasFetch |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-31 |
| Where it runs (differs) | Remote server (app.daedalmap.com/mcp/reverse-geocoding) | On your machine (atlasfetch-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/xyver/daedal-map | github.com/atlasfetch-dev/atlasfetch-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 40 h ago returned HTTP 200 | no remote endpoint we check |
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
DaedalMap Reverse Geocoding (coordinates to loc_id)
Convert WGS84 coordinates to the latest available administrative loc_id chain.
AtlasFetch
Coordinates to places and streets, ZA addresses to points, and routes around your own geofences.
How to run each
DaedalMap Reverse Geocoding (coordinates to loc_id) As a remote MCP server
claude mcp add --transport http reverse-geocoding https://app.daedalmap.com/mcp/reverse-geocodingAtlasFetch As a local MCP server: npm package
claude mcp add --env "ATLASFETCH_API_KEY=<YOUR_ATLASFETCH_API_KEY>" --transport stdio atlasfetch -- npx -y atlasfetch-mcpRequires: ATLASFETCH_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only DaedalMap Reverse Geocoding (coordinates to loc_id) has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of DaedalMap Reverse Geocoding (coordinates to loc_id) publish no settings it asks for, so we do not compare settings.
What it can do: DaedalMap Reverse Geocoding (coordinates to loc_id) · What it can do: AtlasFetch · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.