# LiveTrafficCam MCP Server (npm · livetrafficcam-mcp)

Live US traffic cameras from state DOT feeds with verified live status, via livetrafficcam.com

- Trust score: 91/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- npm · `livetrafficcam-mcp`: 91/100 (this document), [markdown](https://verifymcp.io/servers/bzsasson-livetrafficcam-mcp/livetrafficcam-mcp.md), [page](https://verifymcp.io/servers/bzsasson-livetrafficcam-mcp/livetrafficcam-mcp)

## Channel facts

- Registry: `npm`
- Package: `livetrafficcam-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to bzsasson/livetrafficcam-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 81/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 380 tokens (~76/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 67/100
  - Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add bzsasson-livetrafficcam-mcp -- npx -y livetrafficcam-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "bzsasson-livetrafficcam-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livetrafficcam-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "bzsasson-livetrafficcam-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livetrafficcam-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add bzsasson-livetrafficcam-mcp -- npx -y livetrafficcam-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "bzsasson-livetrafficcam-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "livetrafficcam-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add bzsasson-livetrafficcam-mcp --command npx --arg -y --arg livetrafficcam-mcp
```

### Hermes

```yaml
mcp_servers:
  bzsasson-livetrafficcam-mcp:
    command: "npx"
    args: ["-y", "livetrafficcam-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "bzsasson-livetrafficcam-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "livetrafficcam-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add bzsasson-livetrafficcam-mcp -t stdio -c npx -a -y livetrafficcam-mcp
```

### Other

```json
{
  "mcpServers": {
    "bzsasson-livetrafficcam-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "livetrafficcam-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 91, +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.

### 2026-09-18 (score 90, +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.

### 2026-09-16 (score 89, +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.

### 2026-09-14 (score 88, +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.

### 2026-09-11 (score 87, +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.

### 2026-09-09 (score 86, +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.

### 2026-09-08 (score 85, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-31 (score 81)

First indexed and scored.

## MCP tools (5)

### `list_states` (~39 tokens)

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.

### `cameras_by_state` (~107 tokens)

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.

Input parameters:

- `live_only` (boolean): Only cameras currently verified live (default true)
- `route` (string): Optional route filter, e.g. I-80 or SR 20
- `state` (string, required): Two-letter state code, e.g. WA

### `cameras_for_entity` (~64 tokens)

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.

Input parameters:

- `entity_slug` (string, required): Entity slug, e.g. donner-pass

### `camera_status` (~105 tokens)

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.

Input parameters:

- `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, required): Two-letter state code, e.g. WA

### `state_uptime` (~65 tokens)

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.

Input parameters:

- `state` (string, required): Two-letter state code, e.g. WA

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/bzsasson-livetrafficcam-mcp/livetrafficcam-mcp#diagnostics

## Score history

- 2026-09-20: 91
- 2026-09-19: 90
- 2026-09-18: 90
- 2026-09-17: 89
- 2026-09-16: 89
- 2026-09-15: 88
- 2026-09-14: 88
- 2026-09-13: 87
- 2026-09-12: 87
- 2026-09-11: 87
- 2026-09-10: 86
- 2026-09-09: 86
- 2026-09-08: 85
- 2026-09-07: 81
- 2026-09-06: 81
- 2026-09-05: 81
- 2026-09-04: 81
- 2026-09-03: 81
- 2026-09-02: 81
- 2026-09-01: 81
- 2026-08-31: 81

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/livetrafficcam-mcp
- Socket report: https://socket.dev/npm/package/livetrafficcam-mcp
- Repository: https://github.com/bzsasson/livetrafficcam-mcp
- Website: https://livetrafficcam.com/
- Changelog RSS feed: https://verifymcp.io/servers/bzsasson-livetrafficcam-mcp/livetrafficcam-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/bzsasson-livetrafficcam-mcp/livetrafficcam-mcp.json
- HTML version of this page: https://verifymcp.io/servers/bzsasson-livetrafficcam-mcp/livetrafficcam-mcp