Ext Ops Panel
Open dashboard
Comparison

io.github.leekung125/web-data-toolkit vs io.github.mrslbt/rippr-mcp

io.github.leekung125/web-data-toolkit is an MCP server published by leekung125. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.mrslbt/rippr-mcp is an MCP server published by mrslbt. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. 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
Marketplaceio.github.leekung125/web-data-toolkitio.github.mrslbt/rippr-mcp
Official MCP Registry Listed
Version: 1.2.0
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.3.0
Downloads/month (npm): 208
Downloads/week (npm): 19
Forks (GitHub): 0
Stars (GitHub): 4
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

io.github.leekung125/web-data-toolkit vs io.github.mrslbt/rippr-mcp
Factio.github.leekung125/web-data-toolkitio.github.mrslbt/rippr-mcp
Marketplaces that list it11
Stars (GitHub) (differs)1 (worse)4 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (web-data-toolkit.vercel.app/mcp)On your machine (rippr-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/leekung125/web-data-toolkit-mcpgithub.com/mrslbt/rippr
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 45 h agono remote endpoint we check

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

io.github.leekung125/web-data-toolkit

In its own words, on Official MCP Registry:

YouTube transcripts (video, channel, search), Google Trends, Google Play and App Store reviews.

io.github.mrslbt/rippr-mcp

In its own words, on Official MCP Registry:

Rip YouTube transcripts to disk for AI agents, RAG pipelines, and LLM workflows.

How to run each

io.github.leekung125/web-data-toolkit As a remote MCP server

Claude Code
claude mcp add --transport http web-data-toolkit https://web-data-toolkit.vercel.app/mcp --header "x-api-key: <YOUR_X_API_KEY>"

Requires: x-api-key header

io.github.mrslbt/rippr-mcp As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio rippr-mcp -- npx -y rippr-mcp

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

Only io.github.leekung125/web-data-toolkit 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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.leekung125/web-data-toolkit · What it can do: io.github.mrslbt/rippr-mcp · 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.

Where the data comes from: how the catalog is built