Ext Ops Panel
Open dashboard
Comparison

Mapbox vs ParseAddr — Address Parsing & Normalization

Mapbox is an MCP server published by mapbox. Marketplaces we read that list it: 1 (Docker MCP Catalog). ParseAddr — Address Parsing & Normalization is an MCP server published by parseaddr.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

Where each is published
MarketplaceMapboxParseAddr — Address Parsing & Normalization
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: 0.1.0
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 ParseAddr — Address Parsing & Normalization
FactMapboxParseAddr — Address Parsing & Normalization
Marketplaces that list it11
Stars (GitHub) (differs)361 (better)0 (worse)
Pulls (Docker Hub) (differs)35 390No 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 (api.parseaddr.com/mcp)
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/wezpyke/parseaddr-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-12
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

ParseAddr — Address Parsing & Normalization

In its own words, on Official MCP Registry:

Hosted libpostal: messy free-text postal addresses → structured fields. No 2-4GB self-host.

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)

ParseAddr — Address Parsing & Normalization As a remote MCP server

Claude Code
claude mcp add --transport http address-parse https://api.parseaddr.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Tools each declares

The marketplaces of ParseAddr — Address Parsing & Normalization publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of ParseAddr — Address Parsing & Normalization publish no settings it asks for, so we do not compare settings.

What it can do: Mapbox · What it can do: ParseAddr — Address Parsing & Normalization · 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