Skip to main content
Glama
bzsasson

livetrafficcam-mcp

by bzsasson
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to livetrafficcam-mcp

No user-submitted related servers found.

    Related Servers

    • trafikverket-mcp

      hniska
      F
      license
      A
      quality
      D
      maintenance
      Provides real-time access to Swedish road weather, traffic cameras, road conditions, and traffic flow data from Trafikverket (Swedish Transport Administration). Enables users to query weather stations, cameras, traffic situations, and flow data through natural language.
      10
      -

    • CommuteScout

      nicglazkov
      A
      license
      A
      quality
      A
      maintenance
      Provides live California road conditions, route planning, and an AI assistant over MCP, enabling natural-language queries about traffic, closures, chain controls, and more.
      10
      4
      MIT

    • ia-dmv

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to Iowa DOT driver license station data, including hours, CDL testing info, and live queue camera images from waiting rooms.
      3 npm
      MIT

    • trafikkmeldinger-mcp

      smlhus1
      A
      license
      A
      quality
      B
      maintenance
      Enables querying Norwegian traffic messages (roadworks, closures, detours) from Statens vegvesen, filtered by route and time window. Supports both current and future travel times, with tools for route-based and general searches.
      3
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool targets a distinct lookup type: state overview, cameras by state/route, cameras by named entity, single-camera status, and uptime statistics. There is minor overlap between list_states and state_uptime since both mention liveness summaries, but their levels of detail and purposes are clearly different.

    Naming Consistency3/5

    Naming is readable but inconsistent: list_states uses a verb, cameras_by_state and cameras_for_entity follow a noun-by-entity pattern, while camera_status and state_uptime are noun-noun phrases. The conventions are mixed but still predictable enough to navigate.

    Tool Count5/5

    Five tools is well-scoped for a traffic camera lookup server. Each tool covers a necessary access pattern without redundancy, and the count feels neither thin nor bloated.

    Completeness4/5

    The set covers the core domain well: state coverage, camera listing by state/route and named entities, single-camera status, and uptime reporting. Minor gaps exist, such as no direct camera-image or stream endpoint and no free-text national camera search, but agents can work around these with the provided URLs.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources