
LiveTrafficCam MCP Server
io.github.bzsasson由 GitHub 账号 bzsasson 发布v1.0.0更新于 Oct 25, 2026
Live US traffic cameras from state DOT feeds with verified live status, via livetrafficcam.com
概览
本地 MCP 服务器,通过 LiveTrafficCam 公共 API 让助手查询经核验的实时美国交通摄像头(来源为各州交通部数据)。
- 可以做什么
- 列出覆盖的州及摄像头数量与在线情况汇总,按两位州代码(可选路线过滤)或按山口、走廊、桥梁、隧道的名称标识查找摄像头。查询单个摄像头的核验在线状态、最近在线时间和官方交通部来源,并读取各州摄像头群的实测在线率,包括在线、过期、失效数量及 14 天检查成功率。结果以紧凑 JSON 返回,含来源链接和机构署名,缓存 60 秒。
- 适用场景
- 适合在用户询问当前路况、某条公路、山口、桥梁或隧道摄像头是否在线,或某州交通摄像头覆盖可靠性时使用。它只做只读查询,不提供导航或路线规划。
- 运行要求
- 通过 npx 以 stdio 在本地运行,需要 Node.js 20 或更高版本。未声明 API 密钥、环境变量或请求头。每次工具调用都会向 livetrafficcam.com 公共 API 发起网络请求。
安装
在 SourceWeft 中
- 打开 控制台中的 LiveTrafficCam MCP Server,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
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):
Claude Code:
Cursor (.cursor/mcp.json):
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?" usesdonner-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:
- Camera uptime report — measured per-state uptime of official DOT cameras.
- Traffic camera statistics — how many official DOT traffic cameras exist, per state and agency.
- Donner Pass cameras — an example of the pass pages the entity tool points at.
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
来源:README.md,提交 be6839b
工具
0版本历史
1- v1.0.0最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分