Ext Ops Panel
Open dashboard
Comparison

Google Maps (Archived) vs Latino Events (events.lat)

Google Maps (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Latino Events (events.lat) is an MCP server published by events.lat. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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 (Archived)Latino Events (events.lat)
Docker MCP Catalog Listed
Version: sha256:d8652c8c9c52
Forks (GitHub): 11 874
Pulls (Docker Hub): 84 089
Stars (Docker Hub): 16
Stars (GitHub): 91 633
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
No figure published
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 (Archived) vs Latino Events (events.lat)
FactGoogle Maps (Archived)Latino Events (events.lat)
Marketplaces that list it11
Stars (GitHub) (differs)91 633No figure on GitHub
Pulls (Docker Hub) (differs)84 089No figure on Docker Hub
Forks (GitHub) (differs)11 874No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/google-maps)Remote server (ojlsoqhibryhvuyltwpi.supabase.co/functions/v1/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)7Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 days ago, requires a key

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.

Latino Events (events.lat)

In its own words, on Official MCP Registry:

Find upcoming concerts, festivals and cultural events across Latin America.

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)

Latino Events (events.lat) As a remote MCP server

Claude Code
claude mcp add --transport http latino-events https://ojlsoqhibryhvuyltwpi.supabase.co/functions/v1/mcp

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

Only Latino Events (events.lat) has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Latino Events (events.lat) publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Latino Events (events.lat) publish no settings it asks for, so we do not compare settings.

What it can do: Google Maps (Archived) · What it can do: Latino Events (events.lat) · 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