ReVa vs SonarQube MCP Server
ReVa is a plugin bundle for AI coding tools published by CyberKaida. Marketplaces we read that list it: 1 (Community GitHub marketplaces). 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-20. 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 |  SonarQube MCP Server | |
|---|---|---|
| Community marketplace cyberkaida/reverse-engineering-assistant | Listed Version: 0.1.0 Forks (GitHub): 85 Stars (GitHub): 879 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.21.0 Forks (GitHub): 105 Stars (GitHub): 665 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:925c88bc7cab Forks (GitHub): 105 Pulls (Docker Hub): 1 553 038 Stars (Docker Hub): 23 Stars (GitHub): 665 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 | ReVa | SonarQube MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 879 (better) | 665 (worse) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 1 553 038 |
| Forks (GitHub) (differs) | 85 (worse) | 105 (better) |
| Last release | Not published | Not published |
| 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) | 1, secrets among them: 0 | 3, secrets among them: 3 |
| Parts of the bundle (differs) | 7 | Not a bundle |
| Licence (differs) | Not stated | NOASSERTION |
| Repository (differs) | github.com/cyberkaida/reverse-engineering-assistant | github.com/sonarsource/sonarqube-mcp-server |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-15 | 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
ReVa
AI-assisted binary analysis and reverse engineering with Ghidra integration
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
How to run each
ReVa As a Claude Code plugin
/plugin marketplace add cyberkaida/reverse-engineering-assistant
/plugin install ReVa@revaSonarQube 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 ReVa publish no list of tools, so we do not compare tools.
Settings each asks for
Only ReVa asks for
UV_WORKING_DIRECTORY
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: ReVa · 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.