LiveTrafficCam MCP Server
NPM · LIVETRAFFICCAM-MCP · SCANNED SEP 20
Live US traffic cameras from state DOT feeds with verified live status, via livetrafficcam.com
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 Security98
- 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
- 31 of 96 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 19 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 Management67
- Stability observed for 20 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 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
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
{
"mcpServers": {
"bzsasson-livetrafficcam-mcp": {
"command": "npx",
"args": [
"-y",
"livetrafficcam-mcp"
]
}
}
} {
"servers": {
"bzsasson-livetrafficcam-mcp": {
"command": "npx",
"args": [
"-y",
"livetrafficcam-mcp"
]
}
}
} codex mcp add bzsasson-livetrafficcam-mcp -- npx -y livetrafficcam-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bzsasson-livetrafficcam-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"livetrafficcam-mcp"
],
"enabled": true
}
}
} openclaw mcp add bzsasson-livetrafficcam-mcp --command npx --arg -y --arg livetrafficcam-mcp
mcp_servers:
bzsasson-livetrafficcam-mcp:
command: "npx"
args: ["-y", "livetrafficcam-mcp"] {
"McpServers": {
"bzsasson-livetrafficcam-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"livetrafficcam-mcp"
]
}
}
} assistant mcp add bzsasson-livetrafficcam-mcp -t stdio -c npx -a -y livetrafficcam-mcp
{
"mcpServers": {
"bzsasson-livetrafficcam-mcp": {
"command": "npx",
"args": [
"-y",
"livetrafficcam-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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +4
- Stability: unverified → 0.27 ▲ functional
- 31 Aug 26 81
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 20 Sept 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 | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2c58a772f6873d1ad0cc33f4c7f7491659a3e8a0ab5016a71349bc71ff264ef45af79eaac3e84ef0f70e870903d5d1730e78080e827f74051c6242ba2 |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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.
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 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 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 20 September 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.