Ext Ops Panel
Open dashboard
Comparison

youty-mcp vs YouTube Data

youty-mcp is an MCP server published by legetdev. Marketplaces we read that list it: 1 (PyPI (MCP servers)). YouTube Data is an MCP server published by kirbah. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-07. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceyouty-mcpYouTube Data
PyPI (MCP servers) Listed
Version: 2.0.9
Downloads/month (PyPI): 357
Downloads/week (PyPI): 604
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.16
Downloads/month (npm): 2 328
Downloads/week (npm): 296
Forks (GitHub): 17
Stars (GitHub): 33
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.1.16
Downloads/month (npm): 2 328
Downloads/week (npm): 296
Forks (GitHub): 17
Stars (GitHub): 33
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

youty-mcp vs YouTube Data
Factyouty-mcpYouTube Data
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (worse)33 (better)
Forks (GitHub) (differs)0 (worse)17 (better)
Last release (differs)2026-11-02 (better)2026-11-01 (worse)
Where it runs (differs)On your machine (youty-mcp)Remote server or your machine
Transport (differs)Not statedstdio, Streamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 2
LicenceMITMIT
Repository (differs)github.com/legetdev/youtygithub.com/kirbah/mcp-youtube
Changes in the last 7 days22
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 39 h ago returned HTTP 404

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

youty-mcp

In its own words, on PyPI (MCP servers):

Youty MCP server — lets AI assistants search, read, watch, and save videos in your local Youty vault.

YouTube Data

In its own words, on Official MCP Registry:

YouTube MCP server for token-optimized, structured data using the YouTube Data API v3.

How to run each

youty-mcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

YouTube Data As a local MCP server: npm package

Claude Code
claude mcp add --env "MDB_MCP_CONNECTION_STRING=<YOUR_MDB_MCP_CONNECTION_STRING>" --env "YOUTUBE_API_KEY=<YOUR_YOUTUBE_API_KEY>" --transport stdio mcp-youtube -- npx -y @kirbah/mcp-youtube

Requires: MDB_MCP_CONNECTION_STRING (secret), YOUTUBE_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only YouTube Data has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

The marketplaces of youty-mcp publish no settings it asks for, so we do not compare settings.

What it can do: youty-mcp · What it can do: YouTube Data · Compare two other plugins

Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built