mapbox-docs (mapbox/mcp-docs-server) is an MCP server listed on the M8ven Trust Index. It scores 72 out of 100, grade C. It declares 3 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
72/100

mapbox-docs

Provides AI assistants with instant access to Mapbox documentation and reference materials through tools and resources, with no Mapbox access token required.

→ mapbox/mcp-docs-server· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

mapbox

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

⚡ Connect GitHub for Live Monitored

Install from

Glamanot scored here

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
⚠️
Known vulnerabilities in dependencies: 2 high
Affects packages this MCP installs at runtime. Upgrade or remove the affected dependency.
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
✅
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// known CVEs in dependencies2 high1 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

high@opentelemetry/auto-instrumentations-node@0.74.0GHSA-q7rr-3cgh-j5r3

Prometheus exporter process crash via malformed HTTP request

high@opentelemetry/sdk-node@0.216.0GHSA-q7rr-3cgh-j5r3

Prometheus exporter process crash via malformed HTTP request

lowvitest@4.1.4GHSA-82fw-gwwq-j7x9

Vitest: Path Traversal / Arbitrary File Read via @vitest/mocker Redirect Mock

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configHOSTNAME
configMAPBOX_DOCS_CACHE_TTL_MS
configMAPBOX_DOCS_HOST_OVERRIDE
configOTEL_EXPORTER_OTLP_ENDPOINT
configOTEL_EXPORTER_OTLP_HEADERS
configOTEL_LOG_LEVEL
configOTEL_SERVICE_NAME
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

3/3 tools missing one or more hints — batch_get_documents_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_document_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); search_mapbox_docs_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint). OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool test coverage

Only 0/3 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Production dependencies are patched

0 critical, 2 high severity in production deps — @opentelemetry/auto-instrumentations-node@0.74.0 (high), @opentelemetry/sdk-node@0.216.0 (high)

Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 4 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/mapbox/mcp-docs-server?variant=verified)](https://m8ven.ai/mcp/mapbox/mcp-docs-server)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: d1f32cc42db23183a91d4c516462022e08976fc2
code hash: 340186a09bae96cfda19102d08556d36aa031e7694fc94b7a19889e624c67fe2
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client