npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

livetrafficcam-mcp

v1.0.0

Published

MCP server for live US traffic cameras: state DOT feeds with verified live status, from livetrafficcam.com

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.

More from the same data:

License

MIT