Mmcp.market

Open Eagle Eye MCP server

by stuchapin909·io.github.stuchapin909/open-eagle-eye·v8.0.0·4 stars
No reviews yet

Live snapshots from ~29,000 public cameras across 11 countries — traffic, weather, webcams

B74/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B74/100

full report

Adoption
Growing

4 stars64 downloads/wk

Reviews

Write one

Nobody has reviewed Open Eagle Eye yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Open Eagle Eye tools (13, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • add_local_camera

    Add a camera to your local collection. Local cameras persist in ~/.openeagleeye/local-cameras.json and survive restarts and registry updates. They appear in list_cameras and search_cameras with source 'local'. Share upstream anytime with submit_local.

  • check_config

    Show API key configuration status. Lists all cameras in the registry that require authentication, the provider name, whether a key is configured in ~/.openeagleeye/config.json, and the signup URL for each. Use when a snapshot fails with an API key error to see which keys are missing.

  • explore_cameras

    Get random cameras from the registry for discovery. Returns a surprise selection. Filter by city, country, or category to narrow the pool, or leave empty for a truly random pick.

  • get_camera_info

    Look up camera metadata by ID. Returns full details for a single camera without fetching a snapshot. Use this to check if an ID is valid or to get current metadata for a known camera.

  • get_snapshot

    Fetch a live image from a camera. Downloads the image to disk and returns the file path. Works on both upstream registry cameras and locally-added cameras. Use list_cameras or search_cameras first to find IDs.

  • get_snapshots

    Fetch live images from multiple cameras in one call. Returns all snapshot file paths. Use to compare several cameras at once or to monitor a set of favorites. Max 5 cameras per call.

  • list_cameras

    Browse the camera registry. Returns cameras with id, name, city, country, location, category, coordinates, and source (upstream or local). Supports filtering by city, country, location, and category. Use limit/offset for pagination — the full registry is large.

  • list_local

    Show your locally-added cameras. These persist in ~/.openeagleeye/local-cameras.json and survive restarts and registry updates. They appear in list_cameras and search_cameras with source 'local'. Returns camera IDs, names, URLs, coordinates, and auth requirements.

  • nearby_cameras

    Find cameras within a geographic radius. Returns cameras sorted by distance from the given point. Use for spatial queries like 'webcams near Times Square' or 'cameras within 10km of the Opera House'.

  • remove_localwrite action

    Delete a locally-added camera by ID. Removes it from ~/.openeagleeye/local-cameras.json and the in-memory merged view. The camera is also auto-removed from the merged list. Use after sharing upstream via submit_local, or when a URL stops working.

  • report_camera

    Report a broken or low-quality camera. Files a GitHub issue with a snapshot showing the current state, and saves the report locally. If the camera is local with a broken link, it is automatically removed. Requires 'gh' CLI for GitHub issue creation.

  • search_cameras

    Search cameras by text. Matches against name, city, country, location, and category. Use when looking for cameras in a specific place or of a specific type.

  • submit_localwrite action

    Share your locally-added cameras with the upstream Open Eagle Eye registry by filing a GitHub issue. Validates each camera URL, checks for duplicates, and embeds a snapshot preview. Requires the 'gh' CLI installed and authenticated (gh auth login). Your local cameras are not removed — use remove_local after they are accepted.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

1 high
  • Code scan6 source files scanned13/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highShell command built from a string (injection risk)exec.shell-concat
    src/github.js: …dy, 'utf8'); try { const result = execSync( `gh issue create --repo ${GITHUB_REPO} --title ${JSON.stringify(title)} --body-file ${JSON.stringify(tmpFile)} --label ${JSON.stringify(label)}`, { encodin…
Overall 74/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

Install Open Eagle Eye in Claude Code, Cursor or VS Code

Runs npx -y openeagleeye on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add open-eagle-eye -- npx -y openeagleeye
Add to Cursor

What the publisher says

From the Open Eagle Eye repository's README, as published. We do not edit it. Read it on GitHub

Open Eagle Eye

MCP server that gives AI agents instant access to public camera feeds worldwide. One HTTP GET, sub-second captures, no browser automation, no stream decoding.

Why

Most camera APIs require authentication, serve video streams, or hide images behind JavaScript rendering. Open Eagle Eye only indexes cameras that return a JPEG or PNG on a plain HTTP GET — the simplest possible integration. Agents don't need to render pages or decode video. They just fetch an image.

The registry is self-healing. A GitHub Action runs nightly, checks every camera, retries failures before removing them, and uses vision AI to catch cameras that return error pages instead of live feeds. Dead cameras get flagged automatically.

Quick start

{
  "mcpServers": {
    "openeagleeye": {
      "command": "npx",
      "args": ["-y", "openeagleeye"]
    }
  }
}

Or install globally:

npm install -g openeagleeye
openeagleeye

On first run, the server fetches the latest camera registry from GitHub and caches it locally in ~/.openeagleeye/. Subsequent starts refresh the cache automatically.

How it works

A valid camera URL is any endpoint that returns a JPEG or PNG on a plain HTTP GET. Most city traffic cameras, weather stations, and park cams expose exactly this. The server fetches the image, saves it to disk, and returns the file path.

MCP Tools

Upstream vs local cameras

The registry has two layers:

  • Upstream — the global registry fetched from GitHub on every server start. These are the ~32,000 validated public cameras.
  • Local — cameras you add yourself via addlocalcamera. They persist in ~/.openeagleeye/local-cameras.json, survive restarts, and appear in listcameras/searchcameras with source: "local". Share them upstream anytime with submit_local.

Filtering

Every camera has a city field. Use list_cameras with city: "Sydney" to get a short, focused list instead of dumping all cameras into context.

Output format

Every tool returns structured JSON. Snapshots save to disk and return the file path — the MCP server runs as a local subprocess, so the agent has filesystem access.

Snapshot response:

{
  "success": true,
  "file_path": "/home/user/.openeagleeye/snapshots/a1b2c3d4e5f6a7b8.jpg",
  "size_bytes": 14579,
  "content_type": "image/jpeg",
  "camera": {
    "id": "nyc-bb-21-north-rdwy-at-above-south-st",
    "name": "BB-21 North Rdwy @ Above South St",
    "city": "New York",
    "location": "Manhattan, New York, USA",
    "coordinates": { "lat": 40.708, "lng": -73.999 }
  }
}

Registry

~32,000 cameras across eleven countries (32,096 verified):

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Open Eagle Eye: common questions

Is Open Eagle Eye MCP server safe?
Mostly: it is graded B (74/100). Read the Open Eagle Eye safety report
How do I install Open Eagle Eye?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Open Eagle Eye need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Open Eagle Eye maintained?
The last commit was in the last day (2026-09-27). The latest release is v8.0.0.
What can I use instead of Open Eagle Eye?
Servers from other publishers that do the same job: Japan Seasons MCP server, Singapore MCP by Olano MCP server and Weather Markets Edge Desk MCP server. Compare all Open Eagle Eye alternatives.

Alternatives to Open Eagle Eye

Same job from other publishers: the closest match first, then the best rated.

All Open Eagle Eye alternatives →
  • Japan Seasons
    Live Japan seasonal travel MCP: sakura, autumn leaves, flowers, festivals, fruit farms, weather.
    A
  • Singapore MCP by Olano
    Singapore public data, transport, rail, property, business, economy, weather, and analytics.
    B
  • Weather Markets Edge Desk
    Kalshi weather markets: live daily-high temperature edges, plus EV, Kelly and base-rate tools.
    B
  • Weather Data MCP Server
    17 weather tools, no API keys: forecasts, alerts, air quality, marine, radar, lightning, wildfires
    A
  • Variflight
    VariFlight's official MCP server provides tools to query flight, weather, comfort, and fare data.
    A

More from stuchapin909 →