io.github.mapbox/mcp-docs-server
REMOTE · MCP-DOCS.MAPBOX.COM · 2 COMPONENTS
AI access to Mapbox docs, API references, style specs, and guides. No token required.
Available components
Last scanned (22 hours ago)
Scores higher than 98% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Code Search and Documentation
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability89
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 862 tokens (~66/item across 13 items; 3 tools + 10 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 0
- Tool “get_document_tool” rewrote its description, which is the text the model reads security
- Server version: 0.3.1 → 0.3.2 functional
- “batch_get_documents_tool” reworded the description of “urls” cosmetic
- “get_document_tool” reworded the description of “url” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp-docs.mapbox.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.mapbox.com | CN=Amazon RSA 2048 M04,O=Amazon,C=US | 6 Aug 2026 | 19 Feb 2027 | RSA 2048 | SHA256-RSA | a8f5d714fba0d3b6d5815718d593480 |
| SANs: *.mapbox.com, mapbox.com | ||||||
| CN=Amazon RSA 2048 M04,O=Amazon,C=US (CA) | CN=Amazon Root CA 1,O=Amazon,C=US | 23 Aug 2022 | 23 Aug 2030 | RSA 2048 | SHA256-RSA | 773124f2a952e3ed18a58bdb85d1bc0ce5f27 |
| CN=Amazon Root CA 1,O=Amazon,C=US (CA) | CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US | 25 May 2015 | 31 Dec 2037 | RSA 2048 | SHA256-RSA | 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6 |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp-docs.mapbox.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| mapbox.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | form-action *;default-src 'self';base-uri 'self';font-src 'self' https: data:;frame-ancestors 'self';img-src 'self' data:;object-src 'none';script-src 'self';script-src-attr 'none';style-src 'self' https: 'unsafe-inline';upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp-docs.mapbox.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp-docs.mapbox.com/mcp | HTTPS enforced | 301 | https://mcp-docs.mapbox.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
batch_get_documents_tool Batch Get Mapbox Documents Tool ~89
Fetch the full content of multiple Mapbox documentation pages in a single call (max 20). More efficient than calling get_document_tool multiple times. Returns an array of results — failed pages include an error message rather than failing the whole batch.
| Name | Type | Req | Description |
|---|---|---|---|
| urls | array | yes | Array of Mapbox documentation page URLs to fetch (max 20). All must be https://docs.mapbox.com URLs. |
No output schema declared.
No examples provided.
get_document_tool Get Mapbox Document Tool ~103
Fetch the full content of a specific Mapbox documentation page by URL. Use this after search_mapbox_docs_tool to follow a link from the search results and retrieve the complete page content. For fetching multiple pages at once, use batch_get_documents_tool instead.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | URL of a Mapbox documentation page to fetch. Must be an https://docs.mapbox.com URL (e.g. https://docs.mapbox.com/api/search/geocoding/). |
No output schema declared.
No examples provided.
search_mapbox_docs_tool Search Mapbox Docs Tool ~132
Search Mapbox documentation by keyword or natural language query. Searches across API reference, GL JS, Help Center, Style Spec, Studio, Search JS, iOS/Android Maps and Navigation SDKs, and Tilesets. Returns ranked results with titles, URLs, and descriptions. Use get_document_tool to fetch the full content of a result page.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Maximum number of results to return (1–20, default 5). |
| query | string | yes | Search query for Mapbox documentation (e.g. "add a marker", "camera animation", "geocoding API"). |
No output schema declared.
No examples provided.
How do I install the io.github.mapbox/mcp-docs-server server?
io.github.mapbox/mcp-docs-server is a hosted endpoint at https://mcp-docs.mapbox.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp-docs.mapbox.com
claude mcp add --transport http mapbox-mcp-docs-server 'https://mcp-docs.mapbox.com/mcp'
What is the io.github.mapbox/mcp-docs-server server?
io.github.mapbox/mcp-docs-server is listed in the public MCP registry as io.github.mapbox/mcp-docs-server. AI access to Mapbox docs, API references, style specs, and guides. No token required. This page covers its hosted endpoint (https://mcp-docs.mapbox.com/mcp).
Is the io.github.mapbox/mcp-docs-server server safe to use?
io.github.mapbox/mcp-docs-server scores 90 out of 100 on VerifyMCP. 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 io.github.mapbox/mcp-docs-server server expose?
io.github.mapbox/mcp-docs-server exposes 3 tools: get_document_tool, batch_get_documents_tool, search_mapbox_docs_tool. Their descriptions and schemas cost roughly 324 tokens of context every time the server is loaded.
Does the io.github.mapbox/mcp-docs-server server require authentication?
No. We connected to io.github.mapbox/mcp-docs-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.mapbox/mcp-docs-server server still maintained?
io.github.mapbox/mcp-docs-server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.