kit vs ai.yetty/yetty
kit is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
kit is a plugin bundle for AI coding tools published by Miles Zeilstra. No marketplace we read lists it any more. ai.yetty/yetty is an MCP server published by yetty.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  ai.yetty/yetty | |
|---|---|---|
| Community marketplace airmile/claude-kit | Removed on 2026-10-15 Version: 0.9.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.0 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
| Fact | kitno longer listed · | ai.yetty/yetty |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.yetty.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 18 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/airmile/claude-kit | github.com/avniy/yetty-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
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 kit
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Five practical skills covering the domains developers most often Google when shipping a website. Each skill auto-loads only when relevant to the task: Web Accessibility on UI…
-
Web development tools including frontend design workflows
-
SEO/GEO 2026 plugin: technical SEO, schema markup, E-E-A-T, AI Overviews/ChatGPT/Perplexity optimization, local SEO, sitemaps, hreflang, internal linking, semantic clustering…
-
All CCG skills in one install: bt-panel / seo-page-builder / adsense-site-auditor / scrapling, the verify-* quality gates + gen-docs, the Impeccable-fused frontend-design skill…
-
Verification-gated website launch system: 14-phase checklist (Done ≠ Verified), refuse-to-launch sign-off gate, Day 1/3/7/14/30 monitoring cadence, an anonymized failure-mode…
-
Insights, experimentation and personalization for WordPress. Self-learning loops to automatically iterate on content.
What each says it does
kit
Minimal dev workflow: roadmap, build, launch, commit, convert, seo
ai.yetty/yetty
Build, edit and run real hosted websites from your AI - content, SEO, menus, store, rollback.
How to run each
kit
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
ai.yetty/yetty As a remote MCP server
claude mcp add --transport http yetty https://mcp.yetty.ai/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only ai.yetty/yetty 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: kit · What it can do: ai.yetty/yetty · 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.