Mapbox Documentation MCP Server
[ tools: 3 ][ checks: 12 ][ latency: 9ms ]
93/100(A)
npx -y @mapbox/mcp-docs-server
check breakdown
✓Tools exposed — Server exposed 3 tools.
• get_document_tool
• batch_get_documents_tool
• search_mapbox_docs_tool
✓Input schemas valid — All tools have a valid JSON-Schema input definition.
!Input schema quality — 3 schema-quality issue(s) across 3 tool(s).
get_document_tool: inputSchema.additionalProperties is not set to false (extra args pass through silently)
batch_get_documents_tool: inputSchema.additionalProperties is not set to false (extra args pass through silently)
search_mapbox_docs_tool: inputSchema.additionalProperties is not set to false (extra args pass through silently)
→ Declare `required` for every schema that has properties, so agents know which params are mandatory.
→ Give every property a `description` and a concrete `type` (avoid bare `{}` placeholders).
→ Set `additionalProperties: false` on the top-level inputSchema so models can't silently pass extra, unvalidated arguments.
!Output schemas — No tools declare an outputSchema.
→ Optional: declare outputSchema for tools with structured results so agents can validate/parse output reliably.
✓Duplicate tool names — All tool names are unique.
✓Tool naming — All tool names use spec-legal characters.
✓Descriptions — Every tool and parameter is clearly described.
✓Tool annotations — Tools fully declare behavioural hints (title, readOnly, destructive, idempotent, openWorld).
✓Tool titles — All tools declare a human-readable title.
!Server instructions — No top-level instructions declared.
→ Declare instructions to guide agents on when/how to use this server.
→ Return a non-empty `instructions` string in your InitializeResult — most SDKs let you set this alongside serverInfo.
✓Handshake + list latency — tools/list responded in 9ms.
✓Resources — All 10 resource(s)/template(s) are well-described.
add the badge
Paste into your README:
[](https://scoremcp.dev/servers/mapbox-docs-mcp)