Ext Ops Panel
Open dashboard
Comparison

kibi-zcode vs Yaver

kibi-zcode is a plugin bundle for AI coding tools published by looted. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Yaver is an MCP server published by kivanccakmak. Marketplaces we read that list it: 2 (Official MCP Registry, 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
Marketplacekibi-zcodeYaver
Community marketplace looted/kibi Listed
Version: not stated
Forks (GitHub): 2
Stars (GitHub): 10
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.99.309
Downloads/month (npm): 9 098
Downloads/week (npm): 2 402
Forks (GitHub): 1
Stars (GitHub): 4
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

kibi-zcode vs Yaver
Factkibi-zcodeYaver
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)10 (better)4 (worse)
Forks (GitHub) (differs)2 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (yaver-cli)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Hooks it runs (differs)5Not published
Parts of the bundle (differs)102
Licence (differs)Not statedFSL-1.1-Apache-2.0
Repository (differs)github.com/looted/kibigithub.com/kivanccakmak/yaver.io
Changes in the last 7 days (differs)42
First seen (differs)2026-10-132026-10-11

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

kibi-zcode

In its own words, on Community GitHub marketplaces:

Kibi ZCode plugin: bundled Kibi skills, a kibi-bootstrap command, advisory lifecycle hooks, and the workspace-gated Kibi MCP server.

Yaver

In its own words, on Official MCP Registry:

Phone-first local dev MCP for Claude Code and Codex: install Yaver, pair mobile, run, build, deploy.

How to run each

kibi-zcode As a Claude Code plugin

Claude Code
/plugin marketplace add looted/kibi
/plugin install kibi-zcode@kibi

Yaver As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio yaver -- npx -y yaver-cli

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

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 kibi-zcode publish no settings it asks for, so we do not compare settings.

What it can do: kibi-zcode · What it can do: Yaver · 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. 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