Plex (vladimir-tutin) MCP Server

plex-mcp-server PyPI v1.1.7

Published by vladimir-tutin — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for Plex Media Server - Control your Plex server via Claude Desktop, Cursor, or any MCP-compatible client

Trust grade
A
93/100
Last scanned get badge →
Trust
A · 93/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 93/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 7 = 93. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (watcher.py)MTC-SRC-002

In the server's implementation (`watcher.py:67`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: self.process = subprocess.Popen( command, cwd=SERVER_PATH, cr

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server watcher.py

Tools 55

Each tool and what it can reach — statically extracted from the published source.

  • media_get_detailsingests untrusted input
  • sessions_get_media_playback_historyingests untrusted input
  • client_control_playbackno sensitive capability
  • client_get_detailsno sensitive capability
  • client_get_timelinesno sensitive capability
  • client_listno sensitive capability
  • client_navigateno sensitive capability
  • client_set_streamsno sensitive capability
  • client_start_playbackno sensitive capability
  • collection_add_tono sensitive capability
Show 45 more tools ↓
  • collection_createno sensitive capability
  • collection_deleteno sensitive capability
  • collection_editno sensitive capability
  • collection_listno sensitive capability
  • collection_remove_fromno sensitive capability
  • library_get_contentsno sensitive capability
  • library_get_detailsno sensitive capability
  • library_get_recently_addedno sensitive capability
  • library_get_statsno sensitive capability
  • library_listno sensitive capability
  • library_refreshno sensitive capability
  • library_scanno sensitive capability
  • media_deleteno sensitive capability
  • media_edit_metadatano sensitive capability
  • media_get_artworkno sensitive capability
  • media_list_available_artworkno sensitive capability
  • media_searchno sensitive capability
  • media_set_artworkno sensitive capability
  • playlist_add_tono sensitive capability
  • playlist_copy_to_userno sensitive capability
  • playlist_createno sensitive capability
  • playlist_deleteno sensitive capability
  • playlist_editno sensitive capability
  • playlist_get_contentsno sensitive capability
  • playlist_listno sensitive capability
  • playlist_remove_fromno sensitive capability
  • playlist_upload_posterno sensitive capability
  • server_clean_bundlesno sensitive capability
  • server_empty_trashno sensitive capability
  • server_get_alertsno sensitive capability
  • server_get_bandwidthno sensitive capability
  • server_get_butler_tasksno sensitive capability
  • server_get_current_resourcesno sensitive capability
  • server_get_infono sensitive capability
  • server_get_plex_logsno sensitive capability
  • server_optimize_databaseno sensitive capability
  • server_run_butler_taskno sensitive capability
  • sessions_get_activeno sensitive capability
  • user_get_continue_watchingno sensitive capability
  • user_get_infono sensitive capability
  • user_get_on_deckno sensitive capability
  • user_get_statisticsno sensitive capability
  • user_get_watch_historyno sensitive capability
  • user_list_all_usersno sensitive capability
  • user_search_usersno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.1.7 latest A 93/100 1 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 93/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/plex-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/plex-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/plex-mcp-server"><img src="https://mcptrustchecker.com/registry/plex-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/plex-mcp-server/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan plex-mcp-server --online --registry pypi

Use the free API → How scoring works

Other implementations of Plex 5

Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →

More in Other