
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 分