Ext Ops Panel
Open dashboard
Comparison

vibecircle vs app.goshipyard/shipyard

vibecircle is a plugin bundle for AI coding tools published by miltonian. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). app.goshipyard/shipyard is an MCP server published by goshipyard.app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacevibecircleapp.goshipyard/shipyard
Claude Code: claude-plugins-community Listed
Version: bf8b30f
Forks (GitHub): 2
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
No figure published
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

vibecircle vs app.goshipyard/shipyard
Factvibecircleapp.goshipyard/shipyard
Marketplaces that list it11
Stars (GitHub) (differs)4No figure on GitHub
Forks (GitHub) (differs)2No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (goshipyard.app/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/miltonian/vibecirclegithub.com/jonnonz1/shipyard
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 6 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

vibecircle

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

See what your friends are building. A social feed for friend groups who vibe code — share screenshots, deploy links, and coding activity with your circle. Features: auto-capture from Claude Code via /share command, live app embeds, reactions and comments, ambient presence (see who's building right now), and AI-powered project explanations (BYOK). Includes /circle setup for zero-friction device code authentication, and /share for posting updates. Open source, MIT licensed.

app.goshipyard/shipyard

In its own words, on Official MCP Registry:

Ship, discover and review vibe-coded projects on Shipyard, the invite-only feed for AI-built apps.

How to run each

vibecircle As a Claude Code plugin

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

app.goshipyard/shipyard As a remote MCP server

Claude Code
claude mcp add --transport http shipyard https://goshipyard.app/mcp

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

Only app.goshipyard/shipyard 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: vibecircle · What it can do: app.goshipyard/shipyard · 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