Blender integration through the Model Context Protocol
Nothing to run from here
vid2context is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
71/100
trust score
9
tools declared
local
runs on your machine
—
downloads a day
What it does
Turn any video into context for AI agents: transcripts, metadata, chapters, timestamps.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user vid2context-mcp '--' npx -y vid2context-mcp
# 2 — ask your agent for something these tools do
# list_items, export_context_pack, list_models and 6 more
vid2context costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
NIAll 82 servers
@nirholas82 servers
11 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts vid2context as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user vid2context-mcp '--' npx -y vid2context-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take GROQ_API_KEY (Optional. Groq free tier: fast Whisper speech-to-text and LLMs), GEMINI_API_KEY (Optional. Google AI Studio free tier LLMs), OPENAI_API_KEY (Optional. OpenAI, used last and only when set), OLLAMA_BASE_URL (Optional. Local Ollama server, for example http://localhost:11434/v1), LOCAL_STT_BASE_URL (Optional. Local OpenAI-compatible speech-to-text server, for example http://localhost:8000/v1) if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
9 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Expand a playlist, channel, podcast feed or page into its videos (a single video URL returns itself).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Playlist, channel, feed or page URL |
| limit | integer | no | Most items to return. Default: … |
One Markdown document for many videos (the pack format): a header per video with title, channel, URL and chapters, then each transcript in timestamped paragraphs.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| urls | array | no | Video, playlist, channel or feed URLs (lists are expanded into their videos) |
| collection | string | no | Export this saved collection (id or name) |
| maxTokens | integer | no | Token budget for the whole pack |
| limit | integer | no | Most videos taken from each playlist, channel or feed. Default: … |
The models (rungs) this server can use for speech-to-text, LLM, embedding, video and visual work, in free-first order: tier (local, free, keyless, paid), quality 1 to 5,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| kind | string | no | Only this kind of model. Default: all kinds |
The full transcript of one video or local media file, with a header (title, channel, URL, duration, how the transcript was made, chapters).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| format | string | no | Output format (see list_formats). Default: text |
| timestamps | boolean | no | Prefix lines with [m:ss] timestamps. Default: true |
| maxTokens | integer | no | — |
| cursor | string | no | Continuation cursor from a previous partial result (like "seg:412"). Use the same other arguments |
Title, channel, description, duration, publish date, chapters, tags and language for a video URL or local file, without fetching the transcript.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | yes | — |
The output formats get_transcript and get_section accept (text, json, markdown, srt, vtt, pack, ...), with what each is for.
No parameter schema on file.
Start here for any video longer than about 20 minutes. Returns the metadata and the video's chapters (or sections of about five minutes when it has none),
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | string | yes | Video URL (YouTube and more), a YouTube video id, or a local media file path |
| mode | string | no | — |
| language | string | no | Preferred transcript language (BCP-47, e.g. en, de). Default: the spoken language |
One chapter or time range of a video's transcript, with the same header as get_transcript.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | no | Start time: seconds (754), m:ss (12:34) or h:mm:ss (1:02:03). Default: the start | |
| to | no | End time (exclusive), same forms as from. Default: the end | |
| chapter | no | — | |
| format | string | no | Output format. Default: text |
| timestamps | boolean | no | Prefix lines with [m:ss] timestamps. Default: true |
Top comments of a video, with creator replies and pinned comments flagged. Useful for corrections, follow-up questions and audience consensus that the video itself lacks.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| url | yes | — | |
| limit | integer | no | Most comments to return. Default: 50 |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install vid2context or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
CTrust score 71 / 100
Release 0.1.1 · scanned 15 Nov 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score78
Client score71
Findings5 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest379f7650ce6a788918a7ee874f6c3dfbcec189ad09340fc1c62f960fd3e2ac0d
Score vectorthreat 78 → client 71
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfacenot available
Implementation sourceread
Package metadataread
Live transportnot available
No tools were enumerated, so prompt-injection, capability and toxic-flow analysis had no tool surface to inspect. To grade a package’s real runtime tools, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| No per-tool rows for this release — see the note below. | ||
can execute shell commands or code
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest379f7650ce6a7889
Scanned2026-11-15
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.1. Pin a release below and the command asks for exactly that one.
0.1.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish vid2context can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.