Watchlist tracking
Reviewed for relevance and future tracking value.
MCP100 Assessment
Watchlist / Tracking
Why we’re tracking it
Track YouTube API and package behavior as source access changes
Reviewed · Documentation review; complete setup workflow not independently tested
Best fit
YouTube search, channel, playlist and transcript research.
What we know
Read-oriented YouTube MCP for video/channel search, details, transcripts, creator discovery and playlist access.
Maintenance / activity evidence
- Observed (UTC)Update README.md
Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.
Verification gaps / watch-outs
- Installation and comprehensive security have not been independently audited.
- Read/search permissions.
- YouTube API key.
- Sensitive access: API key, Public creator/contact metadata
- Mostly read-only, but keep API keys out of images/config repositories and protect HTTP mode.
Full authority, access and evidence limits are available in Review context and Access & risk.
Popularity
577 repository stars
Stars observed Sep 25, 2026.
Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.
Do not overwrite existing reviewed stars/download metrics with nulls from this enrichment batch.
All limitations / Review context
Which YouTube operations and authentication requirements are currently documented?
The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.
- Mostly read-only, but keep API keys out of images/config repositories and protect HTTP mode.
- Read/search permissions.
- YouTube API key.
- Public YouTube data and transcripts are returned; Docker mode exposes an HTTP listener.
- Sensitive access: API key, Public creator/contact metadata
- Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
- A project-specific SECURITY.md policy was not available at the fetched official path; the review remains limited to published repository notices.
- No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
- The fetched official SECURITY.md path returned HTTP 404; it was not treated as positive evidence.
- At least one YouTube API key is required.
- Quota limits and transcript availability still apply.
- Current documented core surface is research-oriented, not publishing.
Original activity observations
- 2026-08-08T22:55:53Z: Update README.md
Technical identity
github.com/zubeidhendricks/youtube-mcp-server- Exact implementation source
- https://github.com/zubeidhendricks/youtube-mcp-server ↗
- Reviewed resource type
- MCP Server
- Repository identity
- zubeidhendricks/youtube-mcp-server
- Package identity
- npm:zubeid-youtube-mcp-server
- Service endpoint
- http://localhost:8088/mcp
Evidence & Sources
- Evidence basis
- Recorded source evidence
- Setup runtime verification
- Not independently runtime-tested by MCP100 for this setup workflow.
Reviewed · Latest source observation
- GitHub repository ↗
zubeidhendricks/youtube-mcp-server
Recorded repository material and project history.
Includes references whose attribution is not established.
Setup · Watchlist
Install & Agents
Publisher instructions.
Source evidence observed .
Additional setup details required — see the specific gaps below.
Install / connect
Publisher instructionsPublisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · Publisher instructions
npx -y zubeid-youtube-mcp-serverConfigure / authenticate
MCP100 setup guideSet at least one of YOUTUBE_API_KEY, YOUTUBE_API_KEY2 or YOUTUBE_API_KEY3; register npx -y zubeid-youtube-mcp-server in client. Key 2/3 are optional quota fallbacks.
Check connection
Suggested checkVerify tool discovery then perform a read-only metadata lookup for a public video.
Remove / uninstall / revoke
MCP100 setup guideIf registered in Claude Code under the name `youtube`, remove the client entry with `claude mcp remove youtube`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Separate credential guidance (provider revocation is not verified): Revoke or rotate YOUTUBE_API_KEY in the provider dashboard if compromised/no longer needed; removing the MCP client entry alone does not revoke it.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove youtube
What it does
Read-oriented YouTube MCP for video/channel search, details, transcripts, creator discovery and playlist access.
- Capability
- Search & Web
- Resource type
- MCP Server
- Industry
- Media & Marketing
- Best fit
- YouTube search, channel, playlist and transcript research.
Representative uses
- Search videos/channels
- Get video/transcript details
- List channel videos
- Inspect playlists/creator channels
Limitations
- At least one YouTube API key is required.
- Quota limits and transcript availability still apply.
- Current documented core surface is research-oriented, not publishing.
Reviewed access
Access & risk
Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.
- Authentication
- YouTube API key.
- Permissions
- Read/search permissions.
- Data handling
- Public YouTube data and transcripts are returned; Docker mode exposes an HTTP listener.
- Cost
- usage_based
- Risk and cautions
- Mostly read-only, but keep API keys out of images/config repositories and protect HTTP mode.
Access scope and cautions
- Write actions
- None in the reviewed inventory
- Sensitive access
- API key Public creator/contact metadata
- Risk level
- moderate
FAQ
Based on reviewed evidence as of 2026-10-07. Watchlist tracking is not a recommendation or a security certification.
Which tasks are documented for this implementation?
What setup and authentication are documented?
Can it modify data or perform write operations?
What data-handling boundary should I consider?
What limitations and risks should I check before use?
What cost model is recorded?
Is this an official MCP?
ZubeidHendricks is listed as Community implementation in MCP100’s current evidence.