# Mapbox (npm · @pipeworx/mcp-mapbox)

Mapbox MCP.

- Trust score: 79/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-mapbox/mapbox-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-mapbox/mapbox-mcp)
- npm · `@pipeworx/mcp-mapbox`: 79/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-mapbox/pipeworx-mcp-mapbox.md), [page](https://verifymcp.io/servers/pipeworx-io-mapbox/pipeworx-mcp-mapbox)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-mapbox`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-mapbox).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1221 tokens (~152/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 2% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Mapbox MCP server?

Mapbox runs locally as an npm package, launched with npx -y @pipeworx/mcp-mapbox. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-mapbox -- npx -y @pipeworx/mcp-mapbox
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-mapbox": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-mapbox"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-mapbox": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-mapbox"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-mapbox -- npx -y @pipeworx/mcp-mapbox
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-mapbox": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-mapbox"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-mapbox --command npx --arg -y --arg @pipeworx/mcp-mapbox
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-mapbox:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-mapbox"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-mapbox": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-mapbox"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-mapbox -t stdio -c npx -a -y @pipeworx/mcp-mapbox
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-mapbox": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-mapbox"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 78, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 62, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 75)

First indexed and scored.

## MCP tools (8)

### `geocode_forward` (~168 tokens)

"What are the coordinates of [address]" / "geocode [place]" / "lat lng for [location]" / "find [city] on a map" — convert a street address, city, or place name to GPS coordinates (longitude / latitude) using Mapbox's global geocoder. Works on any street, intersection, POI, or administrative area worldwide. Example: geocode_forward({ query: "1600 Pennsylvania Ave, Washington DC" }).

Input parameters:

- `autocomplete` (boolean)
- `bbox` (string)
- `country` (string)
- `fuzzyMatch` (boolean)
- `language` (string)
- `limit` (number)
- `proximity` (string)
- `query` (string, required)
- `types` (string)

### `geocode_reverse` (~115 tokens)

"What's at [lat,lng]" / "reverse geocode coordinates" / "what address is at these coords" / "what place is at this GPS point" — convert longitude / latitude into the nearest street address, neighborhood, city, region, or country via Mapbox's global geocoder. Works worldwide.

Input parameters:

- `country` (string)
- `language` (string)
- `lat` (number, required)
- `limit` (number)
- `lon` (number, required)
- `types` (string)

### `directions` (~194 tokens)

"Directions from A to B" / "how long does it take to drive from X to Y" / "how far is [A] from [B]" / "walking / cycling / driving directions" / "navigation between points" / "shortest route" — turn-by-turn routing between two or more coordinates. Returns geometry, distance (meters), duration (seconds), voice + banner instructions, and alternatives. Profile: driving, driving-traffic, walking, or cycling. Backed by Mapbox's commercial-grade traffic data and global road network.

Input parameters:

- `alternatives` (boolean)
- `annotations` (string)
- `banner_instructions` (boolean)
- `coordinates` (array, required)
- `geometries` (string)
- `language` (string)
- `overview` (string)
- `profile` (string)
- `steps` (boolean)
- `voice_instructions` (boolean)

### `directions_matrix` (~111 tokens)

"Distance matrix" / "drive times between multiple points" / "travel times grid" / "all-to-all distances" — N×M distance and duration matrix between many coordinates. Use for traveling-salesman, delivery routing, nearest-warehouse, or "which of these N stores is closest to each of these M customers" questions.

Input parameters:

- `annotations` (string)
- `coordinates` (array, required)
- `destinations` (string)
- `profile` (string)
- `sources` (string)

### `isochrone` (~177 tokens)

"How far can I get in [N] minutes from [point]" / "reachable area in [time]" / "drive-time / walk-time / cycle-time polygons" / "delivery zone within [radius]" / "service area around [location]" — isochrone polygons (reachable area within X minutes or meters) from a starting coordinate by car, walking, or cycling. Use for site-selection, delivery-zone, commute-shed, and "how big a catchment do I have" questions.

Input parameters:

- `contours_colors` (string)
- `contours_meters` (string)
- `contours_minutes` (string)
- `coordinates` (array, required): [lon, lat]
- `denoise` (number)
- `generalize` (number)
- `polygons` (boolean)
- `profile` (string, required)

### `map_matching` (~137 tokens)

"Snap GPS trace to roads" / "clean up noisy GPS coordinates" / "match track to road network" — takes a sequence of GPS points and returns the most likely path along the road network. Use for vehicle telematics, fitness-tracker cleanup, or "what road did this driver actually take" questions.

Input parameters:

- `annotations` (string)
- `coordinates` (array, required)
- `geometries` (string)
- `overview` (string)
- `profile` (string)
- `radiuses` (string)
- `steps` (boolean)
- `tidy` (boolean)
- `timestamps` (string)

### `tilequery` (~116 tokens)

Query features inside a Mapbox vector tile around a coordinate — what POIs / roads / boundaries / buildings are within a radius of a point. Specialized GIS query against a specific tileset_id; most users want geocode_reverse or directions instead.

Input parameters:

- `dedupe` (boolean)
- `geometry` (string)
- `lat` (number, required)
- `layers` (string)
- `limit` (number)
- `lon` (number, required)
- `radius` (number)
- `tileset_id` (string, required)

### `static_image_url` (~151 tokens)

"Static map image of [location]" / "embed a map of [coords]" / "screenshot a map" / "thumbnail map" — generates a Mapbox static-tile image URL for embedding in slack, docs, emails, or dashboards. Pass style + coords + zoom + width/height; returns a fetchable PNG URL. No client-side JS or interactivity required.

Input parameters:

- `bearing` (number)
- `height` (number, required)
- `lat` (number, required)
- `lon` (number, required)
- `pitch` (number)
- `retina` (boolean)
- `style_id` (string, required)
- `width` (number, required)
- `zoom` (number, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-mapbox/pipeworx-mcp-mapbox#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 62
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75

## Common questions

### What is the Mapbox MCP server?

Mapbox is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mapbox. Mapbox MCP. This page covers its npm package (@pipeworx/mcp-mapbox).

### Is the Mapbox MCP server safe to use?

Mapbox scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Mapbox MCP server expose?

Mapbox exposes 8 tools: geocode_forward, geocode_reverse, directions, directions_matrix, isochrone, and 3 more. Their descriptions and schemas cost roughly 1,169 tokens of context every time the server is loaded.

### Is the Mapbox MCP server still maintained?

Mapbox is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Mapbox MCP server under?

Mapbox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Mapbox MCP server?

VerifyMCP ran 16 checks on Mapbox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-mapbox
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-mapbox
- Repository: https://github.com/pipeworx-io/mcp-mapbox
- Website: https://pipeworx.io/packs/mapbox
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-mapbox/pipeworx-mcp-mapbox.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-mapbox/pipeworx-mcp-mapbox/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-mapbox/pipeworx-mcp-mapbox.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-mapbox/pipeworx-mcp-mapbox