Video Analyzer (guimatheus92) MCP Server

mcp-video-analyzer npm v0.7.1

Published by guimatheus92 — no publish provenance and no vendor-owned scope, so the publisher could not be verified. The repository link below is self-declared.

Trust grade
A
100/100
Last scanned
Trust
A · 100/100
How safe the published surface and source look. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
A Why this grade

Started at 100 and nothing was deducted: the deterministic scan raised no scored threat in the published surface it inspected. Capability observations and advisory notes are recorded but never lower the score.

Findings 6

high Shell/command execution in server code (dist/processors/audio-transcriber.js)MTC-SRC-002

In the server's implementation (`dist/processors/audio-transcriber.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/processors/audio-transcriber.js

high Shell/command execution in server code (dist/processors/embedded-subtitles.js)MTC-SRC-002

In the server's implementation (`dist/processors/embedded-subtitles.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/processors/embedded-subtitles.js

high Shell/command execution in server code (dist/processors/frame-extractor.js)MTC-SRC-002

In the server's implementation (`dist/processors/frame-extractor.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/processors/frame-extractor.js

high Shell/command execution in server code (dist/utils/ytdlp.js)MTC-SRC-002

In the server's implementation (`dist/utils/ytdlp.js:1`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: child_process

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/utils/ytdlp.js

medium Hardcoded egress to an external endpoint (dist/adapters/loom.adapter.js)MTC-SRC-003

In the server's implementation (`dist/adapters/loom.adapter.js:216`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch(`https://www.loom.com/api/campaigns/sessions/${videoId}/transcoded-url`

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/adapters/loom.adapter.js

medium Hardcoded egress to an external endpoint (dist/processors/audio-transcriber.js)MTC-SRC-003

In the server's implementation (`dist/processors/audio-transcriber.js:298`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: fetch('https://api.openai.com/v1/audio/transcriptions'

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/processors/audio-transcriber.js

What this scan could not see

Versions

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.7.1 latest A 100/100 6 1.5.0 2026-07-22

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 100/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-video-analyzer/badge.svg)](https://mcptrustchecker.com/registry/mcp-video-analyzer)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-video-analyzer"><img src="https://mcptrustchecker.com/registry/mcp-video-analyzer/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-video-analyzer/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan mcp-video-analyzer --online

Use the free API → How scoring works

Other implementations of Video Analyzer 1

Independent packages implementing the same tool, scanned with the same engine. Compare all 2 side by side →

More in Design & Media