Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

IP cameras (ONVIF/RTSP)

PYPI · IPCAM-MCP

MCP server for local IP cameras (ONVIF/RTSP): snapshots, recordings, pan/tilt, presets

Available components

53 Trust /100

Last scanned (1 hour ago)

Scores higher than 56% of PyPI servers

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs uv_build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 3 of 53 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1552 tokens (~77/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
  • Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 −14
    • Malware scan: pass → unverified ▼ security
  • 4 Nov 26 +17
    • Malware scan: unverified → pass ▲ security
    • Stability: unverified → 0.03 ▲ functional
    • Destructive annotations: All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • Package version: 0.3.2 → 0.4.0 functional
  • 3 Nov 26 50

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/ipcam-mcp@0.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted uv_build

Background: Why install scripts are a supply-chain risk →

Dependencies 53 packages
Packages resolved 53
Stale 2
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~1,482 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_camera ~203

Add an ONVIF/RTSP IP camera. Ask the user for the camera's IP address (from its app or router) and pick a short name such as "garage". Credentials are never passed as arguments: by default the user is shown a login form; with credentials_via="file" a secrets file is created for the user to fill in, then call add_camera again with credentials_via="file". Use credentials_via="file" when the user is on Remote Control or a phone and the form does not appear. onvif_port: only if the camera uses a non-standard ONVIF port (80 and 2020 are tried). scene: the place it watches, if not its own name (several cameras may share a scene).

NameTypeReqDescription
credentials_viastring––
hoststringyes–
namestringyes–
onvif_port–––
scene–––
NameTypeReqDescription
resultstringyes–

No examples provided.

camera_compare ~74

Take a new snapshot and report what changed compared with this camera's previous snapshot in its current scene, or with a named baseline saved in that scene. Use the reported cells as `region` in camera_snapshot to look closer.

NameTypeReqDescription
baseline–––
camerastringyes–
qualitystring––

No output schema declared.

No examples provided.

camera_record ~103

Record a video clip (1-60 s) from a camera to an mp4 file on the local machine. Returns the file path and size; the video itself is not returned, so take a snapshot if you need to see the scene. quality: "high" = main stream (1080p); "low" = sub stream (smaller file).

NameTypeReqDescription
camerastringyes–
qualitystring––
secondsinteger––
NameTypeReqDescription
resultstringyes–

No examples provided.

camera_save_baseline ~53

Take a snapshot and keep it as a named reference for camera_compare (e.g. 'door-closed').

NameTypeReqDescription
camerastringyes–
namestringyes–
qualitystring––

No output schema declared.

No examples provided.

camera_snapshot ~198

Take a still picture from a camera. Returns the image (downscaled to at most 1280 px wide) and the path of the full-size JPEG saved on the local machine. quality: "high" = main stream (1080p); "low" = sub stream (smaller, quicker). crop: [x, y, w, h] as fractions of the frame (0-1) to see a detail at full resolution. region: a named ninth of the frame instead of crop (not both). from_path: reuse an earlier full-size snapshot (e.g. the one just viewed, or one from scene_timeline) instead of taking a new one; combine with crop/region to zoom into it. The camera is not contacted, and camera may be omitted.

NameTypeReqDescription
camera–––
crop–––
from_path–––
qualitystring––
region–––

No output schema declared.

No examples provided.

delete_camera ~78

Delete a camera and all its snapshots, recordings and baselines, or the leftover files of a removed camera with that name. The user approves in a form that lists what will be deleted; you cannot approve it. Without form support nothing is deleted and the result says how to do it by hand.

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

list_cameras ~68

List configured cameras with their ids (names), uids, types and capabilities (camera, ptz). include_removed=true also lists removed cameras whose files are still on disk ("removed": true), e.g. to clean them up with delete_camera.

NameTypeReqDescription
include_removedboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

list_scenes ~41

The scenes (places watched): their configured cameras, removed cameras that were there, the time of the oldest and newest capture, and how many there are.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

ptz_goto_preset ~44

Move a pan/tilt camera to a saved preset, given by name or token.

NameTypeReqDescription
camerastringyes–
presetstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

ptz_list_presets ~35

List the saved camera positions (presets) of a pan/tilt camera.

NameTypeReqDescription
camerastringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

ptz_move ~113

Pan or tilt a camera. Directions are as seen in the camera image ("left" turns the view left). amount: "small" is a slight nudge, "medium" a noticeable turn, "large" a big sweep. Waits until the camera has stopped, then returns its pan/tilt position if the camera reports one. Take a snapshot afterwards to see the new view.

NameTypeReqDescription
amountstring––
camerastringyes–
directionstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

ptz_remove_preset ~39

Delete a saved preset by name or token. This cannot be undone.

NameTypeReqDescription
camerastringyes–
presetstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

ptz_save_preset ~52

Save the camera's current position as a preset. Refuses an existing name unless overwrite=true.

NameTypeReqDescription
camerastringyes–
namestringyes–
overwriteboolean––
NameTypeReqDescription
resultstringyes–

No examples provided.

reload_cameras ~35

Re-read cameras.toml after it was edited by hand and list the cameras, in the same format as list_cameras.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

remove_camera ~37

Remove a camera from the configuration. Never deletes snapshots or recordings (delete_camera does, after the user approves).

NameTypeReqDescription
namestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

rename_camera ~39

Change a camera's name. Its baselines, snapshots and recordings stay with it.

NameTypeReqDescription
newstringyes–
oldstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

scene_compare ~43

camera_compare for every camera in the scene, labelled with the camera's name.

NameTypeReqDescription
baseline–––
qualitystring––
scenestringyes–

No output schema declared.

No examples provided.

scene_snapshot ~39

Take a snapshot with every camera in the scene, labelled with the camera's name.

NameTypeReqDescription
qualitystring––
scenestringyes–

No output schema declared.

No examples provided.

scene_timeline ~85

The scene's snapshots, recordings and baselines, newest first, from every camera that watched it (removed ones too). start/end: YYYY-MM-DD (whole day) or an ISO datetime. Open a snapshot with camera_snapshot(from_path=...).

NameTypeReqDescription
end–––
limitinteger––
scenestringyes–
start–––
NameTypeReqDescription
resultstringyes–

No examples provided.

set_scene ~103

Move a camera to another scene (the place it watches). Its earlier snapshots stay with the earlier scene; camera_compare only compares within the current scene. If removed cameras watched that scene, the user is asked in a form whether this camera replaces one of them (it then continues that camera's compare and baselines). Call it with the camera's current scene to answer that question later.

NameTypeReqDescription
camerastringyes–
scenestringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the IP cameras (ONVIF/RTSP) MCP server?

IP cameras (ONVIF/RTSP) runs locally as a PyPI package, launched with uvx ipcam-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · ipcam-mcp

# add to Claude Code
claude mcp add aidev-iprokszin-ipcam-mcp -- uvx ipcam-mcp
Common questions

What is the IP cameras (ONVIF/RTSP) MCP server?

IP cameras (ONVIF/RTSP) is an MCP server listed in the public MCP registry as io.github.aidev-iprokszin/ipcam-mcp. MCP server for local IP cameras (ONVIF/RTSP): snapshots, recordings, pan/tilt, presets. This page covers its PyPI package (ipcam-mcp).

Is the IP cameras (ONVIF/RTSP) MCP server safe to use?

IP cameras (ONVIF/RTSP) scores 53 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the IP cameras (ONVIF/RTSP) MCP server expose?

IP cameras (ONVIF/RTSP) exposes 20 tools: list_cameras, camera_snapshot, camera_save_baseline, camera_compare, list_scenes, and 15 more. Their descriptions and schemas cost roughly 1,482 tokens of context every time the server is loaded.

Is the IP cameras (ONVIF/RTSP) MCP server still maintained?

IP cameras (ONVIF/RTSP) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the IP cameras (ONVIF/RTSP) MCP server under?

IP cameras (ONVIF/RTSP) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.