brents-toasts vs Yaver
brents-toasts is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
brents-toasts is a plugin bundle for AI coding tools published by Brentspine. 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-28. 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 | ||
|---|---|---|
| Community marketplace brentspine/brents-toasts | Removed on 2026-10-27 Version: not stated Forks (GitHub): 3 Stars (GitHub): 11 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 | brents-toastsno longer listed · | Yaver |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 11 | 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 |
| Licence | Apache-2.0 | Apache-2.0 |
| Repository (differs) | github.com/brentspine/brents-toasts | github.com/kivanccakmak/yaver.io |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 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 brents-toasts
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Pre-built animated React component collections combining Magic UI (150+ TypeScript/Tailwind/Motion components) and React Bits (90+ minimal-dependency animated components). Use…
-
Search, compare, compose, and install free source-backed React UI from Watermelon.
-
MCP server for UI Beats. Let your coding agent search, read and install animated React components.
-
Build complex HTML artifacts (React, Tailwind, shadcn/ui) with state management for inline rendering in Claude
-
AI assistant skills that guide Claude to add product tours, onboarding flows, hints, checklists, announcements, and adoption tracking to React/Next.js apps using @tour-kit/* npm…
-
Reusable UI component patterns - version badge, tooltips, and common UI elements for React, Vue, Svelte
What each says it does
brents-toasts
Claude Skill for writing correct code against brents-toasts, a zero-dependency toast/snackbar UI library.
Yaver
Phone-first local dev MCP for Claude Code and Codex: install Yaver, pair mobile, run, build, deploy.
How to run each
brents-toasts
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-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 brents-toasts publish no settings it asks for, so we do not compare settings.
What it can do: brents-toasts · 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.