clover vs Inspectrum
clover is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
clover is a plugin bundle for AI coding tools published by Clover Security. No marketplace we read lists it any more. Inspectrum is an MCP server published by yannmenec. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 |  Inspectrum | |
|---|---|---|
| Community marketplace clover-security-public/clover-claude-plugin | Removed on 2026-10-15 Version: 0.1.82 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.3 Downloads/month (npm): 208 Downloads/week (npm): 51 Forks (GitHub): 1 Stars (GitHub): 2 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 | cloverno longer listed · | Inspectrum |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 0 | 2 |
| Forks (GitHub) (differs) | 0 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (inspectrum) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/clover-security-public/clover-claude-plugin | github.com/yannmenec/inspectrum |
| Changes in the last 7 days | 4 | 4 |
| 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 clover
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Protect your coding agent experience — Clover silently threat-models every plan, surfaces missing security requirements, and folds them in before code is written.
-
Open-source Claude Code plugins for multi-agent software delivery. Plan-first SDLC workflow, code review, LLM quality judges, and self-learning — grounded in your codebase…
-
Automated code review for codebase using multiple specialized agents.
-
Engineering standards and code governance enforcement with parallel agent execution for code reviews, commits, and standards audits.
-
stetkeep stops Claude from refactoring code that's intentionally the way it is. Two pillars: 1) XML-structured behavior protocols (BRAIN/CRAFT/PERF, ~1.8K tokens each) encode…
-
suede-code
Code quality subset: one-pass review plus an A-F ship verdict (suede-code), deep findings with TypeScript, React, Next.js, OWASP, and database checklists (suede-code-review), a…
What each says it does
clover
Ship secure code at agent speed. Clover silently reviews every plan, surfaces missing security requirements, and folds them into the work before a single line is written — no questions, no detours.
Inspectrum
Review coding-agent plans on demand with peer models, attributed findings, and a structured verdict.
How to run each
clover
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Inspectrum As a local MCP server: npm package
claude mcp add --transport stdio inspectrum -- npx -y inspectrumCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: clover · What it can do: Inspectrum · 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.