Jarroba Tools · Test audit vs SonarQube MCP Server
Jarroba Tools · Test audit is an MCP server published by Invarato. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). 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-28. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Jarroba Tools · Test audit |  SonarQube MCP Server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 Downloads/month (npm): 1 284 Downloads/week (npm): 248 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.30.0 Forks (GitHub): 102 Stars (GitHub): 674 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.3.0 Downloads/month (npm): 1 284 Downloads/week (npm): 248 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Docker MCP Catalog | Not listed | Listed Version: sha256:925c88bc7cab Forks (GitHub): 102 Pulls (Docker Hub): 1 603 973 Stars (Docker Hub): 23 Stars (GitHub): 674 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 | Jarroba Tools · Test audit | SonarQube MCP Server |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 0 (worse) | 674 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 1 603 973 |
| Forks (GitHub) (differs) | 0 (worse) | 102 (better) |
| Last release (differs) | 2026-10-27 (better) | 2026-10-23 (worse) |
| Where it runs (differs) | On your machine (@jarroba/mcp-tests) | On your machine (docker.io/sonarsource/sonarqube-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | Not published | 25 |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 3, secrets among them: 3 |
| Licence (differs) | MIT | NOASSERTION |
| Repository (differs) | github.com/invarato/jarroba-mcp | github.com/sonarsource/sonarqube-mcp-server |
| Changes in the last 7 days (differs) | 6 | 1 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Jarroba Tools · Test audit
Audits tests instead of writing them: what each one really asserts. 4 tools, local.
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
How to run each
Jarroba Tools · Test audit As a local MCP server: npm package
claude mcp add --transport stdio jarroba-tools-tests -- npx -y @jarroba/mcp-testsSonarQube 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 Jarroba Tools · Test audit publish no list of tools, so we do not compare tools.
Settings each asks for
Only Jarroba Tools · Test audit asks for
JARROBA_MCP_DOMAINS
Only SonarQube MCP Server asks for
SONARQUBE_ORG (secret)SONARQUBE_TOKEN (secret)SONARQUBE_URL (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Jarroba Tools · Test audit · What it can do: SonarQube MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.