Stv MCP Server

stv PyPI v1.3.2

Published by hybirdss — 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.

Talk to your TV. Play Netflix, Disney+, and 20+ streaming platforms by name on any smart TV.

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 3

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

In the server's implementation (`src/smartest_tv/http.py:3`): 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: rtest-tv. Replaces raw subprocess.run(["curl", ...]) calls with a structured helper that provides consistent error hand

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 src/smartest_tv/http.py

low Shell/command execution in packaging/dev tooling (.github/scripts/check-regressions.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`.github/scripts/check-regressions.py:15`): 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: try: result = subprocess.run( ["git", "show", "origin/main:community-cache.json"], cap

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 .github/scripts/check-regressions.py

low Shell/command execution in packaging/dev tooling (.github/scripts/verify-netflix.py)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`.github/scripts/verify-netflix.py:24`): 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: try: result = subprocess.run( [ "curl", "-s", "-L", "--compressed", "--max-time",

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 .github/scripts/verify-netflix.py

Tools 23

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

  • tv_audiono sensitive capability
  • tv_castno sensitive capability
  • tv_displayno sensitive capability
  • tv_groupsno sensitive capability
  • tv_historyno sensitive capability
  • tv_insightsno sensitive capability
  • tv_launchno sensitive capability
  • tv_list_tvsno sensitive capability
  • tv_nextno sensitive capability
  • tv_notifyno sensitive capability
Show 13 more tools ↓
  • tv_playno sensitive capability
  • tv_powerno sensitive capability
  • tv_queueno sensitive capability
  • tv_recommendno sensitive capability
  • tv_resolveno sensitive capability
  • tv_sceneno sensitive capability
  • tv_screenno sensitive capability
  • tv_stateno sensitive capability
  • tv_state_watchno sensitive capability
  • tv_statusno sensitive capability
  • tv_syncno sensitive capability
  • tv_volumeno sensitive capability
  • tv_whats_onno sensitive capability

What this scan could not see

Versions 3

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.3.2 latest A 93/100 3 1.13.0 2026-08-25
v1.3.0 A 93/100 3 1.12.1 2026-08-16
v1.2.0 A 93/100 3 1.12.1 2026-07-27

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/stv/badge.svg)](https://mcptrustchecker.com/registry/stv)
HTML
<a href="https://mcptrustchecker.com/registry/stv"><img src="https://mcptrustchecker.com/registry/stv/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/stv/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 stv --online --registry pypi

Use the free API → How scoring works

More in Design & Media