MCP servers › io.github.nirholas › vid2context
MCP server · registry snapshot 2026-11-19 · last tested 2026-11-19
vid2context MCP server
Registry name io.github.nirholas/vid2context
by nirholas · GitHub account (the registry's namespace rule)repository: same ownerSource ↗npm ↗Website ↗
Turn any video into context for AI agents: transcripts, metadata, chapters, timestamps. — the publisher's description
Summary
io.github.nirholas/vid2context is a remote and local MCP server listed in the official MCP registry at version 0.2.0, under the namespace of the GitHub account nirholas. Its linked repository, github.com/nirholas/vid2context, belongs to the same GitHub account.
Record checks
- met: Registry entry is active and says how to run it
- met: Source repository link opens
- met: Repository is not archived
- met: Code pushed to the repository in the 90 days before our check
- met: Repository publishes a security policy (SECURITY.md)
- met: Package names its licence with a standard (SPDX) identifier
- met: The version the registry lists can be installed and is not withdrawn
- not met: npm package carries build provenance (attestation)
- met: No known critical or high advisory in the package or its dependencies
- #7,076 of 20,610 packages by monthly downloads, tied with 18 others
- Not ranked by stars: 3 stars (ranked from 10)
From public records, not a safety rating. Each check with its reason · Is it safe to install?
Operate this server? Correct a fact · README badge · Run the checks yourself · Claim it
Key facts
- Runs
- remote and local package
- Transport
- standard input/output, streamable HTTP
- Your own values
- none declared (not a guarantee)
- Sign-in
- required
- Package
- npm · listed version current
- License
- Apache-2.0
- Dependencies
- no known high or critical advisories
- Repository
- public
- Last tested
- 2026-11-19
How a client gets in
Asks for a key or token from the publisher (no OAuth metadata published)
Read from the server's public metadata on 2026-11-19 (vid2context.com), in our read-only connection; no tool was called. It may have changed since. How it is read
Tool list
Not read: The server required a sign-in before it would list anything, and we never use a credential its operator did not give us. Its operator can test it with their own credential, on their own machine, with our self-test command (/docs/selftest). So there is no tool-list size and no result from the three APIs.
How fresh this is
- Live-tested
- attempted, see below
- Last tested
- 2026-11-19
- Latest version
- 0.2.0, published 2026-11-19 (registry, as of the 2026-11-19 snapshot)
- First listed version
- 2026-11-14 (earliest version still in the registry; older removed versions would be earlier)
- Version history
- 3 versions listed, 2026-11-14 to 2026-11-19; 3 in the 90 days before the 2026-11-19 snapshot.(versions still listed in the registry only)
Most recent 3 versions
0.2.0· 2026-11-190.1.1· 2026-11-140.1.0· 2026-11-14
- Registry data
- snapshot 2026-11-19
- Package and repository
- checked 2026-11-19
- Engine
- mcp-runtime-engine@0.1.0 · sdk@1.32.0
Dead or stale signals
None found in the records we hold
Looked for and not found: deprecated in the registry; listed version cannot be installed or is withdrawn; repository link does not open; repository archived; no push in over 365 days. Each line is a dated fact from a public record. It does not say whether the server still works, and a record can change after the date shown.
Changes since the last refresh
Version 0.1.1 (published 2026-11-14) → 0.2.0 (published 2026-11-19), between the registry lists of 2026-11-18 and 2026-11-19.
The publisher’s GitHub release note for v0.2.0 (“vid2context 0.2.0”), published 2026-11-19.
Read the release note (the publisher’s text, shown as plain text, cut at 4,000 characters)
Install or update: `npx vid2context@latest` (CLI) and `npx vid2context-mcp@latest` (MCP server). Both are on npm as 0.2.0.
### Added
- Playlist view in the web app: rows show each video's title and length from the list page (new optional `VideoRef.title` and `durationSec` listing hints, read by the YouTube lister; also in `GET /items` and MCP `list_items`). Repeated entries are left out. A video waiting on a retry shows a live countdown and "Retry now", which cancels that job and starts it again. Stop and Retry now cancel the server job (`DELETE /jobs/:id`) instead of leaving it to retry for nobody.
- Job `progress` events carry `retryAt` while a failed attempt waits to be retried.
- X provider: a third lane for reading posts, x.com's GraphQL `TweetResultByRestId` with a guest token, the lane xactions runs for xactions.app/video. Tried after syndication and FxTwitter, only when `X_BEARER_TOKEN` (or `TWITTER_BEARER_TOKEN`) is set; `X_GRAPHQL_QUERY_ID` follows X when it rotates the operation id. Recorded fixtures and a gated live test.
### Fixed
- Speech-to-text decoder loops no longer cost the speech under them. A 9-minute interview on the keyless OVH lane came back with "issuance of" repeated 39 times over 45 seconds of real speech: the long-audio path never ran the repetition guard, and the guard alone would only have cut the junk back. Now every piece is checked; a looped piece is sent to the other rungs, then split in two at new cut points (once per piece), and only when every retry still loops is it cut back, with a `loop-kept` attempt saying the speech is missing. The single-request path re-transcribes a looped answer in two pieces the same way, and the stitched long-audio transcript gets the repetition guard too. See docs/long-audio.md, "Decoder loops".
- The keyless OVH rung declares its 60 s audio cap (`maxDurationSec`, now a field of `SttRung`), so long audio is split before the first upload instead of after refused ones, and audio of known length over every rung's cap goes straight to the long-audio path.
- Long-audio attempts no longer list every cooldown skip while a chunk waits out rate limits: the 429s stay, and one `rate-limit-wait` attempt gives the total wait.
- X links work on Cloudflare Workers (the public vid2context.com instance). Workers' fetch sends no user-agent, and without one X's syndication endpoint answers 400 and FxTwitter 401, so every X link failed there while Node, which always sends one, worked. The X provider now names its client on every lane.
- Long X videos can be transcribed on the keyless lane. X audio is m4a, which no built-in splitter cuts, and the ffmpeg splitter in `@vid2context/ffmpeg` was never passed to the pipeline, so anything over 60 s ended in "no splitter for audio/mp4". `Registry` now carries optional `splitters`, tried after the built-in MP3 and WAV ones, and the Node registry adds `ffmpeg-silence`, so the CLI, HTTP server and MCP server all get it.
- Long audio no longer stalls behind a rung with a bad key. A rejected key puts a rung on a 10-minute cooldown, and the chunk wait loop counted those cooldowns as rate limits, so a chunk waited its whole 10-minute budget and then failed. Cooldowns now remember their cause (`cooldownReason`), and only rate limits, 5xx errors and timeouts are waited for. A chunk planned for keyed rungs that all failed is split again for the length cap of the rungs that are left (OVH's 60 s).
- A rung skipped up front for a declared limit now counts as a too-large refusal, so audio still reaches the long-audio path when the only other rungs fail on auth (seen live: a bad Cloudflare key plus OVH skipped for length ended in "every rung failed").
- Web playlist view: the progress line no longer counts failures as done ("1 of 3 done, 1 failed"), and long status messages wrap instead of being cut off.
- The no-transcript hint follows what was tried: it suggests installing yt-dlp only when no source could download the audio, and otherwise says whethSource: the official MCP Registry list on 2026-11-18 and on 2026-11-19; release notes from the GitHub Releases API, checked 2026-11-19.
What it is
How do I add it to my client?
Config from the registry entry
From the npm package vid2context-mcp
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below. The command runs the publisher’s code on your machine.
Claude Desktop · claude_desktop_config.json (Settings → Developer → Edit Config)
{
"mcpServers": {
"vid2context": {
"command": "npx",
"args": [
"-y",
"vid2context-mcp@0.2.0"
]
}
}
}Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vid2context": {
"command": "npx",
"args": [
"-y",
"vid2context-mcp@0.2.0"
]
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"vid2context": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"vid2context-mcp@0.2.0"
]
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"vid2context","type":"stdio","command":"npx","args":["-y","vid2context-mcp@0.2.0"]}'Claude Code
claude mcp add --transport stdio vid2context -- npx -y vid2context-mcp@0.2.0
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"vid2context": {
"command": "npx",
"args": [
"-y",
"vid2context-mcp@0.2.0"
],
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"vid2context": {
"command": "npx",
"args": [
"-y",
"vid2context-mcp@0.2.0"
]
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.vid2context] command = "npx" args = ["-y", "vid2context-mcp@0.2.0"]
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"vid2context": {
"command": "npx",
"args": [
"-y",
"vid2context-mcp@0.2.0"
]
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 -- npx -y vid2context-mcp@0.2.0
- Optional settings the entry also lists (left out above): GROQ_API_KEY, GEMINI_API_KEY, OPENAI_API_KEY, OLLAMA_BASE_URL, LOCAL_STT_BASE_URL.
- This runs the publisher's code on your machine (npx). Read its README first.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
From the remote endpoint (Streamable HTTP)
Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.
Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste: https://vid2context.com/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
"mcpServers": {
"vid2context": {
"url": "https://vid2context.com/mcp"
}
}
}VS Code · .vscode/mcp.json
{
"servers": {
"vid2context": {
"type": "http",
"url": "https://vid2context.com/mcp"
}
}
}VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"vid2context","type":"http","url":"https://vid2context.com/mcp"}'Claude Code
claude mcp add --transport http vid2context https://vid2context.com/mcp
Cline · cline_mcp_settings.json (Cline CLI: ~/.cline/data/settings/; in the editor: MCP Servers → Configure → Configure MCP Servers)
{
"mcpServers": {
"vid2context": {
"type": "streamableHttp",
"url": "https://vid2context.com/mcp",
"disabled": false,
"autoApprove": []
}
}
}Gemini CLI · ~/.gemini/settings.json, or .gemini/settings.json in a project
{
"mcpServers": {
"vid2context": {
"httpUrl": "https://vid2context.com/mcp"
}
}
}OpenAI Codex · ~/.codex/config.toml, or .codex/config.toml in a trusted project
[mcp_servers.vid2context] url = "https://vid2context.com/mcp"
Zed · Zed settings file (command: zed: open settings file)
{
"context_servers": {
"vid2context": {
"url": "https://vid2context.com/mcp"
}
}
}Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://vid2context.com/mcp --transport http
- The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
- Zed's docs we read on 2026-10-26 describe remote servers by URL and do not name the transport.
- The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.
Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21; Cline, Gemini CLI, OpenAI Codex and Zed 2026-10-26). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.
Can it be installed, and is it up to date?
Version pin · advisories
Listed version
- Registry lists
- 0.2.0
- Latest stable
- 0.2.0
- Status
- current
- Withdrawn
- no
Source: registry.npmjs.org · 2026-11-19. About the version the registry lists; a manual install may resolve to a different one.
Dependency advisories
Counted in the full dependency tree as resolved on 2026-11-19 (npm audit; each bar counts packages with an advisory, not advisories). Bars share one scale. The package itself has no known vulnerability (OSV.dev).
Integrity, provenance, license
- Integrity
- sha512-PePelS2EnlpTxUAwf…
- Signature
- signed
- License
- Apache-2.0
Source: the package registry · 2026-11-19.
Usage
- Downloads
- 614 in the last month
Source: api.npmjs.org · 2026-11-19.
What do the published files and outside lists say?
Read as text · nothing run · no tool called
Package files
- Install-time script (npm). No install-time script in the published package.json (version 0.2.0). Source: registry.npmjs.org/vid2context-mcp/0.2.0 · read 2026-11-19.
- Operating systems and processors (npm). The npm package sets no os or cpu limit (package.json). Source: registry.npmjs.org/vid2context-mcp/0.2.0 · read 2026-11-19.
- Node.js version (npm). Needs Node 22 or later (engines.node
>=22). Source: registry.npmjs.org/vid2context-mcp/0.2.0 · read 2026-11-19. - MCP SDK in the package files. The package ships MCP SDK code inside its own files (1 file) but does not list
@modelcontextprotocol/sdkor any of the MCP SDK's split packages (core, server, client, node, express, hono, fastify, server-legacy) as a dependency, so its SDK version is fixed at build time. Bundled SDK version: not read. Source: registry.npmjs.org/vid2context-mcp/-/vid2context-mcp-0.2.0.tgz · read 2026-11-19. - Build workflow. No build provenance published for this version. Source: registry.npmjs.org/vid2context-mcp/0.2.0 · read 2026-11-19.
Registry entry
- Same package in other registry entries. No other registry entry lists this entry's npm or PyPI package at a newer version. Source: own registry snapshot · read 2026-11-19.
Outside lists
- CVE records (NVD). No CVE record in the NVD feeds we read links this server's repository. Source: read 2026-11-19. This product uses the NVD API but is not endorsed or certified by the NVD.
- GitHub advisories. No GitHub advisory names this entry's listed package. Source: read 2026-11-19. GitHub Advisory Database, CC BY 4.0
- Docker MCP catalogue. Not in the Docker MCP catalogue on 2026-11-19. Source: read 2026-11-19.
- Cline marketplace. Not in the Cline marketplace on 2026-11-19. Source: read 2026-11-19.
Own host
- security.txt. No security.txt at https://vid2context.com/.well-known/ (HTTP 404, 2026-11-19). Source: vid2context.com/.well-known/security.txt · read 2026-11-19.
- A2A agent card. No A2A agent card at https://vid2context.com/.well-known/ (HTTP 404, 2026-11-19). Source: vid2context.com/.well-known/agent-card.json · read 2026-11-19.
Read as text from published files and outside lists. Nothing was installed or run, and no tool was called. A fact, not a rating. How each fact is read
Does the registry listing match what we found?
Feature #6The registry checks an entry when it is published (each new version), and nothing re-checks it on a schedule. A difference below is about the listing, not a judgement of the publisher.
| Registry says | We found | Result | Source · date |
|---|---|---|---|
| Remote endpoint vid2context.com/mcp | Endpoint answered and asked for sign-in | matches | our test · 2026-11-19 |
| No credential declared as required | Required sign-in | differs | our test · 2026-11-19 |
| Version 0.2.0 on npm | Exists and can be installed | matches | npm · 2026-11-19 |
| Repository github.com/nirholas/vid2context | Opens publicly | matches | api.github.com · 2026-11-19 |
Who made it?
Feature #7 · lineage
Facts about the publisher. We do not turn them into a trust score.
- Namespace
- io.github.nirholas · 81 servers
- GitHub owner
- a personal account (nirholas)
- Build record
- signed
- Repository
- github.com/nirholas/vid2context
- Stars
- 3
- Repository age
- 0–30 days
- Last push
- 0–30 days ago
- Archived
- no
- Security policy
- SECURITY.md
Source: the registry entry and api.github.com · 2026-11-19; security policy read from GitHub · 2026-11-15.
Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.
Choosing
Record checks
Public records · not a safety rating8 of 9 record checks met
- #7,076 of 20,610 packages by monthly downloads, tied with 18 others
- Not ranked by stars: 3 stars (ranked from 10)
- MetRegistry entry is active and says how to run itActive, with a package or a remote address.
- MetSource repository link opensThe linked GitHub repository is public.
- MetRepository is not archivedNot archived.
- MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
- MetRepository publishes a security policy (SECURITY.md)SECURITY.md found.
- MetPackage names its licence with a standard (SPDX) identifierApache-2.0
- MetThe version the registry lists can be installed and is not withdrawnThe listed version exists and is current.
- Not metnpm package carries build provenance (attestation)Signed by npm, but no build attestation.What changes this check: npm's documentation describes publishing with provenance from a cloud-hosted runner of a supported CI/CD provider, using npm CLI 9.5.0 or newer and npm publish --provenance. npm: generating provenance statements
- MetNo known critical or high advisory in the package or its dependenciesNone known in the package or its dependency tree.
Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-11-19 (security policy 2026-11-15). No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating, and the same rules apply to every server. How each check works · Leaderboards · How we stay neutral
Common questions about io.github.nirholas/vid2context
Answered from the data aboveWho publishes io.github.nirholas/vid2context?
The registry ties the namespace io.github.nirholas to the GitHub account nirholas; only its owner can publish under it. Its linked repository, github.com/nirholas/vid2context, belongs to the same GitHub account. These are facts from the registry and GitHub, not a rating.
Is io.github.nirholas/vid2context safe to install?
We do not rate servers as safe or unsafe. 8 of its 9 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. The listed version is the latest stable release. The package itself has no known vulnerability (OSV.dev). Its full dependency tree has no known advisory. These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.
Does io.github.nirholas/vid2context need an API key or sign-in?
It required sign-in on 2026-11-19. The registry entry declares no required credential; no declaration is not a guarantee.
Has io.github.nirholas/vid2context been security tested?
We tried, but no check could run. None of the 17 checks that apply to it could be exercised. The server requires sign-in. We never use a credential its operator did not give us, so most checks could not run. ProtocolProbe publishes no security verdict for a named server.
Does io.github.nirholas/vid2context publish a security policy?
Yes: its repository has a public security policy (github.com/nirholas/vid2context/blob/HEAD/SECURITY.md). That is the publisher's statement, not permission for us to test the server, and we call none of its tools.
Is the listed version current?
Yes. The registry lists 0.2.0, the latest stable release on npm.
Where is the source code of io.github.nirholas/vid2context?
In github.com/nirholas/vid2context, which opens publicly.
Found this page useful?
Anonymous · no sign-inA quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.
Compare with another server
Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.
Security testing
What did we test, and what did we leave out?
18 checks · features #1, #2
Needs the operator's credential
The server requires sign-in. We never use a credential its operator did not give us, so most checks could not run. No security score is given; a check we did not run is never counted as passed.
Why no live read-only session: The server required a sign-in before it would list anything, and we never use a credential its operator did not give us. Its operator can test it with their own credential, on their own machine, with our self-test command (/docs/selftest). — the server's own choice
- Inventory: not run · needs the operator's credential
- Hidden instructions: not run · needs the operator's credential
- Real execution: not run · needs the operator's credential
- Secret leak: not run · needs the operator's credential
- Internal addresses: not run · needs the operator's credential
- Unconfirmed changes: not run · needs the operator's credential
- Bad input: not run · needs the operator's credential
- Model requests: not run · needs the operator's credential
- Sensitive questions: not run · needs the operator's credential
- Folder boundary: not run · needs the operator's credential
- Log leaks: not run · needs the operator's credential
- Hidden content: not run · needs the operator's credential
- Fake assistant turns: not run · needs the operator's credential
- Token passthrough: not run · needs the operator's credential
- Token audience: not run · needs the operator's credential
- Sign-in redirect: not run · our policy
- Consent handling: not testable from outside
- Sign-in metadata: not applicable
0 exercised17 not run (reason given)1 not applicable
Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). None of the 17 checks that apply to it could be exercised. We do not publish security-check outcomes for named servers. These 18 checks are separate from the record checks at the top of this page, which read public records only.
- 1Inventory
tool-listReads the declared tools, resources and prompts.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 3Real execution
real-executionCalls a tool and checks what really happens.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 7Bad input
error-handlingSends bad input and watches how the server answers.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 8Model requests
samplingChecks whether the server asks the client's model to act for it.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 11Log leaks
logging-side-channelChecks whether log messages carry data they should not.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 12Hidden content
audience-hidingChecks resources that hide content from the user.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server requires sign-in, and we never use a credential its operator did not give us.not run · needs the operator's credential - 14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.Needs a real token issued by the server's own sign-in service, which only its operator can give us.not run · needs the operator's credential - 15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.Needs a real token issued by the server's own sign-in service, which only its operator can give us.not run · needs the operator's credential - 16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy - 17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
- 18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.No sign-in (OAuth) metadata is published, so there are no sign-in addresses to check.not applicable
Source: our own test, 2026-11-19, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.
What happened during the test?
Feature #8
The steps in order, as the test record holds them.
- 0 msStarted a session with the server's remote endpoint
- The server asked for sign-in before listing anything.
- 1,254 msFinished: 0 checks exercised.
Reference
How is it classified?
18 fields
One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.
“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.
Cite or correct this page
Sources and corrections
Suggested citation
ProtocolProbe. “io.github.nirholas/vid2context: MCP server record.” Data checked 2026-11-19. https://protocolprobe.com/mcp/servers/io.github.nirholas/vid2context
Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.
As JSON: this record in the API · API documentation.
Badge for your README
[](https://protocolprobe.com/mcp/servers/io.github.nirholas/vid2context)
It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.
Something wrong, or is this yours?
If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here, except for a server whose operator has claimed it and given permission (that server's page says so).
Write to hello@protocolprobe.com · corrections log · methodology