YouTube License Metadata — FlashData vs YouTube Data
YouTube License Metadata — FlashData is an MCP server published by flashdata-dev. Marketplaces we read that list it: 1 (Official MCP Registry). YouTube Data is an MCP server published by kirbah. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
| Marketplace |  YouTube License Metadata — FlashData |  YouTube Data |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.1.15 Downloads/month (npm): 2 872 Downloads/week (npm): 1 076 Forks (GitHub): 16 Stars (GitHub): 30 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
| Fact | YouTube License Metadata — FlashData | YouTube Data |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 30 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 16 (better) |
| Last release (differs) | 2026-10-15 | Not published |
| Where it runs (differs) | On your machine (https://github.com/rocosen/flashdata-mcp/releases/download/smithery-task-servers-v0.1.1/flashdata-youtube-trainability-0.1.1.mcpb) | Remote server or your machine |
| Transport (differs) | stdio | stdio, Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/rocosen/flashdata-mcp | github.com/kirbah/mcp-youtube |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (4 days ago) |
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
YouTube License Metadata — FlashData
YouTube Creative Commons license-label metadata, not training authorization. Paid FlashData API.
YouTube Data
YouTube MCP server for token-optimized, structured data using the YouTube Data API v3.
How to run each
YouTube License Metadata — FlashData
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: FLASHDATA_API_KEY (secret)
YouTube Data As a local MCP server: npm package
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-youtubeRequires: 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
Only YouTube License Metadata — FlashData asks for
FLASHDATA_API_KEY (secret)
Only YouTube Data asks for
MDB_MCP_CONNECTION_STRING (secret)YOUTUBE_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: YouTube License Metadata — FlashData · What it can do: YouTube Data · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.