YouTube Transcript MCP Server

The materials explicitly state that no keys or environment variables are required. No API tokens, OAuth credentials, or requests for local secrets are described, so credential exposure appears low based on the provided facts.

The description says it fetches YouTube video transcripts, which normally implies network access to YouTube-related resources. Although the materials declare no remote host, no README or implementation details are provided, so the actual egress scope and transmitted data cannot be fully verified.

The objective checks indicate that it executes code. As an MCP tool, this typically means running a local server process and handling requests. The provided materials do not show any abnormal system privilege requests or unrelated high-risk execution behavior.

The materials only state that it provides YouTube transcript content to LLM agents and do not claim broad filesystem access or local sensitive data collection. However, with no README available, possible caching, logging, or additional local data access cannot be confirmed.

Positive factors include being open source under the MIT License, making the code auditable in principle. However, it comes from a third-party registry, has 0 stars, and its maintenance status is unknown, so trust is limited and the code and dependencies should be reviewed before use.