Ext Ops Panel
Open dashboard
Comparison

open-source-launch vs npm Trends MCP

open-source-launch is a plugin bundle for AI coding tools published by OMARVII. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). npm Trends MCP is an MCP server published by trendsmcp.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
Marketplaceopen-source-launchnpm Trends MCP
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.7
Forks (GitHub): 0
Stars (GitHub): 0
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

open-source-launch vs npm Trends MCP
Factopen-source-launchnpm Trends MCP
Marketplaces that list it11
Stars (GitHub) (differs)3 (better)0 (worse)
Forks (GitHub)00
Last release (differs)Not published2026-10-21
Where it runs (differs)Installs as a plugin bundleRemote server (npm.api.trendsmcp.ai/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/omarvii/open-source-launch-skillgithub.com/trendsmcp-ai/npm-trends-mcp
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 2 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

open-source-launch

In its own words, on Claude Code: claude-plugins-community:

A portable launch-readiness skill that helps maintainers prepare open-source repositories for a clear, trusted public launch. It audits the README, first-run path, proof/demo, metadata, security surface, release hygiene, launch channels, launch copy, and follow-up plan, then reports evidence-backed code blockers, account/platform blockers, and launch blockers.

npm Trends MCP

In its own words, on Official MCP Registry:

npm package trends and weekly downloads over time. Free key at trendsmcp.ai

How to run each

open-source-launch As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install open-source-launch@claude-community

npm Trends MCP As a remote MCP server

Claude Code
claude mcp add --transport http npm https://npm.api.trendsmcp.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only npm Trends MCP 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: open-source-launch · What it can do: npm Trends MCP · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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