Ext Ops Panel
Open dashboard
Comparison

Google Maps Comprehensive vs io.github.fouomene/mcp-server-geodata-placefinder

Google Maps Comprehensive is an MCP server published by vicpeacock. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.fouomene/mcp-server-geodata-placefinder is an MCP server published by fouomene. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
MarketplaceGoogle Maps Comprehensiveio.github.fouomene/mcp-server-geodata-placefinder
Docker MCP Catalog Listed
Version: sha256:fc37a12a21f4
Forks (GitHub): 1
Pulls (Docker Hub): 39 177
Stars (Docker Hub): 0
Stars (GitHub): 6
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.0
Downloads/month (npm): 136
Downloads/week (npm): 58
Forks (GitHub): 0
Stars (GitHub): 1
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

Google Maps Comprehensive vs io.github.fouomene/mcp-server-geodata-placefinder
FactGoogle Maps Comprehensiveio.github.fouomene/mcp-server-geodata-placefinder
Marketplaces that list it11
Stars (GitHub) (differs)6 (better)1 (worse)
Pulls (Docker Hub) (differs)39 177No figure on Docker Hub
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/google-maps-comprehensive)On your machine (mcp-server-geodata-placefinder)
Transportstdiostdio
Tools it declares (differs)8Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/vicpeacock/google-maps-comprehensive-mcpgithub.com/fouomene/geodataplacefinder
Changes in the last 7 days00
First seen2026-10-112026-10-11

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 Comprehensive

In its own words, on Docker MCP Catalog:

Complete Google Maps integration with 8 tools including geocoding, places search, directions, elevation data, and more using Google's latest APIs.

io.github.fouomene/mcp-server-geodata-placefinder

In its own words, on Official MCP Registry:

MCP GeoData Placefinder: search places, reverse geocode, and find nearby locations.

How to run each

Google Maps Comprehensive 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-comprehensive -- docker run -i --rm -e GOOGLE_MAPS_API_KEY mcp/google-maps-comprehensive

Requires: GOOGLE_MAPS_API_KEY (secret)

io.github.fouomene/mcp-server-geodata-placefinder As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio mcp-server-geodata-placefinder -- npx -y mcp-server-geodata-placefinder

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

Tools each declares

The marketplaces of io.github.fouomene/mcp-server-geodata-placefinder publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.fouomene/mcp-server-geodata-placefinder publish no settings it asks for, so we do not compare settings.

What it can do: Google Maps Comprehensive · What it can do: io.github.fouomene/mcp-server-geodata-placefinder · 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.

Where the data comes from: how the catalog is built