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.

io.github.Shoberman2/clipswarm

NPM · CLIPSWARM

Clip YouTube videos and livestreams into viral 9:16 shorts, in parallel, for AI agents

Available components

60 Trust /100

Last scanned (6 hours ago)

Scores higher than 36% of npm servers

Category Design and Media

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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 32 of 108 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
Schema Quality & AI Usability66
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1267 tokens (~105/item across 12 items; 12 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage86
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 59% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_watch" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 12 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 14 Oct 26 +27
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • First check of Schema quality: fail functional
    • First check of Tool coverage: 59 functional
    • First check of Destructive annotations: 0 functional
    • First check of Schema quality: pass functional
    • First check of Schema quality: good functional
  • 12 Oct 26 −5
    • Source repository: pass → fail ▼ security
  • 11 Oct 26 38

    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 17 Oct 2026 · Analysed npm/clipswarm@0.1.0

Provenance No attestation

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

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 108 packages
Packages resolved 108
Stale 32
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 12 exposed · ~1,267 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
create_clips ~166

Cut one or more clips from YouTube videos (including streams that are live right now) in parallel. Only the requested sections are downloaded. Jobs can span different videos. Returns a result per job; failures don't abort the batch. Live results include the wall-clock range covered. Viral clips take ~15-60s each; if the batch isn't done within waitSec, you get finished results plus a jobId: call get_clips with it until pending is 0.

NameTypeReqDescription
clipsarrayyes–
outDirstring–Output directory, default /workdir/clips
waitSecnumber–Seconds to wait before returning, default 40. If clips are still rendering, the response includes a jobId; collect the rest with get_clips.

No output schema declared.

No examples provided.

create_watch ~341

Watch a category: on a schedule, search YouTube for new videos about it and auto-clip the best moments into viral shorts (moments and hooks picked by the local Claude Code CLI if installed, else YouTube's most-replayed peaks, else a transcript heuristic). Anything it can't clip (and live streams, if enabled) goes to the inbox for you. Replaces a watch with the same id. Runs via the background scheduler (see watch_scheduler).

NameTypeReqDescription
autoClipboolean–Default true. false = only collect videos into the inbox
clipSecondsnumber–Target clip length, default 45
clipsPerVideonumber–Default 2
everystringyesHow often to check: "30m", "6h", "1d" (min 5m)
idstring–Short name; defaults to a slug of the query
includeLiveboolean–Also surface streams that are live right now
maxAgeHoursnumber–Only videos uploaded within this many hours (default 72)
maxDurationSecnumber–Default 14400
maxVideosPerRunnumber–Default 3
minDurationSecnumber–Default 120 (skips Shorts)
minViewsnumber––
outDirstring–Default ~/clipswarm/<id>
pickerstring–How moments are chosen. Default "auto"
querystringyesThe category, phrased like a YouTube search, e.g. "netflix stock analysis"
stylestring––

No output schema declared.

No examples provided.

delete_watch ~21

Stop and remove a watch.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

get_clips ~84

Get results of a create_clips batch that was still running (create_clips returns a jobId when it doesn't finish within waitSec). Waits up to waitSec for more clips to finish. Call repeatedly until pending is 0.

NameTypeReqDescription
jobIdstringyes–
waitSecnumber–Seconds to wait for completion before returning, default 40

No output schema declared.

No examples provided.

get_inbox ~105

Videos found by watches. "clipped" = auto-clipped (paths in clips; note says how moments were picked). "needs_agent" = couldn't be clipped automatically: read the transcript, pick moments, call create_clips, then mark it "done". "live" = streaming now. "failed" = see note.

NameTypeReqDescription
limitnumber–Most recent N, default 30
statusstring––
watchIdstring––

No output schema declared.

No examples provided.

get_transcript ~222

Get the timestamped transcript of a YouTube video. Optionally limit to a time window to keep output small. Read it to decide which moments to clip.

NameTypeReqDescription
fromstring|number–Seconds (83) or "1:23" / "1:02:03.5". Negative = from the end ("-0:30"). For LIVE streams: "now", negative offsets from the live edge (-90), or ISO time ("2026-10-08T00:40:00Z"); roughly the last hou…
langstring–Caption language code, default "en"
tostring|number–Seconds (83) or "1:23" / "1:02:03.5". Negative = from the end ("-0:30"). For LIVE streams: "now", negative offsets from the live edge (-90), or ISO time ("2026-10-08T00:40:00Z"); roughly the last hou…
urlstringyes–

No output schema declared.

No examples provided.

get_video_info ~60

Get a YouTube video's title, channel, duration, chapters and liveStatus ("is_live" means it's streaming now: clip it with times relative to "now"). Use chapters to find natural clip boundaries.

NameTypeReqDescription
urlstringyesYouTube URL

No output schema declared.

No examples provided.

list_watches ~24

List watches with their schedule, last and next run, plus scheduler status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

run_watch ~45

Run a watch right now instead of waiting for its schedule. Runs in the background (searching and rendering takes minutes); check get_inbox afterwards.

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

search_transcript ~93

Find where a phrase is said in a YouTube video. Returns time windows with surrounding text, ready to pass to create_clips.

NameTypeReqDescription
contextSecnumber–Seconds of padding around each hit, default 15
langstring––
limitnumber––
querystringyesWords to find (all must appear in the caption line)
urlstringyes–

No output schema declared.

No examples provided.

update_inbox_item ~49

Mark an inbox video as handled ("done") or not worth clipping ("dismissed").

NameTypeReqDescription
notestring––
statusstringyes–
videoIdstringyes–

No output schema declared.

No examples provided.

watch_scheduler ~57

Status, install or uninstall the background job that runs due watches every 5 minutes (launchd on macOS; returns a crontab line elsewhere). Install only when the user wants watches to run automatically.

NameTypeReqDescription
actionstringyes–

No output schema declared.

No examples provided.

Install

How do I install the io.github.Shoberman2/clipswarm MCP server?

io.github.Shoberman2/clipswarm runs locally as an npm package, launched with npx -y clipswarm. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · clipswarm

# add to Claude Code
claude mcp add shoberman2-clipswarm -- npx -y clipswarm
Common questions

What is the io.github.Shoberman2/clipswarm MCP server?

io.github.Shoberman2/clipswarm is an MCP server listed in the public MCP registry as io.github.Shoberman2/clipswarm. Clip YouTube videos and livestreams into viral 9:16 shorts, in parallel, for AI agents. This page covers its npm package (clipswarm).

Is the io.github.Shoberman2/clipswarm MCP server safe to use?

io.github.Shoberman2/clipswarm scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. 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.Shoberman2/clipswarm MCP server expose?

io.github.Shoberman2/clipswarm exposes 12 tools: get_video_info, get_transcript, search_transcript, create_clips, get_clips, and 7 more. Their descriptions and schemas cost roughly 1,267 tokens of context every time the server is loaded.

Is the io.github.Shoberman2/clipswarm MCP server still maintained?

io.github.Shoberman2/clipswarm is still listed as active in the MCP registry. We last reached this channel on 17 October 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.Shoberman2/clipswarm MCP server under?

io.github.Shoberman2/clipswarm declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.