bns-dev vs Yaver
bns-dev is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑20.
bns-dev is a plugin bundle for AI coding tools published by chekos. No marketplace we read lists it any more. Yaver is an MCP server published by kivanccakmak. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-26. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Yaver | |
|---|---|---|
| Community marketplace chekos/bns-marketplace | Removed on 2026-10-20 Version: 0.2.0 Forks (GitHub): 3 Stars (GitHub): 5 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.99.309 Downloads/month (npm): 7 719 Downloads/week (npm): 476 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.99.478 Downloads/month (npm): 7 719 Downloads/week (npm): 476 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
| Fact | bns-devno longer listed · | Yaver |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 5 | 4 |
| Forks (GitHub) (differs) | 3 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (yaver-cli) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/chekos/bns-marketplace | github.com/kivanccakmak/yaver.io |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of bns-dev
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Developer tooling setup and management (SOPS secrets encryption, Claude Code environment setup, multi-ecosystem quality stack for JVM/Node.js/Python, Taskfile task runner setup…
-
Core development tools including quality pipeline, TDD implementation, code review, and refactoring capabilities
-
Enforces worktree + branch + PR pattern for all development. /b:b creates isolated git worktrees, spawns parallel agents for multi-task work, and opens PRs with correct base…
-
Project health and permission management, dev sessions, team updates with feedback triage, GitHub releases, multi-model brains trust, git workflows, UX audits, responsive layout…
-
anthropic-plugin-dev
Plugin development toolkit for hooks, MCP servers, commands, and skills.
-
Build an MCP server and bundle your tools into a shareable plugin, end to end. Two skills: build-mcp scaffolds one server; build-plugin packages skills, hooks, agents, and MCP…
What each says it does
bns-dev
The brasas & nube development plugin. Ships the image-generator skill (Gemini Nano Banana Pro image generation) and the repo-modernization-auditor skill (audit and modernize aging repos to be clean, current, safe, and agent-friendly); home for dev tooling as it emerges.
Yaver
Phone-first local dev MCP for Claude Code and Codex: install Yaver, pair mobile, run, build, deploy.
How to run each
bns-dev
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Yaver As a local MCP server: npm package
claude mcp add --transport stdio yaver -- npx -y yaver-cliCommands 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 bns-dev publish no settings it asks for, so we do not compare settings.
What it can do: bns-dev · 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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.