io.github.vishalguptax/media-context-mcp
NPM · MEDIA-CONTEXT-MCP
Local MCP server to analyze video, audio & images: frames, transcripts, on-screen text.
Available components
Last scanned (9 hours ago)
Scores higher than 92% of npm servers
Category Design and Media
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to vishalguptax/media-context-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 135 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 888 tokens (~444/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 +1
- Stability: 0.97 → pass security
- 27 Oct 26 −1
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.97 functional
- 26 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
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 6 Nov 2026 · Analysed npm/media-context-mcp@0.1.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | vishalguptax/media-context-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/vishalguptax/media-context-mcp/.github/workflows/publish.yml@refs/tags/v0.1.4 |
| Rekor log index | 1932535498 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b6dbcb014b13ea3e7b5783bc24812fb8bf6d75295acd3e43a0a24bedf5eb97b4c19ed5d8c3d379f2bbffdc0239c38d94ba2d61b76ecfbd5e747984968 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
analyze_media Analyze a video, audio, or image file or URL ~840
Turn a local media file or URL (video, audio, or image) into compact context a model can read — fully local, no paid APIs. Video: montage frames (mode 'sheet', cheapest default), individual stills ('frames'), or scene changes ('scenes'); add transcript and/or ocr. Audio: speech transcript. Image: the picture plus optional OCR. For app/screen recordings use detail:'high' + ocr:true. To catch a transient UI glitch (a flicker/jump lasting <1s), use mode:'filmstrip' with a narrow startSec/endSec window, a high fps (10–15), and a crop around the affected control — it stacks dense frames so you can spot a frame whose value disagrees with the visual. Use the cheap default for everything else. Pass context to frame the analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| context | string | – | Optional note about the video to frame the analysis, e.g. 'signup flow, focus on the validation error'. |
| crop | object | – | Rectangle to crop before sampling — zoom into a UI region for sharper frames/OCR. Pixels, or fractions 0–1 of the frame (e.g. {x:0,y:0.7,width:1,height:0.3} = bottom 30%). |
| detail | string | – | high = readable stills for screen recordings (frames + large scale + png); low = cheap montage. Overrides only the fields you leave unset. |
| detectJumps | boolean | – | Track the on-screen number (e.g. a slider %) across frames and report non-monotonic 'jump-back' glitches with timestamps. Pair with a crop around the value and a narrow window for best results. |
| endSec | number | – | Window end in seconds. |
| format | string | – | Image encoding. webp = smallest/fewest tokens (default); png = lossless for crisp text. |
| fps | number | – | Explicit sampling rate (frames/sec); overrides the auto rate for sheet/frames/filmstrip. Use a high value (e.g. 10–15) with filmstrip to catch sub-second glitches. |
| grid | integer | – | Tiles per row/column for sheet/scenes modes (grid x grid). |
| maxDurationSec | number | – | Reject URL downloads longer than this many seconds. |
| maxFileSizeMb | number | – | Abort a URL download once it exceeds this size in MB. |
| maxFrames | integer | – | Upper bound on sampled frames across the whole window. |
| mode | string | – | sheet = montage grids (cheapest, default); frames = individual stills; scenes = only scene-change montages; filmstrip = dense near-native-fps vertical strip for catching transient UI glitches (pair w… |
| ocr | boolean | – | Extract on-screen text via OCR — ideal for app/screen recordings. Implies detail:high unless set. |
| ocrLang | string | – | Tesseract language code(s) for OCR, e.g. 'eng' or 'eng+deu'. |
| ocrMaxFrames | integer | – | Frames to OCR (sampled at full resolution, independent of the display images). |
| ocrPsm | integer | – | Tesseract page-segmentation mode. 3 = auto (default), 6 = uniform block, 11 = sparse/scattered UI labels. |
| scale | integer | – | Width in px of each frame before tiling. Lower = fewer tokens. |
| sceneThreshold | number | – | Scene-change sensitivity for 'scenes' mode (higher = fewer cuts). |
| source | string | yes | Local media file path (video, audio, or image) OR an http(s) URL. |
| startSec | number | – | Window start in seconds. |
| stripRows | integer | – | Tiles stacked per image in 'filmstrip' mode. |
| transcript | boolean | – | Also run local Whisper to produce a speech transcript. |
| whisperModel | string | – | Whisper model name (tiny, base, small, medium, large). |
No output schema declared.
No examples provided.
check_media_deps Check media tool dependencies ~48
Report which external binaries (ffmpeg, ffprobe, yt-dlp, whisper, tesseract) are available. Call this first if analyze_media fails with a missing-binary error.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.vishalguptax/media-context-mcp server?
io.github.vishalguptax/media-context-mcp runs locally as an npm package, launched with npx -y media-context-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · media-context-mcp
claude mcp add vishalguptax-media-context-mcp -- npx -y media-context-mcp
What is the io.github.vishalguptax/media-context-mcp server?
io.github.vishalguptax/media-context-mcp is listed in the public MCP registry as io.github.vishalguptax/media-context-mcp. Local MCP server to analyze video, audio & images: frames, transcripts, on-screen text. This page covers its npm package (media-context-mcp).
Is the io.github.vishalguptax/media-context-mcp server safe to use?
io.github.vishalguptax/media-context-mcp scores 88 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. It declares no install or post-install scripts. 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 io.github.vishalguptax/media-context-mcp server expose?
io.github.vishalguptax/media-context-mcp exposes 2 tools: check_media_deps, analyze_media. Their descriptions and schemas cost roughly 888 tokens of context every time the server is loaded.
Is the io.github.vishalguptax/media-context-mcp server still maintained?
io.github.vishalguptax/media-context-mcp is still listed as active in the MCP registry. We last reached this channel on 6 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 io.github.vishalguptax/media-context-mcp server under?
io.github.vishalguptax/media-context-mcp declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.vishalguptax/media-context-mcp server?
VerifyMCP ran 16 checks on io.github.vishalguptax/media-context-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.