Mapbox MCP Server

Mapbox Model Context Protocol (MCP) server

MCP Servers TypeScript Listed MIT

Is Mapbox MCP Server safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 5.5 / 10
Provenance None
Signed commits 100%
Last push yesterday
Advisories None known
Compare Mapbox MCP Server
Suggest a correction

In detail: Mapbox MCP Server scores 70.4/100 (Grade B), ranked #364 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 5.5/10; 100% of recent commits are signed; no published advisory affects its latest release (@mapbox/mcp-server); last pushed 2026-11-10. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mapbox MCP Server could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Chain of custody

Scanners check what the code says. This traces who ships Mapbox MCP Server and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Signed

    github.com/mapbox/mcp-server, MIT, last pushed 2026-11-10. 100% of the last 100 commits carry a verified signature, so changes trace to a verified account.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 5.5/10 (scanned Nov 2, 2026). The checks that decide who can get a change released:

    • Code Review10
    • Branch Protection6
    • Signed Releases0
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies1
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 6
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 10
    Contributors 10
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 1
    SAST 10
    Security-Policy 10
    Signed-Releases 0
    Token-Permissions 0
    Vulnerabilities 0
  3. Published packages Linked, not attested

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @mapbox/mcp-server 0.17.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-05 OSSF Scorecard: 5.5/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Mapbox MCP Server’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Mapbox MCP Server compares in MCP Servers

  1. #213 Marketplaces MCP (RU) — Wildberries & Ozon 70.6 +0.2
  2. #214 MCP Server Couchbase 70.5 +0.1
  3. #215 Mapbox MCP Server 70.4 this agent
  4. #216 Pyxel MCP 70.4 ±0
  5. #217 Octen MCP 70.4 ±0

Bars show each HVTrust score; the tick marks Mapbox MCP Server’s 70.4.

Where the 70.4 comes from

HVTrust dimensions vs the MCP Servers average

70.4 / 100 · 100.0% confidence

Mapbox MCP Server MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.9 / 25
1.1 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
13.2 / 17
0.9 above avg 12.3
Maintenance60% last-push freshness · 40% commit activity
18.3 / 20
6.0 above avg 12.3
AdoptionLog-scaled stars · package downloads
11.2 / 20
3.6 above avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-07
Rank Moved
Rank dropped 11 spots (#363 → #374)
2026-11-05
Rank Moved
Rank rose 12 spots (#372 → #360)
2026-10-26
Rank Moved
Rank rose 16 spots (#403 → #387)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 5.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Compare with another agent
View MCP Servers Report missing data
67.9
Activity sub-score · out of 100
#215

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-11 00:08 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
368
Forks
44
Last Push
2026-11-10
yesterday
Commits (4 wk)
38
Downloads (7d)
5,677
npm
HN mentions (30d)
—
Open Issues
11
Rank Change
=
was #364

Analysis

Activity Inputs

67.9 / 100
StarsRepository reach
15.4 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
19.8 / 25
CommunityFork signal
7.7 / 20

Common questions about Mapbox MCP Server

Mapbox MCP Server has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Mapbox MCP Server publish package provenance?
No published build provenance is currently detected for Mapbox MCP Server. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Mapbox MCP Server have an OpenSSF Scorecard?
Mapbox MCP Server has an OpenSSF Scorecard score of 5.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Mapbox MCP Server actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Mapbox MCP Server use?
Mapbox MCP Server ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Mapbox MCP Server's commits signed?
100% of the last 100 commits to Mapbox MCP Server are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Mapbox MCP Server appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Mapbox MCP Server's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Mapbox MCP Server?

For maintainers

HVTrust scores Mapbox MCP Server from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Reputation Timeline

Signal history
Rank 34Grade 5HVTrust 3Scorecard 1Delisted 1Listed 1MCP 1
2026-11-07
Rank Moved
Rank dropped 11 spots (#363 → #374)
2026-11-05
Rank Moved
Rank rose 12 spots (#372 → #360)
2026-10-26
Rank Moved
Rank rose 16 spots (#403 → #387)
2026-10-15
Rank Moved
Rank rose 14 spots (#400 → #386)
2026-10-14
Rank Moved
Rank rose 11 spots (#411 → #400)
2026-10-09
Rank Moved
Rank rose 63 spots (#474 → #411)
2026-10-08
Rank Moved
Rank rose 13 spots (#487 → #474)
2026-10-07
Grade Changed
Trust grade C → B
2026-10-07
Rank Moved
Rank rose 14 spots (#501 → #487)
2026-10-05
Rank Moved
Rank rose 13 spots (#512 → #499)
2026-09-26
Rank Moved
Rank rose 12 spots (#500 → #488)
2026-09-25
Rank Moved
Rank dropped 12 spots (#488 → #500)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 307 spots (#804 → #497)
2026-09-23
HVTrust Changed
HVTrust up 35.4pts (28.7 → 64.1)
2026-09-22
Newly Listed
First tracked at rank #804
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-19
Rank Moved
Rank dropped 15 spots (#466 → #481)
2026-09-17
Grade Changed
Trust grade B → C
2026-09-17
Rank Moved
Rank dropped 33 spots (#432 → #465)
2026-09-16
Rank Moved
Rank rose 17 spots (#449 → #432)
2026-09-12
Grade Changed
Trust grade C → B
2026-09-12
Rank Moved
Rank rose 37 spots (#482 → #445)
2026-09-11
Rank Moved
Rank dropped 13 spots (#469 → #482)
2026-09-09
Rank Moved
Rank dropped 11 spots (#455 → #466)
2026-09-07
Rank Moved
Rank dropped 33 spots (#413 → #446)
2026-09-05
Scorecard Added
OSSF Scorecard: 5.5/10
2026-09-05
Grade Changed
Trust grade D → C
2026-09-05
Rank Moved
Rank rose 708 spots (#1114 → #406)
2026-09-05
HVTrust Changed
HVTrust up 27.5pts (37.1 → 64.6)
2026-09-04
Rank Moved
Rank dropped 19 spots (#1095 → #1114)
2026-09-03
Rank Moved
Rank rose 145 spots (#1240 → #1095)
2026-09-03
HVTrust Changed
HVTrust up 14.2pts (22.9 → 37.1)
2026-09-02
Rank Moved
Rank dropped 34 spots (#1206 → #1240)
2026-09-01
Rank Moved
Rank dropped 34 spots (#1172 → #1206)
2026-08-31
Rank Moved
Rank dropped 28 spots (#1144 → #1172)
2026-08-30
Rank Moved
Rank dropped 42 spots (#1102 → #1144)
2026-08-29
Rank Moved
Rank dropped 66 spots (#1036 → #1102)
2026-08-28
Rank Moved
Rank dropped 34 spots (#1002 → #1036)
2026-08-27
Rank Moved
Rank dropped 25 spots (#977 → #1002)
2026-08-26
Rank Moved
Rank dropped 95 spots (#882 → #977)
2026-08-20
Rank Moved
Rank rose 14 spots (#903 → #889)
2026-08-19
Rank Moved
Rank dropped 17 spots (#886 → #903)
2026-08-17
Rank Moved
Rank rose 11 spots (#897 → #886)
2026-08-16
Rank Moved
Rank dropped 21 spots (#876 → #897)

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 70.4 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/mapbox-mcp-server.svg)](https://hvtracker.net/agents/mapbox-mcp-server)
HTML:
<a href="https://hvtracker.net/agents/mapbox-mcp-server"><img src="https://hvtracker.net/badge/mapbox-mcp-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON