MCP Risk

Directory / server

ai.dinglebear/ytdl-rmcp

This directory entry reports an automated security scan of ai.dinglebear/ytdl-rmcp, scanned 2026-07-28. Trust grade B rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via package-source

B 89/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as ai.dinglebear/ytdl-rmcp. 1 finding
  • Registry entry: ai.dinglebear/ytdl-rmcp ↗
PASS Source repository is public and maintained §1.2
Active repository with a license. 5 findings
  • Repository ↗
  • Last push: 0 days ago
  • Stars: 1
  • License: MIT
  • Security policy (SECURITY.md): absent
WARN Published package is consistent and attested §1.3
Minor integrity gaps: package is only 18 days old; no npm provenance attestation. 6 findings
  • Package: ytdl-rmcp@1.0.2 ↗
  • Ecosystem: npm
  • Age: 18 days
  • Weekly downloads: 212
  • Repo field matches source repo: true
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned. Capabilities detected: process-execution, filesystem. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 5 findings
  • process-execution (child process execution): bin/rytdl.js
  • process-execution (child process module import): bin/rytdl.js
  • filesystem (filesystem write/delete): bin/rytdl.js
  • filesystem (fs module import): bin/rytdl.js
  • Detected capabilities: process-execution, filesystem
INFO Transport & authentication §3

Local (stdio) server: runs with host-process privileges by design. Transport checks apply to remote servers; scrutiny shifts to §1/§2.
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for ytdl-rmcp @1.0.2 (npm).
UNVERIFIABLE Server-supplied instructions free of poisoning indicators §5.1–§5.4

No server-supplied instructions or tool descriptions were obtainable to scan.

Score history

DateGradeScore
2026-07-28B89/100
2026-07-27B89/100
2026-07-27B89/100
2026-07-27B89/100
2026-07-26B89/100
2026-07-26B89/100
2026-07-26B89/100
2026-07-25F38/100
2026-07-25F36/100
2026-07-25F36/100
2026-07-25F36/100
2026-07-24F36/100
2026-07-24F36/100
2026-07-24F36/100
2026-07-13F38/100
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.