youtube-transcript-search@1.1.0
VERIFIED· startup onlyPublisher claims: "Enables agents to search YouTube videos and grep their transcripts for keywords, returning matching videos with occurrence counts and surrounding context." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
YOUTUBE_API_KEYConfiguration, not credentials: ALL_PROXY, FILTER_KEYS, YOUTUBE_SEARCH_BACKEND, YT_DLP, YTS_API_BASE, YTS_CACHE_DIR, YTS_COOKIES_FILE, YTS_INTERVAL_MS, YTS_JOB_DIR, YTS_PROXY, YTS_QUIET, YTS_RL_STOP, YTS_SKIP_PROBE- Where it talks to
- no vendor host named in the codeAlso youtube.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names youtube.com as well as its own vendor. The guard injects YOUTUBE_API_KEY only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-09 and scored it 88/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 20 s · 2 scenarios · 0 deviationsStatic findings
// jobs/<jobId>.log — log postępu (rodzeństwo katalogu joba)Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.r = run(["new", "--id", ID_A, "--langs", "pl", "--keywords", "x", "--proxy", "http://u:p@h:1", "--job-dir", join(shimDir, "jobs9")]);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.const envNoKey = { ...env, YOUTUBE_API_KEY: "" };Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.