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.

Plex Director

OCI · DOCKER.IO/HONEYBEARTECH/PLEX-DIRECTOR-MCP

Ask about and manage your own Plex, Radarr, Sonarr, Prowlarr and download clients.

Available components

oci · docker.io/honeybeartech/plex-director-mcp 10
0 this week 10 Trust /100

Last scanned (35 minutes ago)

Scores higher than 23% of OCI servers

Category Entertainment and Games

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result. View diagnostics → Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency48
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 20 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 6 categories

Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

What we tested

Checks we ran (5)

  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure

Checks we could not complete (9)

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.

  • Malware scan in Supply Chain Security (scores 0 for this)No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  • Known CVEs in Supply Chain Security (scores 0 for this)Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.
  • Install scripts in Supply Chain Security (scores 0 for this)Install-script risk not yet assessed.
  • Dependency health in Supply Chain Security (scores 0 for this)Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

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.

  • 31 Oct 26 0
    • Provenance: unverified → fail ▼ security
  • 30 Oct 26 0
    • Provenance: fail → unverified ▼ security
  • 16 Oct 26 0
    • Package version: 1.2.0 → 1.4.0 functional
  • 15 Oct 26 10

    First indexed and scored.

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 6 Nov 2026 · Analysed oci/docker.io/honeybeartech/plex-director-mcp@1.4.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Vulnerabilities 12 ungraded findings

From the publisher's SBOM, not graded. These advisories match packages listed in the SBOM the publisher attached to this image. A publisher naming a vulnerable package in their own image is credible, so we show them. Nothing verifies that SBOM, though, so the Known CVEs signal does not grade the image from it.

ID CVE Severity Vector Fix available
GHSA-rmxm-3fg6-px4f CVE-2026-118663 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-27r3-jxmh-p828 CVE-2026-111181 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-333x-w4r6-6crp CVE-2026-110725 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-w74x-v6f9-j3xg CVE-2026-110306 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N yes
GHSA-wjr9-j795-jxcr CVE-2026-110180 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N yes
GHSA-xhq7-xmqj-769h CVE-2026-110095 low CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-8r9p-f939-6h3c CVE-2026-111755 high yes
GHSA-mrwp-f3q8-3g9p CVE-2026-116689 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-q3jh-wrc6-jgq8 CVE-2026-111756 high yes
GHSA-5r4p-p66f-jhc7 CVE-2026-109955 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-rxp7-6hxx-x8q5 CVE-2026-111997 medium yes
GHSA-6pq8-jhm2-2vcw CVE-2026-110816 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L yes

Background: What a vulnerability scan can and cannot prove →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the Plex Director MCP server?

Plex Director runs locally as a container image, launched with docker run --rm -i -e PLEX_URL -e PLEX_TOKEN -e RADARR_URL -e RADARR_API_KEY -e SONARR_URL -e SONARR_API_KEY -e PROWLARR_URL -e PROWLARR_API_KEY -e SABNZBD_URL -e SABNZBD_API_KEY -e QBITTORRENT_URL -e QBITTORRENT_USER -e QBITTORRENT_PASS -e TAUTULLI_URL -e TAUTULLI_API_KEY -e TMDB_API_KEY -e WEB_PASSWORD -e SETTINGS_ENCRYPTION_KEY docker.io/honeybeartech/plex-director-mcp:1.4.0. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · docker.io/honeybeartech/plex-director-mcp

# add to Claude Code
claude mcp add honeybeartech-plex-director-mcp -- docker run --rm -i -e PLEX_URL -e PLEX_TOKEN -e RADARR_URL -e RADARR_API_KEY -e SONARR_URL -e SONARR_API_KEY -e PROWLARR_URL -e PROWLARR_API_KEY -e SABNZBD_URL -e SABNZBD_API_KEY -e QBITTORRENT_URL -e QBITTORRENT_USER -e QBITTORRENT_PASS -e TAUTULLI_URL -e TAUTULLI_API_KEY -e TMDB_API_KEY -e WEB_PASSWORD -e SETTINGS_ENCRYPTION_KEY docker.io/honeybeartech/plex-director-mcp:1.4.0

This image reads PLEX_URL, PLEX_TOKEN, RADARR_URL, RADARR_API_KEY, SONARR_URL, SONARR_API_KEY, PROWLARR_URL, PROWLARR_API_KEY, SABNZBD_URL, SABNZBD_API_KEY, QBITTORRENT_URL, QBITTORRENT_USER, QBITTORRENT_PASS, TAUTULLI_URL, TAUTULLI_API_KEY, TMDB_API_KEY, WEB_PASSWORD and SETTINGS_ENCRYPTION_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it.

Common questions

What is the Plex Director MCP server?

Plex Director is an MCP server listed in the public MCP registry as io.github.HoneyBearTech/plex-director-mcp. Ask about and manage your own Plex, Radarr, Sonarr, Prowlarr and download clients. This page covers its container image (docker.io/honeybeartech/plex-director-mcp).

Is the Plex Director MCP server safe to use?

Plex Director scores 10 out of 100 on VerifyMCP. The SBOM its publisher attached lists packages with 12 known advisories as of 6 November 2026. We do not grade that SBOM, as nothing verifies it. 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.

Is the Plex Director MCP server still maintained?

Plex Director is still listed as active in the MCP registry. We last reached this channel on 6 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 Plex Director MCP server under?

Plex Director 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 Plex Director MCP server?

VerifyMCP ran 5 checks on Plex Director, covering Source repository, Provenance, License, Maintenance and 1 more. 9 items could not be completed, a gap on our side rather than a finding about Plex Director: Malware scan, Known CVEs, Install scripts, Dependency health and 5 more. 6 categories score 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.