Fetch (Reference) vs io.github.jkawamoto/mcp-youtube-transcript
Fetch (Reference) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.jkawamoto/mcp-youtube-transcript is an MCP server published by jkawamoto. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-15. 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 |  Fetch (Reference) |   io.github.jkawamoto/mcp-youtube-transcript |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:1a7a0996a565 Forks (GitHub): 11 790 Pulls (Docker Hub): 1 915 198 Stars (Docker Hub): 58 Stars (GitHub): 91 268 Not marked · First seen |
Listed Version: sha256:90eefb484754 Forks (GitHub): 76 Pulls (Docker Hub): 301 549 Stars (Docker Hub): 19 Stars (GitHub): 489 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.8.0 Forks (GitHub): 76 Stars (GitHub): 489 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 | Fetch (Reference) | io.github.jkawamoto/mcp-youtube-transcript |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 91 268 (better) | 489 (worse) |
| Pulls (Docker Hub) (differs) | 1 915 198 (better) | 301 549 (worse) |
| Forks (GitHub) (differs) | 11 790 (better) | 76 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/fetch) | On your machine (https://github.com/jkawamoto/mcp-youtube-transcript/releases/download/v0.8.0/mcp-youtube-transcript.mcpb) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 1 | 4 |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | NOASSERTION | MIT |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/jkawamoto/mcp-youtube-transcript |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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
Fetch (Reference)
Fetches a URL from the internet and extracts its contents as markdown.
io.github.jkawamoto/mcp-youtube-transcript
An MCP server retrieving transcripts of YouTube videos
How to run each
Fetch (Reference) As a local MCP server: Docker image
claude mcp add --transport stdio fetch -- docker run -i --rm mcp/fetchio.github.jkawamoto/mcp-youtube-transcript As a local MCP server: Docker image
claude mcp add --transport stdio youtube-transcript -- docker run -i --rm mcp/youtube-transcriptCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Only Fetch (Reference) declares
fetch
Only io.github.jkawamoto/mcp-youtube-transcript declares
get_available_languagesget_timed_transcriptget_transcriptget_video_info
Both declare
None
Tool names as each marketplace publishes them. More tools is not better in itself: compare what each needs for the job.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Fetch (Reference) · What it can do: io.github.jkawamoto/mcp-youtube-transcript · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.