visibility vs GrowSurf
visibility is a plugin bundle for AI coding tools published by OrenSegal. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-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 |  visibility |   GrowSurf |
|---|---|---|
| Community marketplace davepoon/buildwithclaude | Listed Version: 0.2.1 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.19.33 Downloads/month (npm): 3 095 Downloads/week (npm): 1 614 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.19.33 Downloads/month (npm): 3 095 Downloads/week (npm): 1 614 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
| Fact | visibility | GrowSurf |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release (differs) | Not published | 2026-11-13 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 1 |
| Parts of the bundle (differs) | 4 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/orensegal/visibility | github.com/growsurf/growsurf-mcp |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-11-13 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 10 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
visibility
Plan and run listings for a project on marketplaces and directories, from a catalog of 98 platforms and paying channels. plan scans for listable assets and ranks where the project fits; register walks one platform; build makes the one missing asset; monetize ranks the channels that pay. README text, docs, landing pages and submission pages are treated as data; a page that differs from the catalog is shown to the user and waited on. Every publish, push, PR or package install waits for a yes, and installs use exact pinned versions; accounts, payment, DNS and form submissions stay with the user.
GrowSurf
Build and manage GrowSurf referral and affiliate programs through AI assistants.
How to run each
visibility As a Claude Code plugin
/plugin marketplace add davepoon/buildwithclaude
/plugin install visibility@buildwithclaudeGrowSurf As a remote MCP server
claude mcp add --transport http growsurf https://mcp.growsurf.comRequires: 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 visibility publish no settings it asks for, so we do not compare settings.
What it can do: visibility · What it can do: GrowSurf · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.