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.shephouse-actors/shephouse-yt-mcp

PYPI · SHEPHOUSE-YT-MCP

YouTube transcripts for agents on cloud servers, via an Apify Actor. By ShepHouse (AI-operated).

Available components

+4 this week 82 Trust /100

Last scanned (21 hours ago)

Scores higher than 82% of PyPI servers

Category Education and Research

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
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 31 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency71
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to shephouse-actors/shephouse-yt-mcp). View diagnostics → Pass
  • 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 Usability62
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 121 tokens (~60/item across 2 items; 2 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
  • Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 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
What we tested

Checks we ran (15)

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

Checks we could not complete (1)

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.

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.

  • 21 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 18 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 17 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 16 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 13 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
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 pypi/shephouse-yt-mcp@0.1.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo shephouse-actors/shephouse-yt-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/shephouse-actors/shephouse-yt-mcp/.github/workflows/publish.yml@refs/tags/v0.1.0
Rekor log index 3573363711
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:898e2a396cc78ae91d5854f4e27fb71dee59d2f7917ede047bb9ecc1a859dbc3

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 31 packages
Packages resolved 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 2 exposed · ~121 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_transcript ~73

Fetch the transcript (captions) of one YouTube video. `video` is a URL or 11-char id. `languages` is a preference list. Set timestamps=True for [m:ss] lines.

NameTypeReqDescription
languagesarray––
timestampsboolean––
videostringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

get_transcripts ~48

Fetch transcripts for up to 50 YouTube videos in one call (URLs or ids).

NameTypeReqDescription
languagesarray––
timestampsboolean––
videosarrayyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

Install

How do I install the io.github.shephouse-actors/shephouse-yt-mcp server?

io.github.shephouse-actors/shephouse-yt-mcp runs locally as a PyPI package, launched with uvx shephouse-yt-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · shephouse-yt-mcp

# add to Claude Code
claude mcp add shephouse-actors-shephouse-yt-mcp -- uvx shephouse-yt-mcp
Common questions

What is the io.github.shephouse-actors/shephouse-yt-mcp server?

io.github.shephouse-actors/shephouse-yt-mcp is listed in the public MCP registry as io.github.shephouse-actors/shephouse-yt-mcp. YouTube transcripts for agents on cloud servers, via an Apify Actor. By ShepHouse (AI-operated). This page covers its PyPI package (shephouse-yt-mcp).

Is the io.github.shephouse-actors/shephouse-yt-mcp server safe to use?

io.github.shephouse-actors/shephouse-yt-mcp scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. Its build provenance is signed and verified. 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.shephouse-actors/shephouse-yt-mcp server expose?

io.github.shephouse-actors/shephouse-yt-mcp exposes 2 tools: get_transcript, get_transcripts. Their descriptions and schemas cost roughly 121 tokens of context every time the server is loaded.

Is the io.github.shephouse-actors/shephouse-yt-mcp server still maintained?

io.github.shephouse-actors/shephouse-yt-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 io.github.shephouse-actors/shephouse-yt-mcp server under?

io.github.shephouse-actors/shephouse-yt-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 io.github.shephouse-actors/shephouse-yt-mcp server?

VerifyMCP ran 15 checks on io.github.shephouse-actors/shephouse-yt-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.shephouse-actors/shephouse-yt-mcp: Security disclosure. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.