Ext Ops Panel
Open dashboard
Comparison

versori-skills vs com.vibsync/vibsync

versori-skills is a plugin bundle for AI coding tools published by versori. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-14. 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
Marketplaceversori-skillscom.vibsync/vibsync
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 12
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

versori-skills vs com.vibsync/vibsync
Factversori-skillscom.vibsync/vibsync
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)12 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (mcp.vibsync.com/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)12
Licence (differs)Not statedMIT
Repository (differs)github.com/versori/cligithub.com/loosedays/vibsync-mcp
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 34 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

versori-skills

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

The versori-skills plugin gives Claude Code the ability to create, build, deploy, and monitor production-grade data integrations, entirely from the command line. Rather than stitching together simple automations, Versori enables Claude to build complex, multi-workflow integrations with full TypeScript control using the versori-run SDK. The plugin follows a research-first approach: before writing any code, Claude gathers and structures API documentation for each system involved, producing a grounded research document that becomes the single source of truth for the integration. This ensures generated code is accurate and well-informed rather than hallucinated. From there, Claude manages the full integration lifecycle: bootstrapping projects, configuring systems and connections, generating type-safe TypeScript workflows, running local validation via Deno, and deploying to production with built-in safety checks like dry-run previews and project context validation. Key features: - Research-grounded code generation

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

versori-skills As a Claude Code plugin

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

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

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: versori-skills · What it can do: com.vibsync/vibsync · 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. 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