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.

MCP Server for Binge-watch

PYPI · MCP-VODS · 2 COMPONENTS

MCP Server for Binge-watch / MoonTV / LunaTV. 一个用于追剧/追番的MCP服务器,为AI提供搜索影视播放地址的能力,并支持在小米等安卓电视/投影仪上直接播放

0 this week 0 Trust /100

Last scanned (7 hours ago)

Scores higher than 0% of PyPI servers

Category Entertainment and Games

Recent critical change

CVE-2026-32871 affects this package (3 Aug 2026). See the changelog before you install this server.

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 Security75
Provenance & Transparency44
Schema Quality & AI Usability0
  • Instruction-quality not yet verified: the AI judgement didn't run.Unverified
  • Nothing to assess: this server exposes no tool/resource definitions to measure a footprint for. See how to fix → Fail
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage0
  • Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety0
  • Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.Unverified
  • Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
  • Manipulation not yet verified: our capture carried no tool text for a judge to read, so we will not certify text no model has read as clean.Unverified
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: 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 (13)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • MCP protocol

Checks we could not complete (4)

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.

  • Schema quality in Schema Quality & AI UsabilityInstruction-quality not yet verified: the AI judgement didn't run.
  • Injection markers in Tool Safety (scores 0 for this)Injection markers not yet verified: our capture carried no server instructions, tool names or descriptions for the scan to read.
  • Destructive annotations in Tool Safety (scores 0 for this)Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.
  • Judged manipulation in Tool Safety (scores 0 for this)Manipulation not yet verified: our capture carried no tool text for a judge to read, so we will not certify text no model has read as clean.

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.

  • 5 Nov 26 0
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 0
    • Malware scan: pass → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
  • 2 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 1 Nov 26 0
    • Provenance: unverified → fail ▼ security
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Provenance: fail → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 29 Oct 26 0
    • Malware scan: pass → unverified ▼ security
  • 27 Oct 26 0
    • Provenance: unverified → fail ▼ security
  • 26 Oct 26 0
    • Provenance: fail → unverified ▼ security
    • Security disclosure: unverified → fail ▼ functional
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 5 Nov 2026 · Analysed pypi/mcp-vods@0.1.9

Provenance No attestation

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

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend Known build tool hatchling.build

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 6 findings
ID CVE Severity Vector Fix available
GHSA-m8x7-r2rg-vh5g CVE-2025-64340 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H yes
GHSA-rww4-4w9c-7733 CVE-2026-27124 high yes
GHSA-vv7q-7jx5-f767 CVE-2026-32871 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H yes
PYSEC-2026-2475 CVE-2025-64340 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2476 CVE-2026-27124 none yes
PYSEC-2026-338 CVE-2026-32871 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 81 packages
Packages resolved 81
Stale 5
No linked repository 3
Tree resolution Complete

Background: SBOMs and build attestations, explained →

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 →

The sandbox run completed and this package exposed no tools.

Install

How do I install the MCP Server for Binge-watch server?

MCP Server for Binge-watch runs locally as a PyPI package, launched with uvx mcp-vods. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mcp-vods

# add to Claude Code
claude mcp add aahl-mcp-vods -- uvx mcp-vods
Common questions

What is the MCP Server for Binge-watch server?

MCP Server for Binge-watch is listed in the public MCP registry as io.github.aahl/mcp-vods. MCP Server for Binge-watch / MoonTV / LunaTV. 一个用于追剧/追番的MCP服务器,为AI提供搜索影视播放地址的能力,并支持在小米等安卓电视/投影仪上直接播放. This page covers its PyPI package (mcp-vods).

What tools does the MCP Server for Binge-watch server expose?

MCP Server for Binge-watch exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the MCP Server for Binge-watch server still maintained?

MCP Server for Binge-watch is still listed as active in the MCP registry. We last reached this channel on 5 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 MCP Server for Binge-watch server under?

MCP Server for Binge-watch declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.