system-doctor vs SonarQube MCP Server
system-doctor is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
system-doctor is a plugin bundle for AI coding tools published by Alexandre Mallet. 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-26. 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 buldee/claude-system-doctor | Removed on 2026-10-15 Version: 0.7.0 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): 673 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:925c88bc7cab Forks (GitHub): 103 Pulls (Docker Hub): 1 596 021 Stars (Docker Hub): 23 Stars (GitHub): 673 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 | system-doctorno longer listed · | SonarQube MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 0 | 673 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 1 596 021 |
| 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 |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence (differs) | Not stated | NOASSERTION |
| Repository (differs) | github.com/buldee/claude-system-doctor | 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 system-doctor
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Frictionless security, compliance, and threat detection for Claude Code and Co-Work. Advanced Behavioral detection patterns catch credential exfiltration, reverse shells, prompt…
-
Audit and govern your Claude Code configuration and file-based memory via the Agent Monitor Config Explorer API — skills, subagents, commands, MCP servers, hooks, settings, and…
-
Meta-tools for running Claude Code well: audit your permission allowlist, fix local toolchain gaps, analyze usage costs, and prune stale saved memories.
-
Developer tools for Claude Code Agent Monitor — session debugging, hook diagnostics, data export, and system health checks for maintaining a healthy monitoring setup.
-
A Laravel toolkit for Claude Code with 27 skills across 9 categories: database migration consolidation, model analysis, N+1 detection, security audits, Livewire/Blade auditing…
-
Aikido Security scanning for Claude Code — SAST, secrets, and IaC vulnerability detection powered by the Aikido MCP server.
What each says it does
system-doctor
Scheduled audit and safe auto-heal for your Claude Code installation.
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
How to run each
system-doctor
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 system-doctor publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of system-doctor publish no settings it asks for, so we do not compare settings.
What it can do: system-doctor · 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.