Mapbox vs DaedalMap Disaster and Geospatial Data
Mapbox is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). DaedalMap Disaster and Geospatial Data is an MCP server published by daedalmap.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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 |  Mapbox |  DaedalMap Disaster and Geospatial Data |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:298701beaeed Forks (GitHub): 44 Pulls (Docker Hub): 35 390 Stars (Docker Hub): 2 Stars (GitHub): 361 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 2 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 | Mapbox | DaedalMap Disaster and Geospatial Data |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 361 (better) | 2 (worse) |
| Pulls (Docker Hub) (differs) | 35 390 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 44 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/mapbox) | Remote server (app.daedalmap.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 28 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/mapbox/mcp-server | github.com/xyver/daedal-map |
| 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 27 h 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
Mapbox
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.
DaedalMap Disaster and Geospatial Data
Geospatial MCP server for earthquake, tsunami, volcano, disaster, and FX data queries.
How to run each
Mapbox As a local MCP server: Docker image
claude mcp add --env "MAPBOX_ACCESS_TOKEN=<YOUR_MAPBOX_ACCESS_TOKEN>" --transport stdio mapbox -- docker run -i --rm -e MAPBOX_ACCESS_TOKEN mcp/mapboxRequires: MAPBOX_ACCESS_TOKEN (secret)
DaedalMap Disaster and Geospatial Data As a remote MCP server
claude mcp add --transport http county-map https://app.daedalmap.com/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only DaedalMap Disaster and Geospatial Data has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of DaedalMap Disaster and Geospatial Data publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of DaedalMap Disaster and Geospatial Data publish no settings it asks for, so we do not compare settings.
What it can do: Mapbox · What it can do: DaedalMap Disaster and Geospatial Data · 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.