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.

YouTube Transcript MCP

NPM · @FAKASYS/YOUTUBE-TRANSCRIPT-MCP

Fetches public YouTube caption tracks with timestamps and exact language selection.

0 this week 66 Trust /100

Last scanned (15 hours ago)

Scores higher than 38% of npm servers

Category Entertainment and Games

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 Security100
  • 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
  • 0 of 25 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 10 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability80
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 411 tokens (~137/item across 3 items; 3 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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.

What we tested

Checks we ran (14)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Security disclosure in Provenance & TransparencySecurity-disclosure policy not yet verified: we couldn't inspect the source repository.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

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 →

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 Nov 26 −5
    • Source repository: pass → fail ▼ security
    • Security disclosure: fail → unverified ▼ functional
  • 11 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 10 Nov 26 56

    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 21 Nov 2026 · Analysed npm/@fakasys/youtube-transcript-mcp@1.0.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 25 packages
Packages resolved 25
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~411 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
get_youtube_transcript ~191

Fetches and returns publicly available YouTube caption tracks; it does not transcribe audio. Accepts allowed YouTube URLs or raw video IDs, exact ISO 639-1/BCP-47 language codes such as pt-BR, es-419, and zh-Hans, and formats items into timestamped lines. If the requested track is unavailable, returns an error rather than another language.

NameTypeReqDescription
langstring–Optional ISO 639-1/BCP-47 language code, including regional or script subtags such as "pt-BR" or "zh-Hans"
videoIdOrUrlstringyesThe YouTube video URL (e.g. https://www.youtube.com/watch?v=dQw4w9WgXcQ or https://youtu.be/dQw4w9WgXcQ) or raw 11-character video ID

No output schema declared.

No examples provided.

list_youtube_transcript_languages ~78

Lists the caption languages currently exposed by YouTube for a video, including each language code, display name, and whether it is auto-generated. Call this before get_youtube_transcript when the user wants a specific language.

NameTypeReqDescription
videoIdOrUrlstringyesThe YouTube video URL or raw 11-character video ID

No output schema declared.

No examples provided.

summarize_youtube_transcript ~142

Fetches a publicly available YouTube caption track and returns it to the calling AI for summarization. This server does not transcribe audio, run an LLM, or require an API key; it relies on ChatGPT or the connected MCP client to summarize the returned captions.

NameTypeReqDescription
langstring–Optional ISO 639-1/BCP-47 language code, including regional or script subtags such as "pt-BR" or "zh-Hans"
stylestring–How the calling AI should format the summary
videoIdOrUrlstringyesThe YouTube video URL or raw 11-character video ID

No output schema declared.

No examples provided.

Install

How do I install the YouTube Transcript MCP server?

YouTube Transcript MCP runs locally as an npm package, launched with npx -y @fakasys/youtube-transcript-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 · @fakasys/youtube-transcript-mcp

# add to Claude Code
claude mcp add windows10fan648-youtube-transcript-mcp -- npx -y @fakasys/youtube-transcript-mcp
Common questions

What is the YouTube Transcript MCP server?

YouTube Transcript MCP is listed in the public MCP registry as io.github.windows10fan648/youtube-transcript-mcp. Fetches public YouTube caption tracks with timestamps and exact language selection. This page covers its npm package (@fakasys/youtube-transcript-mcp).

Is the YouTube Transcript MCP server safe to use?

YouTube Transcript MCP scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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 YouTube Transcript MCP server expose?

YouTube Transcript MCP exposes 3 tools: get_youtube_transcript, summarize_youtube_transcript, list_youtube_transcript_languages. Their descriptions and schemas cost roughly 411 tokens of context every time the server is loaded.

Is the YouTube Transcript MCP server still maintained?

YouTube Transcript MCP is still listed as active in the MCP registry. We last reached this channel on 21 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 YouTube Transcript MCP server under?

YouTube Transcript MCP declares the MIT 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 YouTube Transcript MCP server?

VerifyMCP ran 14 checks on YouTube Transcript MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 10 more. 2 items could not be completed, a gap on our side rather than a finding about YouTube Transcript MCP: Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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.