Ext Ops Panel
Open dashboard
Comparison

Mapbox vs Zomato Restaurant Scraper - City, Cuisine, Contact

Mapbox is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). Zomato Restaurant Scraper - City, Cuisine, Contact is an MCP server published by AnshumanAtrey. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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
MarketplaceMapboxZomato Restaurant Scraper - City, Cuisine, Contact
Docker MCP Catalog Listed
Version: sha256:298701beaeed
Forks (GitHub): 44
Pulls (Docker Hub): 35 601
Stars (Docker Hub): 2
Stars (GitHub): 362
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Forks (GitHub): 0
Stars (GitHub): 0
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

Mapbox vs Zomato Restaurant Scraper - City, Cuisine, Contact
FactMapboxZomato Restaurant Scraper - City, Cuisine, Contact
Marketplaces that list it11
Stars (GitHub) (differs)362 (better)0 (worse)
Pulls (Docker Hub) (differs)35 601No figure on Docker Hub
Forks (GitHub) (differs)44 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/mapbox)Remote server (mcp.apify.com)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)28Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/mapbox/mcp-servergithub.com/anshumanatrey/zomato-restaurant-scraper
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 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

Mapbox

In its own words, on Docker MCP Catalog:

Transform any AI agent into a geospatially-aware system with Mapbox APIs. Provides geocoding, POI search, routing, travel time matrices, isochrones, and static map generation.

Zomato Restaurant Scraper - City, Cuisine, Contact

In its own words, on Official MCP Registry:

Zomato Restaurant Scraper - City, Cuisine, Contact

How to run each

Mapbox As a local MCP server: Docker image

Claude Code
claude mcp add --env "MAPBOX_ACCESS_TOKEN=<YOUR_MAPBOX_ACCESS_TOKEN>" --transport stdio mapbox -- docker run -i --rm -e MAPBOX_ACCESS_TOKEN mcp/mapbox

Requires: MAPBOX_ACCESS_TOKEN (secret)

Zomato Restaurant Scraper - City, Cuisine, Contact

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Requires: Authorization header

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

Only Zomato Restaurant Scraper - City, Cuisine, Contact has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Zomato Restaurant Scraper - City, Cuisine, Contact publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of Zomato Restaurant Scraper - City, Cuisine, Contact publish no settings it asks for, so we do not compare settings.

What it can do: Mapbox · What it can do: Zomato Restaurant Scraper - City, Cuisine, Contact · 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