Comparison

Google Maps (Archived) vs unesco-heritage-mcp-server

Google Maps (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). unesco-heritage-mcp-server is an MCP server published by cyanheads. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplace	Google Maps (Archived)	unesco-heritage-mcp-server
Docker MCP Catalog	Listed Version: sha256:d8652c8c9c52 Forks (GitHub): 11 868 Pulls (Docker Hub): 84 000 Stars (Docker Hub): 16 Stars (GitHub): 91 555 Not marked · First seen 2026-10-11	Not listed
Official MCP Registry	Not listed	Listed Version: 0.2.1 Downloads/month (npm): 740 Downloads/week (npm): 263 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen 2026-10-11

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

Google Maps (Archived) vs unesco-heritage-mcp-server
Fact	Google Maps (Archived)	unesco-heritage-mcp-server
Marketplaces that list it	1	1
Stars (GitHub) (differs)	91 555 (better)	2 (worse)
Pulls (Docker Hub) (differs)	84 000	No figure on Docker Hub
Forks (GitHub) (differs)	11 868 (better)	0 (worse)
Last release (differs)	Not published	2026-10-18
Where it runs (differs)	On your machine (mcp/google-maps)	Remote server (unesco-heritage.caseyjhand.com/mcp)
Transport (differs)	stdio	Streamable HTTP
Tools it declares (differs)	7	Not published
Environment variables it asks for (differs)	1, secrets among them: 1	6, secrets among them: 0
Licence (differs)	NOASSERTION	Not stated
Repository (differs)	github.com/modelcontextprotocol/servers	github.com/cyanheads/unesco-heritage-mcp-server
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 4 days 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

Google Maps (Archived)

In its own words, on Docker MCP Catalog:

Tools for interacting with the Google Maps API.

unesco-heritage-mcp-server

In its own words, on Official MCP Registry:

Search UNESCO World Heritage sites, intangible heritage, biosphere reserves, and Global Geoparks.

How to run each

Google Maps (Archived) As a local MCP server: Docker image

Claude Code

claude mcp add --env "GOOGLE_MAPS_API_KEY=<YOUR_GOOGLE_MAPS_API_KEY>" --transport stdio google-maps -- docker run -i --rm -e GOOGLE_MAPS_API_KEY mcp/google-maps

Requires: GOOGLE_MAPS_API_KEY (secret)

unesco-heritage-mcp-server As a remote MCP server

Claude Code

claude mcp add --transport http unesco-heritage-mcp-server https://unesco-heritage.caseyjhand.com/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only unesco-heritage-mcp-server has a remote endpoint we check. How we check endpoints

Tools each declares

Only Google Maps (Archived) has

maps_directions
maps_distance_matrix
maps_elevation
maps_geocode
maps_place_details
maps_reverse_geocode
maps_search_places

Only unesco-heritage-mcp-server has

unesco_get_biosphere_reserve
unesco_get_geopark
unesco_get_intangible_heritage_element
unesco_get_site
unesco_list_reference
unesco_search_biosphere_reserves
unesco_search_geoparks
unesco_search_intangible_heritage
unesco_search_sites

Both have

None

Tool names as the marketplaces declare them and as Ext Ops observed them on the endpoints (unesco-heritage-mcp-server as of 2026-10-21). More tools is not better in itself: compare what each needs for the job.

Settings each asks for

Only Google Maps (Archived) asks for

GOOGLE_MAPS_API_KEY (secret)

Only unesco-heritage-mcp-server asks for

MCP_AUTH_MODE
MCP_HTTP_ENDPOINT_PATH
MCP_HTTP_HOST
MCP_HTTP_PORT
MCP_LOG_LEVEL
MCP_TRANSPORT_TYPE

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Google Maps (Archived) · What it can do: unesco-heritage-mcp-server · 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 2026-10-26. We publish no contact details for plugin publishers.