Ext Ops Panel
Open dashboard
Comparison

SonarQube MCP Server vs io.github.tiluckdave/hound

SonarQube MCP Server is an MCP server published by SonarSource. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). io.github.tiluckdave/hound is an MCP server published by tiluckdave. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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

Where each is published
MarketplaceSonarQube MCP Serverio.github.tiluckdave/hound
Official MCP Registry Listed
Version: 1.21.0
Forks (GitHub): 104
Stars (GitHub): 669
Not marked · First seen
Listed
Version: 0.2.1
Downloads/month (npm): 207
Downloads/week (npm): 29
Forks (GitHub): 20
Stars (GitHub): 17
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:925c88bc7cab
Forks (GitHub): 104
Pulls (Docker Hub): 1 573 519
Stars (Docker Hub): 23
Stars (GitHub): 669
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

SonarQube MCP Server vs io.github.tiluckdave/hound
FactSonarQube MCP Serverio.github.tiluckdave/hound
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)669 (better)17 (worse)
Pulls (Docker Hub) (differs)1 573 519No figure on Docker Hub
Forks (GitHub) (differs)104 (better)20 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (docker.io/sonarsource/sonarqube-mcp)On your machine (hound-mcp)
Transportstdiostdio
Tools it declares (differs)25Not published
Environment variables it asks for (differs)3, secrets among them: 3Not published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/sonarsource/sonarqube-mcp-servergithub.com/tiluckdave/hound-mcp
Changes in the last 7 days00
First seen2026-10-112026-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

In its own words, on Official MCP Registry:

Analyze code quality and security with SonarQube Server or Cloud directly in AI assistants.

io.github.tiluckdave/hound

In its own words, on Official MCP Registry:

The dependency bloodhound for AI coding agents. Zero API keys, zero config.

How to run each

SonarQube MCP Server As a local MCP server: Docker image

Claude Code
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-mcp

Requires: SONARQUBE_ORG (secret), SONARQUBE_TOKEN (secret), SONARQUBE_URL (secret)

io.github.tiluckdave/hound As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio hound -- npx -y hound-mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

The marketplaces of io.github.tiluckdave/hound publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.tiluckdave/hound publish no settings it asks for, so we do not compare settings.

What it can do: SonarQube MCP Server · What it can do: io.github.tiluckdave/hound · 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.

Where the data comes from: how the catalog is built