Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Vancam

by shughestrversion 0.1.0i★ –iRuns on your computer
Registry nameio.github.shughestr/vancam-mcp

Install

Overview

Description from the maker (original English)

Search 1M+ live traffic cameras worldwide by bounds, radius, route, or nearest point.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Search & AI memory
  • You need to fill in: VANCAM_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: VANCAM_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • PyPIPython’s uv installed (for the uvx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "vancam": {
      "command": "uvx",
      "args": [
        "vancam-mcp"
      ],
      "env": {
        "VANCAM_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add vancam --env VANCAM_API_KEY=your-value -- uvx vancam-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "vancam": {
      "command": "uvx",
      "args": [
        "vancam-mcp"
      ],
      "env": {
        "VANCAM_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "vancam": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "vancam-mcp"
      ],
      "env": {
        "VANCAM_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • VANCAM_API_KEY secret env
    Personal Vancam.ai API key for higher rate limits. Optional — falls back to a shared, low-limit key if unset.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account shughestr, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 5717 servers in this category
  • Published to the registry more recently than 26% of the other 5717 servers in this category
  • Basic checks equal to or better than 100% of the other 5717 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Vancam safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: VANCAM_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

by upstashWidely used↓ 972.7K/wk★ 64.2KUpdated 2 days ago

Computer or cloud

Codebase Memory

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

by DeusDataWidely used↓ 18K/wk★ 48.1KUpdated 22 days ago

Runs on your computer

Exa

Connect AI agents to Exa for web search, content fetching, and multi-step research.

by exa-labsWidely used★ 5.2KUpdated 2 months ago

Runs in the cloud✓ exa.ai

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Vancam MCP Server

Vancam.ai — Traffic Cameras & Road Conditions — as an MCP (Model Context Protocol) server. Gives AI agents live access to the same camera network behind Vancam's road-condition data: over 1 million traffic cameras worldwide, searchable by map bounds, radius, route, or nearest point.

  • 🔍 Search cameras by bounding box, radius, route corridor, or nearest-to-point
  • 📸 Fetch live frames by camera asset ID, returned directly in the tool result
  • 🌐 Real-time data from the same backend that powers the Vancam.ai map
  • 🤖 AI-ready — built with FastMCP, works with Claude Desktop, Claude Code, and any MCP-compatible client

Quick Start

Option A: Install from PyPI

uvx vancam-mcp   # or: pip install vancam-mcp

Option B: Clone and install dependencies

git clone https://github.com/shughestr/vancam-mcp.git

cd vancam-mcp pip install -r requirements.txt

2. (Optional) Set up an API key

Requests work out of the box using a shared, rate-limited key (1 req/s, 500/month, pooled across all anonymous users). For higher limits, grab a free personal key from your Vancam.ai account page and set it as an environment variable:

cp .env.example .env   # then edit .env
# .env

VANCAM_API_KEY=your_personal_key_here

3. Register the server with your MCP client

For Claude Desktop or Claude Code, add to your MCP config. If installed from PyPI (Option A):

{

"mcpServers": { "vancam": { "command": "uvx", "args": ["vancam-mcp"], "env": { "VANCAM_API_KEY": "" } } } }

If running from a local clone (Option B, see .mcp.json in this repo):

{

"mcpServers": { "vancam": { "command": "python3", "args": ["/absolute/path/to/vancam-mcp/vancam_mcp/server.py"], "env": { "VANCAM_API_KEY": "" } } } }

VANCAM_API_KEY is optional — leave it blank to use the shared, rate-limited key.

Restart your client, and the tools below become available.

Available Tools

list_cameras

List cameras within a bounding box — the same query the VanCam map runs on pan/zoom.

list_cameras(min_lat=49.2, min_lon=-123.2, max_lat=49.3, max_lon=-123.0, limit=50)
ParameterTypeDescription
min_lat, min_lon, max_lat, max_lonfloatBounding box (WGS84)
limitint, optionalMax results, 1–100 (default 100)
active_onlybool, optionalOnly camera_class=open live feeds (default false)
get_cameras_by_radius

Get cameras within a radius of a point.

get_cameras_by_radius(lat=49.28, lon=-123.12, radius=1.0, limit=20)
ParameterTypeDescription
lat, lonfloatCenter point (WGS84)
radiusfloat, optionalRadius in km (default 1.0)
limitint, optionalMax results (default 50)
active_onlybool, optionalOnly open/live cameras
get_cameras_along_route

Get cameras along a straight-line corridor between two points.

get_cameras_along_route(

origin_lat=49.2827, origin_lon=-123.1207, dest_lat=49.1666, dest_lon=-123.1367, buffer=200.0, limit=50 )

| Parameter | Type | Description |

|---|---|---| | origin_lat, origin_lon, dest_lat, dest_lon | float | Route endpoints | | buffer | float, optional | Corridor width in meters (default 100.0) | | limit | int, optional | Max results (default 50) | | active_only | bool, optional | Only open/live cameras |

Results are sorted by route_fraction (0 = origin, 1 = destination). Note: this is a straight line between the two points, not a driving route.

get_nearest_cameras

Get the closest cameras to a point.

get_nearest_cameras(lat=49.2827, lon=-123.1207, limit=5)
ParameterTypeDescription
lat, lonfloatQuery point (WGS84)
limitint, optionalNumber of cameras (default 5)
active_onlybool, optionalOnly open/live cameras
get_camera_image

Fetch a camera's live frame by asset ID, returned as image data in the tool result (not just a URL — the image endpoint requires an API key header that most MCP clients can't attach themselves).

get_camera_image(asset_id="30145")
describe_camera_api

Returns documentation for all search modes, camera fields, and image URL patterns. Call this first if you're unsure which tool to use.

API Reference

Every search tool queries the same spatial API that backs the Vancam.ai map:

PurposeURL
Spatial searchhttps://api.vancam.ai/cameras/cameras
Live imagehttps://api.vancam.ai/api?asset_id={id}

Each camera includes asset_id, latitude, longitude, street_address, direction, camera_class (open/premium), level1/level2/level3 (country/state/city), distance_meters (radius/nearest searches), route_fraction (route search), and image_url/image_urls.

Full schema: openapi.yaml.

Environment overrides: VANCAM_API_KEY, VANCAM_CAMERAS_SEARCH_URL, VANCAM_API_IMAGE_URL

Project Structure

vancam-mcp/

├── vancam_mcp/ │ ├── server.py # MCP server — registers the tools above │ └── camera_api.py # api.vancam.ai client ├── openapi.yaml # API specification ├── pyproject.toml # Package metadata (PyPI: vancam-mcp) ├── requirements.txt # Python dependencies └── .mcp.json # Example MCP client config

Related Projects

Contributing

Contributions are welcome — feel free to open an issue or submit a pull request.

License

MIT — see LICENSE.

Ask PopNx