LiveTrafficCam MCP Server
io.github.bzsasson/livetrafficcam-mcp·v1.0.0Live US traffic cameras from state DOT feeds with verified live status, via livetrafficcam.com
0 stars39 downloads/wk
Reviews
Write oneNobody has reviewed LiveTrafficCam MCP Server yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
LiveTrafficCam MCP Server tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-29 · same rubric, same numbers if you re-run it
- Code scan8 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 41 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How LiveTrafficCam MCP Server compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,243 servers
- Downloads a week
- 39
- more than 29% of 12,306 servers with a package
Install LiveTrafficCam MCP Server in Claude Code, Cursor or VS Code
Runs npx -y livetrafficcam-mcp on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add livetrafficcam-mcp -- npx -y livetrafficcam-mcp
What the publisher says
From the LiveTrafficCam MCP Server repository's README, as published. We do not edit it. Read it on GitHub
livetrafficcam-mcp
MCP (Model Context Protocol) server for LiveTrafficCam, a directory of live US traffic cameras built on official state DOT feeds. Every camera is checked on a rolling schedule with real HTTP requests, so "live" means a verified current image, not a listing.
The server wraps the site's public JSON API. It sends one request per tool call, caches responses for 60 seconds, and returns compact JSON with a source_url you can cite.
Install
Requires Node 20 or newer.
Claude Desktop (claudedesktopconfig.json):
{
"mcpServers": {
"livetrafficcam": {
"command": "npx",
"args": ["-y", "livetrafficcam-mcp"]
}
}
}Claude Code:
claude mcp add livetrafficcam -- npx -y livetrafficcam-mcpCursor (.cursor/mcp.json):
{
"mcpServers": {
"livetrafficcam": {
"command": "npx",
"args": ["-y", "livetrafficcam-mcp"]
}
}
}Tools
per state. Example: "Which states have traffic camera coverage?"
- list_states — states covered, camera counts, and a liveness summary
optional route filter. Example: "Show live cameras on I-90 in Washington."
- camerasbystate — cameras for a two-letter state code, with an
tunnel slug. Example: "What do the Donner Pass cameras show?" uses donner-pass.
- camerasforentity — cameras for a named pass, corridor, bridge or
and official DOT source. Example: "Is the I-90 floating bridge camera up?"
- camera_status — one camera's verified-live status, last live time,
stale and dead counts plus the 14-day check success rate. Example: "How reliable are Washington's traffic cameras?"
- state_uptime — measured uptime for a state's camera fleet: live,
The camera API returns at most 200 cameras per query; tool output says so when a state has more. Fleet counts come from the camera uptime report.
Data source and attribution
All data comes from livetrafficcam.com's public API, which aggregates official state DOT camera feeds (WSDOT, Caltrans, UDOT, and others). Every camera result carries the attribution line for its agency; keep it when you display the data. Uptime numbers should cite the uptime report.
More from the same data:
— measured per-state uptime of official DOT cameras.
- Camera uptime report
— how many official DOT traffic cameras exist, per state and agency.
- Traffic camera statistics
— an example of the pass pages the entity tool points at.
- Donner Pass cameras
Also available
A Home Assistant integration puts a pass, bridge, tunnel, airport or highway on a dashboard: one camera entity per camera, a verified-live sensor each, and reported disruptions. No API keys.
License
MIT
Nothing above is checked by us. What we check is on the safety report.
LiveTrafficCam MCP Server: common questions
- Is LiveTrafficCam MCP Server safe?
- Yes, by our scan: it is graded A (88/100). Read the LiveTrafficCam MCP Server safety report
- How do I install LiveTrafficCam MCP Server?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does LiveTrafficCam MCP Server need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is LiveTrafficCam MCP Server maintained?
- The last commit was 48 days ago (2026-09-18). The latest release is v1.0.0.
- How does LiveTrafficCam MCP Server compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,243 servers); downloads a week 39 (more than 29% of 12,306 servers with a package). Full comparison.