SonarQube MCP Server vs Dependency check
SonarQube MCP Server is an MCP server published by SonarSource. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). Dependency check is an MCP server published by ladanyin. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-08. 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 |  Dependency check |
|---|---|---|
| Official MCP Registry | Listed Version: 1.31.0 Forks (GitHub): 103 Stars (GitHub): 680 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:925c88bc7cab Forks (GitHub): 103 Pulls (Docker Hub): 1 677 149 Stars (Docker Hub): 23 Stars (GitHub): 680 Not marked · First seen |
Not listed |
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 | Dependency check |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 680 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 1 677 149 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 103 (better) | 0 (worse) |
| Last release (differs) | 2026-11-02 | Not published |
| Where it runs (differs) | On your machine (docker.io/sonarsource/sonarqube-mcp) | Remote server (deps.bestsmartgoods.com/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 25 | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 3 | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/sonarsource/sonarqube-mcp-server | github.com/ladanyin/agentlane |
| Changes in the last 7 days (differs) | 1 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-05 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 404 (28 h ago) |
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.
Dependency check
Check a package version for known vulnerabilities and Packagist release facts.
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)
Dependency check As a remote MCP server
claude mcp add --transport http dependency-check https://deps.bestsmartgoods.com/mcp --header "X-API-Key: <YOUR_X_API_KEY>"Requires: X-API-Key header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Dependency check has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Dependency check publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Dependency check publish no settings it asks for, so we do not compare settings.
What it can do: SonarQube MCP Server · What it can do: Dependency check · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.