mcp-server@0.18.1
VERIFIED· not startedPublisher claims: "Mapbox MCP server." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
MAPBOX_ACCESS_TOKENConfiguration, not credentials: CLIENT_NEEDS_RESOURCE_FALLBACK, MAPBOX_API_ENDPOINT, OTEL_EXPORTER_CONSOLE_ENABLED, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_HEADERS, OTEL_LOG_LEVEL, OTEL_SERVICE_NAME, OTEL_TRACING_ENABLED, VITEST- Where it talks to
- mapbox.com (its own)
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for MAPBOX_ACCESS_TOKEN and talks to mapbox.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.18.0
vet-skills diff mcp-server 0.18.0 0.18.1This version reaches for something 0.18.0 did not: 1 new install script (patch-package || (cd ../../.. && node ./node_modules/patch-package/index.js --patch-dir ./node_modules/@mapbox/mcp-server/patches) || true). Compared from the two recorded runs, not from source.
- New install scripts
- patch-package || (cd ../../.. && node ./node_modules/patch-package/index.js --patch-dir ./node_modules/@mapbox/mcp-server/patches) || true
0.18.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-17 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 40 s · 3 scenarios · 0 deviationsStatic findings
// Load .env from current working directory (where npm run is executed)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Load environment variables from .env file if presentFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const envPath = (0, node_path_1.join)(process.cwd(), '.env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."dev:http": "npx -y tsx scripts/dev-http-server.ts",Fix: Pin versions and sources; vendor anything fetched at install time.// Record .env loading as a span (retrospectively since it happened before tracing init)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Read and parse .env file using Node.js built-in parseEnvFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Read and parse .env file using Node.js built-in parseEnvFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.…y": "node -e \"console.log('🔍 Verifying tracing setup with Jaeger...\\n1. Copy .env.example to .env and add your MAPBOX_ACCESS_TOKEN\\n2. Start Jaeger: npm run tra…Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.this.log('warning', `${this.name}: Output schema validation failed: ${validationError instanceof Error ? validationError.message : 'Unknown validation error'}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// Record .env loading as a span (retrospectively since it happened before tracing init)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."inspect:dev": "npx @modelcontextprotocol/inspector -e MAPBOX_ACCESS_TOKEN=\"$MAPBOX_ACCESS_TOKEN\" npx -y tsx src/index.ts",Fix: Pin versions and sources; vendor anything fetched at install time.const envPath = join(process.cwd(), '.env');Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.// Load .env from current working directory (where npm run is executed)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.this.log('warning', `${this.name}: Output schema validation failed: ${validationError instanceof Error ? validationError.message : 'Unknown validation error'}`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.// Load environment variables from .env file if presentFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Not checked against OSV yet; the weekly check has not reached this version.