Ext Ops Panel
Open dashboard
Comparison

com.vibsync/vibsync vs io.github.keshrath/agent-knowledge

com.vibsync/vibsync is an MCP server published by vibsync.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.keshrath/agent-knowledge is an MCP server published by keshrath. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-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

Where each is published
Marketplacecom.vibsync/vibsyncio.github.keshrath/agent-knowledge
Official MCP Registry Listed
Version: 0.2.3
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.9.8
Downloads/month (npm): 1 018
Downloads/week (npm): 201
Forks (GitHub): 2
Stars (GitHub): 18
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.9.3
Forks (GitHub): 2
Stars (GitHub): 18
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

com.vibsync/vibsync vs io.github.keshrath/agent-knowledge
Factcom.vibsync/vibsyncio.github.keshrath/agent-knowledge
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)0 (worse)18 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.vibsync.com/mcp)On your machine (agent-knowledge)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle2
LicenceMITMIT
Repository (differs)github.com/loosedays/vibsync-mcpgithub.com/keshrath/agent-knowledge
Changes in the last 7 days (differs)42
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days ago, requires a keyno remote endpoint we check

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

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.

io.github.keshrath/agent-knowledge

In its own words, on Official MCP Registry:

Cross-session memory for AI agents - knowledge graph, scoring, semantic search

How to run each

com.vibsync/vibsync As a remote MCP server

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

io.github.keshrath/agent-knowledge As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-knowledge -- npx -y agent-knowledge

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: com.vibsync/vibsync · What it can do: io.github.keshrath/agent-knowledge · Compare two other plugins

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. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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