YTDL RMCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to Rytdl media search, delivery and Plex tools: Do auto-downloaded media binaries and output paths retain source verification and explicit delivery permissions?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Search and download supported media into controlled destinations with tagging and Plex workflows.

What we know

yt-dlp search, download, metadata, delivery, and Plex workflows over MCP and CLI. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Maintenance / activity evidence

@dinglebear/rytdl 1.1.0 published 2026-08-12T22:18:51.207Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Local/remote filesystem media-write authority and optional Plex operations Writes: Download media to local/NAS/remote target; Write/retag media metadata; Modify Plex playlists and transfer queues.
Local download path needs no provider API key; remote delivery targets require their own configured credentials
Sensitive access: Filesystem/media library, Remote delivery credentials, Potential cookies/source login

Potential high-impact side effects: Download media to local/NAS/remote target, Write/retag media metadata, Modify Plex playlists and transfer queues.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do auto-downloaded media binaries and output paths retain source verification and explicit delivery permissions?

The bounded review of the publisher's documented Rytdl media search, delivery and Plex tools and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Potential high-impact side effects: Download media to local/NAS/remote target, Write/retag media metadata, Modify Plex playlists and transfer queues.
Local/remote filesystem media-write authority and optional Plex operations
Local download path needs no provider API key; remote delivery targets require their own configured credentials
Downloads content from source websites and may transfer it via configured rclone/SSH/Plex targets.
Reviewed write actions: Download media to local/NAS/remote target; Write/retag media metadata; Modify Plex playlists and transfer queues
Sensitive access: Filesystem/media library, Remote delivery credentials, Potential cookies/source login
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
cost: plans, pay-per-call charges, and payment authorization details
Not a read-only scraper: can download and write files
yt-dlp/ffmpeg bootstrapping can fetch binaries
SSH, rclone, NAS and Plex destinations enlarge the trust boundary
Rights and supported source policies remain user responsibilities
The npm entry is a launcher for the Rust binary. Configure paths and executable provenance before enabling downloads.

Original activity observations

@dinglebear/rytdl 1.1.0 published 2026-08-12T22:18:51.207Z

Technical identity

npm/@dinglebear/rytdl

Exact implementation source: https://www.npmjs.com/package/@dinglebear/rytdl ↗
Reviewed resource type: MCP Server
Repository identity: dinglebear-ai/rytdl
Package identity: npm:@dinglebear/rytdl

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@dinglebear/rytdl
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
dinglebear-ai/rytdl
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
YouTube downloader suite: `npx -y @dinglebear/rytdl` runs stdio MCP, setup configures media target; external downloader/Plex integration optional.
publisher install or stdio launch · Publisher instructions
npx -y @dinglebear/rytdl setup
Configure / authenticate
MCP100 setup guide
Publisher: `npx -y @dinglebear/rytdl` (no subcommand) serves MCP over stdio. `setup` and `doctor` are separate CLI functions.
Check connection
Suggested check
Run `npx -y @dinglebear/rytdl doctor`; do not download media as a connection test.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `dinglebear-rytdl`, run `claude mcp remove dinglebear-rytdl`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove dinglebear-rytdl

Official Documentation & Sources

What it does

yt-dlp search, download, metadata, delivery, and Plex workflows over MCP and CLI. This profile is based on verified official documentation where listed; unresolved operational details are explicitly marked.

Capability: Files & Knowledge
Resource type: MCP Server
Best fit: Search and download supported media into controlled destinations with tagging and Plex workflows.

Representative uses

Search and probe media
Download media into configured target
Tag metadata and manage transfer queue
Update Plex playlists

Limitations

Not a read-only scraper: can download and write files
yt-dlp/ffmpeg bootstrapping can fetch binaries
SSH, rclone, NAS and Plex destinations enlarge the trust boundary
Rights and supported source policies remain user responsibilities
The npm entry is a launcher for the Rust binary. Configure paths and executable provenance before enabling downloads.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Local download path needs no provider API key; remote delivery targets require their own configured credentials
Permissions: Local/remote filesystem media-write authority and optional Plex operations
Data handling: Downloads content from source websites and may transfer it via configured rclone/SSH/Plex targets.
Cost: Not documented in the reviewed sources
Risk and cautions: Potential high-impact side effects: Download media to local/NAS/remote target, Write/retag media metadata, Modify Plex playlists and transfer queues.

Access scope and cautions

Write actions: Download media to local/NAS/remote target Write/retag media metadata Modify Plex playlists and transfer queues
Sensitive access: Filesystem/media library Remote delivery credentials Potential cookies/source login
Risk level: high

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Search and probe media; Download media into configured target; Tag metadata and manage transfer queue; Update Plex playlists.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @dinglebear/rytdl. Recorded transport: stdio. Recorded environment-variable notes: YTDLP_TARGET_PATH; YTDLP_VIDEO_TARGET_PATH (optional); YTDLP_EXTRACTOR_ARGS (optional). No configuration values are supplied here. Prerequisites: MCP-capable client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Local download path needs no provider API key; remote delivery targets require their own configured credentials

Can it modify data or perform write operations?

Documented write actions include: Download media to local/NAS/remote target; Write/retag media metadata; Modify Plex playlists and transfer queues. Recorded permission boundary: Local/remote filesystem media-write authority and optional Plex operations

What data-handling boundary should I consider?

Downloads content from source websites and may transfer it via configured rclone/SSH/Plex targets. Recorded sensitive-access context: Filesystem/media library; Remote delivery credentials; Potential cookies/source login.

What limitations and risks should I check before use?

Potential high-impact side effects: Download media to local/NAS/remote target, Write/retag media metadata, Modify Plex playlists and transfer queues. Not a read-only scraper: can download and write files. yt-dlp/ffmpeg bootstrapping can fetch binaries. SSH, rclone, NAS and Plex destinations enlarge the trust boundary. Rights and supported source policies remain user responsibilities. The npm entry is a launcher for the Rust binary. Configure paths and executable provenance before enabling downloads. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.