kit vs HefestoAI
kit is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑27.
kit is a plugin bundle for AI coding tools published by Dwarves Foundation. No marketplace we read lists it any more. HefestoAI is an MCP server published by artvepa80. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  HefestoAI | |
|---|---|---|
| Community marketplace dwarvesf/dwarves-kit | Removed on 2026-10-27 Version: 2.3.0 Forks (GitHub): 2 Stars (GitHub): 12 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.20.3 Forks (GitHub): 2 Stars (GitHub): 7 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 · | HefestoAI |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 12 | 7 |
| Forks (GitHub) | 2 | 2 |
| Last release (differs) | Not published | 2026-10-24 |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (hefestoai.narapallc.com/api/mcp-protocol) |
| 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) | 27 | Not published |
| Parts of the bundle (differs) | 93 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dwarvesf/dwarves-kit | github.com/artvepa80/agents-hefesto |
| Changes in the last 7 days (differs) | 3 | 1 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 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.
-
Never re-explain your project to Claude again. devpace remembers context across sessions, manages requirement changes, and ensures quality gates — all automatically. Zero setup…
-
Reliability hooks for Claude Code - prevents common mistakes, enforces quality standards, blocks --no-verify, and runs automated code review
-
Spec-driven development framework for Claude Code. Manages the propose → plan → build → verify → pr lifecycle with structured proposals, specs, designs, task lists, and…
-
Full-stack engineering ops for Claude Code. One command (/prodmasterai) covers your entire dev lifecycle: orchestrate features into parallel tasks, run 11-phase QA with health…
-
Analyze codebases and recommend tailored Claude Code automations such as hooks, skills, MCP servers, and subagents.
-
Software engineering workflows with skills for planning, implementation, quality review, and structured thinking, plus a suite of specialist agents
What each says it does
kit
Spec-driven Claude Code workflow with verification pipeline. Hooks, slash commands, and verification subagents.
HefestoAI
HefestoAI checks AI-generated code before you ship it.
How to run each
kit
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
HefestoAI As a remote MCP server
claude mcp add --transport http hefestoai https://hefestoai.narapallc.com/api/mcp-protocolCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only HefestoAI has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of kit nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: kit · What it can do: HefestoAI · 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.