Ext Ops Panel
Open dashboard
Comparison

vibiz vs GrowSurf

vibiz is a plugin bundle for AI coding tools published by Vibiz-ai. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). GrowSurf is an MCP server published by growsurf.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-05. 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
MarketplacevibizGrowSurf
Claude Code: claude-plugins-community Listed
Version: 64ff911
Forks (GitHub): 2
Stars (GitHub): 7
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.19.28
Downloads/month (npm): 3 609
Downloads/week (npm): 419
Forks (GitHub): 1
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.19.28
Downloads/month (npm): 3 609
Downloads/week (npm): 419
Forks (GitHub): 1
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

vibiz vs GrowSurf
FactvibizGrowSurf
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)7 (better)0 (worse)
Forks (GitHub) (differs)2 (better)1 (worse)
Last release (differs)Not published2026-11-04
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)github.com/vibiz-ai/vibiz-claude-plugingithub.com/growsurf/growsurf-mcp
Changes in the last 7 days (differs)07
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 4 days ago returned HTTP 200

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

vibiz

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

Generate ads, funnels, ICPs, social posts, and full Meta campaigns from inside Claude Code. Drafts a marketing post about every commit you make.

GrowSurf

In its own words, on Official MCP Registry:

Build and manage GrowSurf referral and affiliate programs through AI assistants.

How to run each

vibiz As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vibiz@claude-community

GrowSurf As a remote MCP server

Claude Code
claude mcp add --transport http growsurf https://mcp.growsurf.com

Requires: GROWSURF_API_KEY (secret)

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

Only GrowSurf 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

The marketplaces of vibiz publish no settings it asks for, so we do not compare settings.

What it can do: vibiz · What it can do: GrowSurf · 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. Package data comes from the public npm registry (registry.npmjs.org). 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