Mapillary
NPM · @PIPEWORX/MCP-MAPILLARY · 2 COMPONENTS
Mapillary MCP — wraps the Mapillary Graph API (graph.mapillary.com)
Available components
Last scanned (10 hours ago)
Scores higher than 76% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-mapillary). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 516 tokens (~172/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-mapillary@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-mapillary |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-mapillary/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3649795454 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:17c62eb0bfd9aa6fb9d59c9ca5c2a54dca19e8ee0a3b8fe5c1503714bbe0246ac2f64f74d5325b2c1914c7093563a78560d9db425baf2cd4bdcbec5b8 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
mapillary_detections ~130
Detected objects/signs in an image. Returns Mapillary computer-vision detections (object/sign classes like "object--support--pole" or "regulatory--stop--g1") found inside a given image id. Example: mapillary_detections({ image_id: "498763468214164", _apiKey: "MLY|..." })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Mapillary access token (looks like "MLY|...") |
| image_id | string | yes | Mapillary image id (numeric string), e.g. "498763468214164" |
No output schema declared.
No examples provided.
mapillary_image ~116
Details for a Mapillary image. Given an image id, returns capture time, coordinates, compass heading, camera type, sequence id, and a 2048px thumbnail URL. Example: mapillary_image({ image_id: "498763468214164", _apiKey: "MLY|..." })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Mapillary access token (looks like "MLY|...") |
| image_id | string | yes | Mapillary image id (numeric string), e.g. "498763468214164" |
No output schema declared.
No examples provided.
mapillary_images_near ~218
Street-level images near a lat/lon point. Returns image ids, coordinates, capture time, compass heading, and a 1024px thumbnail URL. Example: mapillary_images_near({ lat: 40.7580, lon: -73.9855, radius: 30, _apiKey: "MLY|..." })
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | yes | Mapillary access token (free — create an app token at mapillary.com/dashboard/developers). Looks like "MLY|...". |
| lat | number | yes | Latitude of the center point, in degrees (-90 to 90), e.g. 40.7580 |
| limit | number | – | Max number of images to return (default 10, max 25) |
| lon | number | yes | Longitude of the center point, in degrees (-180 to 180), e.g. -73.9855 |
| radius | number | – | Search radius in meters around the point (default 50, max 50) |
No output schema declared.
No examples provided.
How do I install the Mapillary MCP server?
Mapillary runs locally as an npm package, launched with npx -y @pipeworx/mcp-mapillary. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-mapillary
claude mcp add pipeworx-io-mapillary -- npx -y @pipeworx/mcp-mapillary
What is the Mapillary MCP server?
Mapillary is an MCP server listed in the public MCP registry as io.github.pipeworx-io/mapillary. Mapillary MCP, wraps the Mapillary Graph API (graph.mapillary.com). This page covers its npm package (@pipeworx/mcp-mapillary).
Is the Mapillary MCP server safe to use?
Mapillary scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Mapillary MCP server expose?
Mapillary exposes 3 tools: mapillary_images_near, mapillary_image, mapillary_detections. Their descriptions and schemas cost roughly 464 tokens of context every time the server is loaded.
Is the Mapillary MCP server still maintained?
Mapillary is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Mapillary MCP server under?
Mapillary declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.