Ext Ops Panel
Open dashboard
Comparison

viral-launch-pipeline vs SocialGPT

viral-launch-pipeline is a plugin bundle for AI coding tools published by Koz-TV. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SocialGPT is an MCP server published by scrollmark. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplaceviral-launch-pipelineSocialGPT
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 1
Stars (GitHub): 10
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

viral-launch-pipeline vs SocialGPT
Factviral-launch-pipelineSocialGPT
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)10 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.gpt.social/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/koz-tv/viral-launch-pipelinegithub.com/scrollmark/socialgpt-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 3 h 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

viral-launch-pipeline

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

A 21-agent orchestrator for viral product launches. One skill coordinates parallel web research (YouTube, X, Reddit, industry), manager-critiqued hook and giveaway writing, a body specialist chain (weapons, controversy, technical, flow), a Mom Test for mass-market readability, and multi-channel delivery (X-thread, LinkedIn post, ProductHunt copy). Manager loops force rewrites until the rubric passes, with a full paper trail and resumable state.

SocialGPT

In its own words, on Official MCP Registry:

Social media analytics, video analysis, and competitor intel for any MCP-compatible AI agent.

How to run each

viral-launch-pipeline As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install viral-launch-pipeline@claude-community

SocialGPT As a remote MCP server

Claude Code
claude mcp add --transport http socialgpt https://mcp.gpt.social/mcp

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

Only SocialGPT 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: viral-launch-pipeline · What it can do: SocialGPT · 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