Is Livetrafficcam free?

Yes, Livetrafficcam is free to use.

How do I install Livetrafficcam?

Livetrafficcam is a local plugin. Install it using npm package: livetrafficcam-mcp and add the generated configuration snippet to your AI app's MCP config file. Then restart your AI app.

Is Livetrafficcam safe to use?

Livetrafficcam scored 5.2/10 (moderate risk) in MCP Marketplace's automated security scan. It has 5 high or critical findings to review. It's listed, but review the security report on this page before installing.

What AI apps work with Livetrafficcam?

Livetrafficcam uses the Model Context Protocol (MCP) and works with any MCP-compatible AI app, including Claude, ChatGPT / Codex, Gemini, Copilot, Cursor, and more.

Back to Browse

Livetrafficcam MCP Server

by bzsasson

Developer ToolsModerate5.2LocalNew

Free

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

About

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

Security Report

5.2

Moderate5.2Moderate Risk

This is a well-constructed MCP server for accessing public traffic camera data from livetrafficcam.com. The code demonstrates strong security practices with proper input validation, no hardcoded credentials, and appropriate use of the public API. Permissions align well with the server's purpose. Minor quality improvements around error handling and logging are noted but do not materially impact security. Supply chain analysis found 5 known vulnerabilities in dependencies (2 critical, 3 high severity). Package verification found 1 issue.

7 files analyzed · 10 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

How to Install

Add this to your MCP configuration file:

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

Documentation

View on GitHub

From the project's GitHub README.

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 (claude_desktop_config.json):

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

Claude Code:

claude mcp add livetrafficcam -- npx -y livetrafficcam-mcp

Cursor (.cursor/mcp.json):

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

Tools

list_states — states covered, camera counts, and a liveness summary per state. Example: "Which states have traffic camera coverage?"
cameras_by_state — cameras for a two-letter state code, with an optional route filter. Example: "Show live cameras on I-90 in Washington."
cameras_for_entity — cameras for a named pass, corridor, bridge or tunnel slug. Example: "What do the Donner Pass cameras show?" uses donner-pass.
camera_status — one camera's verified-live status, last live time, and official DOT source. Example: "Is the I-90 floating bridge camera up?"
state_uptime — measured uptime for a state's camera fleet: live, stale and dead counts plus the 14-day check success rate. Example: "How reliable are Washington's traffic cameras?"

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.