Skip to main content
Glama
shughestr

Vancam MCP Server

by shughestr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Vancam MCP Server

No user-submitted related servers found.

    Related Servers

    • Luxxon

      luxxon-dev
      A
      license
      A
      quality
      D
      maintenance
      On-demand live vision MCP for AI agents — open a session at a lat/lng, receive a JPEG snapshot or WebRTC stream, settled per-second in USDC on Base. Four tools (get_session, get_frame, get_stream_url, cancel_session); currently Base Sepolia testnet.
      4
      1
      MIT

    • aria-mcp-trafik-dk

      kimhjort
      A
      license
      A
      quality
      C
      maintenance
      Provides access to real-time Danish road traffic events, roadworks, and queues via public data from Vejdirektoratet, enabling AI assistants to check road conditions without any API keys.
      3
      MIT

    • trafikverket-mcp

      hniska
      F
      license
      A
      quality
      C
      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
      -
    • TomTom MCP Server by tomtom-international

      TomTom MCP Serverofficial

      tomtom-international
      A
      license
      A
      quality
      B
      maintenance
      Provides seamless access to TomTom's location services including search, routing, traffic and static maps data, enabling easy integration of precise geolocation data into AI workflows and development environments.
      12
      14
      394 npm
      55
      Apache 2.0
    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

    A4.7/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct spatial query mode (bounds, radius, route, nearest) plus image retrieval and API documentation. There is no overlap; an agent can easily select the right tool based on the user's query.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case, with 'camera(s)' as the object. The verbs list, get, and describe are all clear and predictable, making the naming internally consistent.

    Tool Count5/5

    Six tools is an appropriate size for a camera discovery and retrieval server. Each spatial query type is represented, plus image fetching and a meta-documentation tool, with no unnecessary bloat.

    Completeness5/5

    The tool set covers all spatial search modes from the VanCam web app (bounding box, radius, route corridor, nearest neighbor) and includes live image retrieval that works around the API key limitation. There are no obvious gaps for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources