Ext Ops Panel
Open dashboard
Comparison

DaedalMap Reverse Geocoding (coordinates to loc_id) vs GeoLabel

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). GeoLabel is an MCP server published by TylerCoxDruin. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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

Where each is published
MarketplaceDaedalMap Reverse Geocoding (coordinates to loc_id)GeoLabel
Official MCP Registry Listed
Version: 1.4.2
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (PyPI): 91
Downloads/week (PyPI): 22
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

DaedalMap Reverse Geocoding (coordinates to loc_id) vs GeoLabel
FactDaedalMap Reverse Geocoding (coordinates to loc_id)GeoLabel
Marketplaces that list it11
Stars (GitHub) (differs)2No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (app.daedalmap.com/mcp/reverse-geocoding)On your machine (geolabel-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/xyver/daedal-mapgithub.com/tylercoxdruin/geolabel
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 4 days agono 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)

In its own words, on Official MCP Registry:

Convert WGS84 coordinates to the latest available administrative loc_id chain.

GeoLabel

In its own words, on Official MCP Registry:

Turn GPS coordinates into place name, category, and live opening hours via OpenStreetMap.

How to run each

DaedalMap Reverse Geocoding (coordinates to loc_id) As a remote MCP server

Claude Code
claude mcp add --transport http reverse-geocoding https://app.daedalmap.com/mcp/reverse-geocoding

GeoLabel As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GEOLABEL_API_KEY=<YOUR_GEOLABEL_API_KEY>" --transport stdio geolabel -- uvx geolabel-mcp

Requires: GEOLABEL_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: GeoLabel · Compare two other plugins

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.

Where the data comes from: how the catalog is built