Google Maps (Archived) vs Lilambd Data for Agents
Google Maps (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). Lilambd Data for Agents is an MCP server published by Veniwol-Li-Lambd. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 |  Google Maps (Archived) | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:d8652c8c9c52 Forks (GitHub): 11 930 Pulls (Docker Hub): 84 360 Stars (Docker Hub): 16 Stars (GitHub): 91 903 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.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
| Fact | Google Maps (Archived) | Lilambd Data for Agents |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 903 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 84 360 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 930 | No figure on GitHub |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | On your machine (mcp/google-maps) | Remote server (api.lilambd.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 | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-11-01 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 2 days ago returned HTTP 405 |
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)
Tools for interacting with the Google Maps API.
Lilambd Data for Agents
21 world data tools: airports, units, markets, security, travel meds, pet entry. x402 per call.
How to run each
Google Maps (Archived) As a local MCP server: Docker image
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-mapsRequires: GOOGLE_MAPS_API_KEY (secret)
Lilambd Data for Agents As a remote MCP server
claude mcp add --transport http lilambd-data https://api.lilambd.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Lilambd Data for Agents has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Lilambd Data for Agents publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Lilambd Data for Agents publish no settings it asks for, so we do not compare settings.
What it can do: Google Maps (Archived) · What it can do: Lilambd Data for Agents · 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.