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.

yt-mem-ai

PYPI · YT-MEM-AI · SCANNED SEP 13

Local YouTube memory: transcribe, embed and search videos, with summaries and highlights.

Available components

pypi · yt-mem-ai 32
0 this week 32 Trust /100
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 Security85
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 89 of 148 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 89 of 148 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability0
  • Schema quality not yet verified: this package could not be installed in a clean environment, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this package could not be installed in a clean environment, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this package could not be installed in a clean environment, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this package could not be installed in a clean environment, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this package could not be installed in a clean environment, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the yt-mem-ai MCP server?

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

pypi · yt-mem-ai

# add to Claude Code
claude mcp add dasein108-yt-mem-ai -- uvx yt-mem-ai
// .cursor/mcp.json
{
  "mcpServers": {
    "dasein108-yt-mem-ai": {
      "command": "uvx",
      "args": [
        "yt-mem-ai"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "dasein108-yt-mem-ai": {
      "command": "uvx",
      "args": [
        "yt-mem-ai"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add dasein108-yt-mem-ai -- uvx yt-mem-ai
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dasein108-yt-mem-ai": {
      "type": "local",
      "command": [
        "uvx",
        "yt-mem-ai"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add dasein108-yt-mem-ai --command uvx --arg yt-mem-ai
# ~/.hermes/config.yaml
mcp_servers:
  dasein108-yt-mem-ai:
    command: "uvx"
    args: ["yt-mem-ai"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "dasein108-yt-mem-ai": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "yt-mem-ai"
      ]
    }
  }
}
# add to Vellum
assistant mcp add dasein108-yt-mem-ai -t stdio -c uvx -a yt-mem-ai
// mcp.json
{
  "mcpServers": {
    "dasein108-yt-mem-ai": {
      "command": "uvx",
      "args": [
        "yt-mem-ai"
      ]
    }
  }
}
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.

  • 12 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 7 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
  • 3 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 2 Sept 26 −15
    • Malware scan: pass → unverified ▼ security
  • 1 Sept 26 +15
    • Malware scan: unverified → pass ▲ security
  • 31 Aug 26 −15
    • Malware scan: pass → unverified ▼ security
  • 29 Aug 26 +15
    • Malware scan: unverified → pass ▲ security
  • 27 Aug 26 −15
    • Malware scan: pass → unverified ▼ security
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 13 Sept 2026 · Analysed pypi/yt-mem-ai@0.6.3

Provenance No attestation

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

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

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

Dependencies 89 packages
Packages resolved 89
Stale 9
No linked repository 1
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

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 →

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.

Common questions

What is the yt-mem-ai MCP server?

yt-mem-ai is an MCP server listed in the public MCP registry as io.github.dasein108/yt-mem-ai. Local YouTube memory: transcribe, embed and search videos, with summaries and highlights. This page covers its PyPI package (yt-mem-ai).

Is the yt-mem-ai MCP server safe to use?

yt-mem-ai scores 32 out of 100 on VerifyMCP. 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 yt-mem-ai MCP server still maintained?

yt-mem-ai is still listed as active in the MCP registry. We last reached this channel on 13 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.