SonarQube MCP Server vs bouncer
SonarQube MCP Server is an MCP server published by SonarSource. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). bouncer is an MCP server published by nugehs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-09. 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 |  bouncer |
|---|---|---|
| Official MCP Registry | Listed Version: 1.31.0 Forks (GitHub): 103 Stars (GitHub): 681 Not marked · First seen |
Listed Version: 0.3.0 Downloads/month (npm): 1 359 Downloads/week (npm): 129 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:925c88bc7cab Forks (GitHub): 103 Pulls (Docker Hub): 1 680 264 Stars (Docker Hub): 23 Stars (GitHub): 681 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 0.3.0 Downloads/month (npm): 1 359 Downloads/week (npm): 129 Forks (GitHub): 0 Stars (GitHub): 1 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 | SonarQube MCP Server | bouncer |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 681 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 1 680 264 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 103 (better) | 0 (worse) |
| Last release (differs) | 2026-11-02 (better) | 2026-10-14 (worse) |
| Where it runs (differs) | On your machine (docker.io/sonarsource/sonarqube-mcp) | On your machine (@nugehs/bouncer) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 25 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 3 | Not published |
| Licence (differs) | NOASSERTION | MIT |
| Repository (differs) | github.com/sonarsource/sonarqube-mcp-server | github.com/nugehs/bouncer |
| Changes in the last 7 days | 0 | 0 |
| 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
SonarQube MCP Server
Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.
bouncer
Static compliance-controls checker for UK Online Safety Act & ICO Children's Code. CLI + MCP.
How to run each
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)
bouncer As a local MCP server: npm package
claude mcp add --transport stdio bouncer -- npx -y @nugehs/bouncer mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of bouncer publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of bouncer publish no settings it asks for, so we do not compare settings.
What it can do: SonarQube MCP Server · What it can do: bouncer · Compare two other plugins
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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.