# Video Frames (pypi · mcp-video-frames)

MCP server that lets image-only models look at video: timecoded frames, measurable properties.

- Trust score: 89/100 (high trust)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `mcp-video-frames`: 89/100 (this document), [markdown](https://verifymcp.io/servers/azzy-h-mcp-video-frames/mcp-video-frames.md), [page](https://verifymcp.io/servers/azzy-h-mcp-video-frames/mcp-video-frames)

## Channel facts

- Registry: `pypi`
- Package: `mcp-video-frames`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Azzy-H/mcp-video-frames).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 37 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 531 tokens (~265/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Video Frames MCP server?

Video Frames runs locally as a PyPI package, launched with uvx mcp-video-frames. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add azzy-h-mcp-video-frames -- uvx mcp-video-frames
```

### Cursor

```json
{
  "mcpServers": {
    "azzy-h-mcp-video-frames": {
      "command": "uvx",
      "args": [
        "mcp-video-frames"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "azzy-h-mcp-video-frames": {
      "command": "uvx",
      "args": [
        "mcp-video-frames"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add azzy-h-mcp-video-frames -- uvx mcp-video-frames
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "azzy-h-mcp-video-frames": {
      "type": "local",
      "command": [
        "uvx",
        "mcp-video-frames"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add azzy-h-mcp-video-frames --command uvx --arg mcp-video-frames
```

### Hermes

```yaml
mcp_servers:
  azzy-h-mcp-video-frames:
    command: "uvx"
    args: ["mcp-video-frames"]
```

### Netclaw

```json
{
  "McpServers": {
    "azzy-h-mcp-video-frames": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcp-video-frames"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add azzy-h-mcp-video-frames -t stdio -c uvx -a mcp-video-frames
```

### Other

```json
{
  "mcpServers": {
    "azzy-h-mcp-video-frames": {
      "command": "uvx",
      "args": [
        "mcp-video-frames"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 89, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 74, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-28 (score 89, 0)

- [security] Stability: 0.97 → pass

### 2026-10-27 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 86, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 85, +16)

- [security improvement] Malware scan: unverified → pass

## MCP tools (2)

### `view_frames` (~270 tokens)

Sample a video and return frames as images, each preceded by its timecode — the only thing tying an image to a moment. Set start == end to look at a single moment (returns a lossless PNG); the interval is ignored in that case. Range requests default to jpeg, which is about an order of magnitude smaller and fits far more frames in the same budget. Frames are cached by absolute timestamp, so overlapping ranges reuse work. max_frames defaults to 12; raising it up to the image limit trades away detail — lower max_edge or use format="jpeg" to afford more frames. All of these limits are set by whoever deployed this server, not by you. Server limits for this deployment: at most 20 images per call, each at most 10 MB, 40 MB per result. Frames are never silently dropped or resampled, so the interval you ask for is the interval you get. Requests past a limit fail with the numbers and concrete alternatives — the server never truncates a range or coarsens your interval.

Input parameters:

- `end`
- `format`
- `interval` (number)
- `max_edge` (integer)
- `max_frames`
- `quality` (integer)
- `start` (number)
- `video` (string, required)

Output parameters:

- `result` (array)

### `video_info` (~148 tokens)

Metadata for a video. detail="basic" reads container headers only and returns immediately. detail="full" additionally scans the whole file for scene cuts, silence intervals and EBU R128 loudness; that scan is exhaustive and therefore slow on long files, but it is cached and reused. Use force=true to recompute. This tool returns no images, so the image limits do not apply to it, but your client's per-call time limit does: a full scan of a long video takes time proportional to its length, and may exceed the limit. Raise that limit if your client allows it.

Input parameters:

- `detail` (string)
- `force` (boolean)
- `video` (string, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/azzy-h-mcp-video-frames/mcp-video-frames#diagnostics

## Score history

- 2026-11-05: 89
- 2026-11-04: 74
- 2026-11-03: 74
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 74
- 2026-10-28: 89
- 2026-10-27: 89
- 2026-10-26: 88
- 2026-10-25: 88
- 2026-10-24: 87
- 2026-10-23: 87
- 2026-10-22: 86
- 2026-10-21: 86
- 2026-10-20: 85
- 2026-10-19: 85
- 2026-10-18: 85
- 2026-10-17: 69
- 2026-10-16: 84
- 2026-10-15: 68
- 2026-10-14: 83
- 2026-10-13: 67
- 2026-10-12: 82
- 2026-10-08: 65
- 2026-10-06: 64
- 2026-10-04: 60
- 2026-10-03: 60
- 2026-10-02: 60

## Common questions

### What is the Video Frames MCP server?

Video Frames is an MCP server listed in the public MCP registry as io.github.Azzy-H/mcp-video-frames. MCP server that lets image-only models look at video: timecoded frames, measurable properties. This page covers its PyPI package (mcp-video-frames).

### Is the Video Frames MCP server safe to use?

Video Frames scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Video Frames MCP server expose?

Video Frames exposes 2 tools: view_frames, video_info. Their descriptions and schemas cost roughly 418 tokens of context every time the server is loaded.

### Is the Video Frames MCP server still maintained?

Video Frames 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 Video Frames MCP server under?

Video Frames declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/mcp-video-frames/
- Socket report: https://socket.dev/pypi/package/mcp-video-frames
- Repository: https://github.com/Azzy-H/mcp-video-frames
- Changelog RSS feed: https://verifymcp.io/servers/azzy-h-mcp-video-frames/mcp-video-frames.xml
- Changelog JSON feed: https://verifymcp.io/servers/azzy-h-mcp-video-frames/mcp-video-frames.json
- HTML version of this page: https://verifymcp.io/servers/azzy-h-mcp-video-frames/mcp-video-frames