Ext Ops Panel
Open dashboard
Comparison

Wayfound vs com.vibsync/vibsync

Wayfound is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). com.vibsync/vibsync is an MCP server published by vibsync.com. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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
MarketplaceWayfoundcom.vibsync/vibsync
Docker MCP Catalog Listed
Version: not stated
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.3
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

Wayfound vs com.vibsync/vibsync
FactWayfoundcom.vibsync/vibsync
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (app.wayfound.ai/sse)Remote server (mcp.vibsync.com/mcp)
Transport (differs)SSEStreamable HTTP
Tools it declares (differs)4Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Apache-2.0MIT
Repository (differs)Not statedgithub.com/loosedays/vibsync-mcp
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetResponded 10 h ago, requires a key

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

Wayfound

In its own words, on Docker MCP Catalog:

Wayfound’s MCP server allows business users to govern, supervise, and improve AI Agents.

com.vibsync/vibsync

In its own words, on Official MCP Registry:

One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.

How to run each

Wayfound As a remote MCP server

Claude Code
claude mcp add --transport sse wayfound https://app.wayfound.ai/sse

Requires: MCP_API_KEY (secret)

com.vibsync/vibsync As a remote MCP server

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

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

Only com.vibsync/vibsync has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of com.vibsync/vibsync publish no list of tools, so we do not compare tools.

Settings each asks for

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

What it can do: Wayfound · What it can do: com.vibsync/vibsync · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. 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