Vancam
PYPI · VANCAM-MCP · SCANNED SEP 21
Search 1M+ live traffic cameras worldwide by bounds, radius, route, or nearest point.
Available components
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 0 of 32 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 53 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 912 tokens (~152/item across 6 items; 6 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 Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (83% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
How do I install the Vancam MCP server?
Vancam runs locally as a PyPI package, launched with uvx vancam-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · vancam-mcp
claude mcp add shughestr-vancam-mcp -- uvx vancam-mcp
{
"mcpServers": {
"shughestr-vancam-mcp": {
"command": "uvx",
"args": [
"vancam-mcp"
]
}
}
} {
"servers": {
"shughestr-vancam-mcp": {
"command": "uvx",
"args": [
"vancam-mcp"
]
}
}
} codex mcp add shughestr-vancam-mcp -- uvx vancam-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shughestr-vancam-mcp": {
"type": "local",
"command": [
"uvx",
"vancam-mcp"
],
"enabled": true
}
}
} openclaw mcp add shughestr-vancam-mcp --command uvx --arg vancam-mcp
mcp_servers:
shughestr-vancam-mcp:
command: "uvx"
args: ["vancam-mcp"] {
"McpServers": {
"shughestr-vancam-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"vancam-mcp"
]
}
}
} assistant mcp add shughestr-vancam-mcp -t stdio -c uvx -a vancam-mcp
{
"mcpServers": {
"shughestr-vancam-mcp": {
"command": "uvx",
"args": [
"vancam-mcp"
]
}
}
} 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.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −3
- Stability: pass → 0.80 functional
- 17 Sept 26 0
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
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 21 Sept 2026 · Analysed pypi/vancam-mcp@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| 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 →
describe_camera_api ~55
Describe the spatial camera API exposed by this MCP server. Call this first when unsure which search tool to use. Documents the same capabilities as the VanCam map web app (bounds pan, radius, route, nearest).
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_camera_image ~133
Get the live frame for a camera by asset_id, embedded directly in the tool result. api.vancam.ai requires an x-api-key header this server holds — an MCP client fetching the bare URL itself (e.g. Claude Desktop opening the link) has no way to attach that header and gets 403 Forbidden. This tool fetches the frame server-side instead and returns the image bytes. Parameters: asset_id: Vancam camera asset ID (integer as string) Returns: The live image, plus asset_id/url metadata for reference.
| Name | Type | Req | Description |
|---|---|---|---|
| asset_id | string | yes | – |
No output schema declared.
No examples provided.
get_cameras_along_route ~247
Get traffic cameras along a straight-line route between two points. Same API call as the VanCam web app (vancam.ai) route view. Cameras are returned sorted by route_fraction (0 = origin, 1 = destination). Note: Uses a straight line between origin and destination (PostGIS ST_MakeLine), not a driving route polyline. Buffer is meters perpendicular to that line. Parameters: origin_lat, origin_lon: Route start (WGS84) dest_lat, dest_lon: Route end (WGS84) buffer: Corridor width in meters (default 100, web app uses 100) limit: Max cameras (1–100, default 50, web app uses 50) active_only: If true, only camera_class=open Returns: JSON with type route_search, buffer_meters, cameras[] with route_fraction.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| buffer | number | – | – |
| dest_lat | number | yes | – |
| dest_lon | number | yes | – |
| limit | integer | – | – |
| origin_lat | number | yes | – |
| origin_lon | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_cameras_by_radius ~171
Get traffic cameras within a radius (km) of a lat/lon point. Radius search. Use when the user asks for cameras near a place, within X km of coordinates, or around an address they geocoded. Parameters: lat, lon: Center point (WGS84) radius: Search radius in kilometers (default 1.0, max 50 per API) limit: Max cameras (1–100, default 50) active_only: If true, only camera_class=open Returns: JSON with type radius_search, count, radius_km, cameras[].
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| radius | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
get_nearest_cameras ~130
Get the nearest traffic cameras to a geographic point. Nearest-neighbor search. Use when the user asks for the closest camera(s) to a location. Parameters: lat, lon: Query point (WGS84) limit: Number of cameras (1–100, default 5) active_only: If true, only camera_class=open Returns: JSON with type nearest_search and cameras[] ordered by distance_meters.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| lat | number | yes | – |
| limit | integer | – | – |
| lon | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
list_cameras ~176
List traffic cameras within a map bounding box. Same query the VanCam web app (vancam.ai) runs when the user pans/zooms the map. Use when the user asks for cameras in a visible map area or geographic rectangle. Parameters: min_lat, min_lon, max_lat, max_lon: Bounding box (WGS84) limit: Max cameras to return (1–100, default 100) active_only: If true, return only camera_class=open (live feeds) Returns: Bounds search JSON with enriched image_url per camera.
| Name | Type | Req | Description |
|---|---|---|---|
| active_only | boolean | – | – |
| limit | integer | – | – |
| max_lat | number | yes | – |
| max_lon | number | yes | – |
| min_lat | number | yes | – |
| min_lon | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | object | yes | – |
No examples provided.
What is the Vancam MCP server?
Vancam is an MCP server listed in the public MCP registry as io.github.shughestr/vancam-mcp. Search 1M+ live traffic cameras worldwide by bounds, radius, route, or nearest point. This page covers its PyPI package (vancam-mcp).
Is the Vancam MCP server safe to use?
Vancam scores 63 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. 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 Vancam MCP server expose?
Vancam exposes 6 tools: list_cameras, get_cameras_by_radius, get_cameras_along_route, get_nearest_cameras, get_camera_image, describe_camera_api. Their descriptions and schemas cost roughly 912 tokens of context every time the server is loaded.
Is the Vancam MCP server still maintained?
Vancam is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.