LiveTrafficCam MCP Server
NPM · LIVETRAFFICCAM-MCP
Live US traffic cameras from state DOT feeds with verified live status, via livetrafficcam.com
Available components
Last scanned (16 hours ago)
Scores higher than 93% 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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to bzsasson/livetrafficcam-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 65 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 380 tokens (~76/item across 5 items; 5 tools + 0 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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
- Stability: 0.97 → pass security
- 3 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 27 Oct 26 0
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
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/livetrafficcam-mcp@1.0.0
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 | bzsasson/livetrafficcam-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bzsasson/livetrafficcam-mcp/.github/workflows/release.yml@refs/tags/v1.0.0 |
| Rekor log index | 2660776526 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2c58a772f6873d1ad0cc33f4c7f7491659a3e8a0ab5016a71349bc71ff264ef45af79eaac3e84ef0f70e870903d5d1730e78080e827f74051c6242ba2 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| 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 →
camera_status ~105
Live status of one camera: verified-live state, last live time, official DOT source URL and attribution. Identify the camera by id, slug, or a name fragment, within a state.
| Name | Type | Req | Description |
|---|---|---|---|
| camera_id | integer | – | Camera id from other tools |
| name | string | – | Camera name or fragment, e.g. 'Floating Bridge' |
| slug | string | – | Camera slug from other tools |
| state | string | yes | Two-letter state code, e.g. WA |
No output schema declared.
No examples provided.
cameras_by_state ~107
List traffic cameras for a US state (two-letter code), optionally filtered by route (e.g. "I-80"). The API returns at most 200 cameras per query; use state_uptime for full fleet counts.
| Name | Type | Req | Description |
|---|---|---|---|
| live_only | boolean | – | Only cameras currently verified live (default true) |
| route | string | – | Optional route filter, e.g. I-80 or SR 20 |
| state | string | yes | Two-letter state code, e.g. WA |
No output schema declared.
No examples provided.
cameras_for_entity ~64
List traffic cameras for a named pass, corridor, bridge or tunnel by its slug (e.g. donner-pass, snoqualmie-pass). Includes the matching livetrafficcam.com page URL.
| Name | Type | Req | Description |
|---|---|---|---|
| entity_slug | string | yes | Entity slug, e.g. donner-pass |
No output schema declared.
No examples provided.
list_states ~39
List the US states covered by livetrafficcam.com with camera counts and a liveness summary per state. Counts come from the measured camera uptime report.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
state_uptime ~65
Measured camera uptime for one state: how many official DOT cameras are live, stale or dead right now, and the 14-day check success rate. Cite the report URL when quoting these numbers.
| Name | Type | Req | Description |
|---|---|---|---|
| state | string | yes | Two-letter state code, e.g. WA |
No output schema declared.
No examples provided.
How do I install the LiveTrafficCam MCP Server server?
LiveTrafficCam MCP Server runs locally as an npm package, launched with npx -y livetrafficcam-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · livetrafficcam-mcp
claude mcp add bzsasson-livetrafficcam-mcp -- npx -y livetrafficcam-mcp
What is the LiveTrafficCam MCP Server server?
LiveTrafficCam MCP Server is listed in the public MCP registry as io.github.bzsasson/livetrafficcam-mcp. Live US traffic cameras from state DOT feeds with verified live status, via livetrafficcam.com. This page covers its npm package (livetrafficcam-mcp).
Is the LiveTrafficCam MCP Server server safe to use?
LiveTrafficCam MCP Server scores 90 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 LiveTrafficCam MCP Server server expose?
LiveTrafficCam MCP Server exposes 5 tools: list_states, cameras_by_state, cameras_for_entity, camera_status, state_uptime. Their descriptions and schemas cost roughly 380 tokens of context every time the server is loaded.
Is the LiveTrafficCam MCP Server server still maintained?
LiveTrafficCam MCP Server 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 LiveTrafficCam MCP Server server under?
LiveTrafficCam MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the LiveTrafficCam MCP Server server?
VerifyMCP ran 16 checks on LiveTrafficCam MCP Server, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.