clover vs SonarQube MCP Server
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. SonarQube MCP Server is an MCP server published by SonarSource. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-25. 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 |  SonarQube MCP Server | |
|---|---|---|
| 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: 1.30.0 Forks (GitHub): 103 Stars (GitHub): 671 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:925c88bc7cab Forks (GitHub): 103 Pulls (Docker Hub): 1 585 128 Stars (Docker Hub): 23 Stars (GitHub): 671 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 · | SonarQube MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 0 | 671 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 1 585 128 |
| Forks (GitHub) (differs) | 0 | 103 |
| Last release (differs) | Not published | 2026-10-23 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (docker.io/sonarsource/sonarqube-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 25 |
| Environment variables it asks for (differs) | Not published | 3, secrets among them: 3 |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | Not stated | NOASSERTION |
| Repository (differs) | github.com/clover-security-public/clover-claude-plugin | github.com/sonarsource/sonarqube-mcp-server |
| Changes in the last 7 days (differs) | 0 | 1 |
| 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.
-
DevsForge Enterprise Code Quality Architect delivering comprehensive code governance methodologies, quality assurance frameworks, and security optimization strategies that…
-
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…
-
Engineering standards and code governance enforcement with parallel agent execution for code reviews, commits, and standards audits.
-
suede-code
Code quality subset: one-pass review and A-F ship verdict with TypeScript, React, Next.js, OWASP, and database checklists, plus findings-only and grade-only modes (suede-code…
-
Host-side gauntlet for fetching, scanning, and sanitizing untrusted repositories before any agent, editor, or toolchain opens them.
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.
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
How to run each
clover
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
SonarQube MCP Server As a local MCP server: Docker image
claude mcp add --env "SONARQUBE_ORG=<YOUR_SONARQUBE_ORG>" --env "SONARQUBE_TOKEN=<YOUR_SONARQUBE_TOKEN>" --env "SONARQUBE_URL=<YOUR_SONARQUBE_URL>" --transport stdio sonarqube-mcp-server -- docker run -i --rm -e SONARQUBE_ORG -e SONARQUBE_TOKEN -e SONARQUBE_URL docker.io/sonarsource/sonarqube-mcpRequires: SONARQUBE_ORG (secret), SONARQUBE_TOKEN (secret), SONARQUBE_URL (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of clover publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of clover publish no settings it asks for, so we do not compare settings.
What it can do: clover · What it can do: SonarQube MCP Server · 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. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.