Sonar MCP Server
OCI · GHCR.IO/IGOROLV/SONAR-MCP-SERVER:0.1.0
Read-only SonarQube Community Build access for AI agents: issues, hotspots, rules, code snippets
Available components
Last scanned (21 hours ago)
Scores higher than 81% of OCI servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 47 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2647 tokens (~203/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −6
- Stability: pass → 0.57 functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed oci/ghcr.io/igorolv/sonar-mcp-server:0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
getHotspot ~41
Get one Security Hotspot. Returns review details, rule guidance, locations, flows, and changelog.
| Name | Type | Req | Description |
|---|---|---|---|
| hotspotKey | string | yes | Hotspot key |
| Name | Type | Req | Description |
|---|---|---|---|
| changelog | array|null | – | Full change history of the hotspot (reviews, reassignments, etc.). |
| flows | array|null | – | Data-flow paths showing how user input reaches the risky code. |
| hotspot | – | – | – |
| rule | – | – | – |
| textRange | – | – | Precise text range in the source file; null when the hotspot spans the whole file. |
No examples provided.
getIssue ~165
Get one issue by key. Returns full issue details and changelog, including status and assignment history. Scope explicitly: omitting both `branch` and `pullRequest` uses the configured default (usually main). For non-main or PR work, pass the matching ref explicitly; discover it with `listProjectBranches` / `listProjectPullRequests`.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name; mutually exclusive with `pullRequest`. Omission uses the configured default (usually main). For non-main lookup, pass explicitly; use `listProjectBranches` to discover names. |
| issueKey | string | yes | Issue key |
| pullRequest | string | – | PR key; mutually exclusive with `branch`; no default. For PR work, pass explicitly; use `listProjectPullRequests`. |
| Name | Type | Req | Description |
|---|---|---|---|
| changelog | array|null | – | Full change history of the issue (transitions, assignments, severity changes, etc.). |
| issue | – | – | – |
No examples provided.
getIssueSnippets ~193
Get Sonar-analysed source snippets for all issue locations, including cross-file flows. Returns component path, language, code lines, and SCM metadata. Use when local source is unavailable or may differ from the analysed ref. Scope explicitly: omitting both `branch` and `pullRequest` uses the configured default (usually main). For non-main or PR work, pass the matching ref explicitly; discover it with `listProjectBranches` / `listProjectPullRequests`.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name; mutually exclusive with `pullRequest`. Omission uses the configured default (usually main). For non-main lookup, pass explicitly; use `listProjectBranches` to discover names. |
| issueKey | string | yes | Issue key |
| pullRequest | string | – | PR key; mutually exclusive with `branch`; no default. For PR work, pass explicitly; use `listProjectPullRequests`. |
| Name | Type | Req | Description |
|---|---|---|---|
| issueKey | string|null | – | Key of the issue these snippets belong to. |
| snippets | array|null | – | One or more source code snippets showing the issue location and surrounding lines. |
No examples provided.
getProject ~184
Get one project analysis. Returns project metadata, quality gate failures, and metrics for size, findings, coverage, duplication, and technical debt. Scope explicitly: omitting both `branch` and `pullRequest` uses the configured default (usually main). For non-main or PR work, pass the matching ref explicitly; discover it with `listProjectBranches` / `listProjectPullRequests`.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name; mutually exclusive with `pullRequest`. Omission uses the configured default (usually main). For non-main work, pass explicitly; use `listProjectBranches`. |
| projectKey | string | – | Project key; omit only if the server has a default. Discover with `listProjects`. |
| pullRequest | string | – | PR key; mutually exclusive with `branch`; no default. For PR work, pass explicitly; use `listProjectPullRequests`. |
| Name | Type | Req | Description |
|---|---|---|---|
| description | string|null | – | Optional project description. |
| lastAnalysisDate | string|null | – | ISO-8601 timestamp of the most recent successful analysis. |
| metrics | – | – | – |
| name | string|null | – | Human-readable project name. |
| projectKey | string|null | – | Unique project key. |
| qualifier | string|null | – | Project qualifier: TRK for a main project, VW for a portfolio, APP for an application. |
| qualityGate | – | – | – |
| version | string|null | – | Project version string, if configured. |
| visibility | string|null | – | Visibility setting: 'public' or 'private'. |
No examples provided.
getProjectIssuesBreakdown ~374
Count project issues by logical module and rule; intended for multi-module projects. A module is the first `componentPath` segment. Returns totals, module/rule facets, and per-module severity/type summaries. Scope explicitly: omitting both `branch` and `pullRequest` uses the configured default (usually main). For non-main or PR work, pass the matching ref explicitly; discover it with `listProjectBranches` / `listProjectPullRequests`. If `branchAdvisory` is present, choose the branch matching the user's ref and retry explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name; mutually exclusive with `pullRequest`. Omission uses the configured default (usually main). For non-main work, pass explicitly; use `listProjectBranches`. |
| componentPathPrefix | string | – | Same Sonar `componentPath` prefix semantics as `listIssues`; use `listComponents` instead of guessing. |
| projectKey | string | – | Project key; omit only if the server has a default. Discover with `listProjects`. |
| pullRequest | string | – | PR key; mutually exclusive with `branch`; no default. For PR work, pass explicitly; use `listProjectPullRequests`. |
| resolved | boolean | – | Resolved filter; defaults to false only when statuses is also omitted. |
| rules | string | – | Comma-separated rule keys, e.g. `java:S1234`. |
| severities | string | – | Comma-separated: INFO,MINOR,MAJOR,CRITICAL,BLOCKER. |
| statuses | string | – | Comma-separated: OPEN,CONFIRMED,REOPENED,RESOLVED,CLOSED. With no statuses/resolved, returns open issues. |
| types | string | – | Comma-separated: CODE_SMELL,BUG,VULNERABILITY. |
| Name | Type | Req | Description |
|---|---|---|---|
| branchAdvisory | – | – | – |
| byModule | array|null | – | Issues grouped by logical module. |
| byRule | array|null | – | Issues grouped by rule key across the selected scope. |
| modules | array|null | – | Per-module issue summaries, including rule/severity/type breakdowns. |
| pathPrefixTruncated | boolean | – | True when componentPathPrefix was supplied and the underlying scan hit the configured maximum issue count before exhausting Sonar. Totals/modules reflect only the scanned slice. |
| projectKey | string|null | – | Key of the project being analysed. |
| total | integer | – | Total number of issues matching the query. |
No examples provided.
getProjectIssuesSummary ~365
Count project issues and group them by severity, type, status, rule, tag, and SCM author. Returns the total and facet counts; use before listing details. Scope explicitly: omitting both `branch` and `pullRequest` uses the configured default (usually main). For non-main or PR work, pass the matching ref explicitly; discover it with `listProjectBranches` / `listProjectPullRequests`. If `branchAdvisory` is present, choose the branch matching the user's ref and retry explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name; mutually exclusive with `pullRequest`. Omission uses the configured default (usually main). For non-main work, pass explicitly; use `listProjectBranches`. |
| componentPathPrefix | string | – | Same Sonar `componentPath` prefix semantics as `listIssues`; use `listComponents` instead of guessing. |
| projectKey | string | – | Project key; omit only if the server has a default. Discover with `listProjects`. |
| pullRequest | string | – | PR key; mutually exclusive with `branch`; no default. For PR work, pass explicitly; use `listProjectPullRequests`. |
| resolved | boolean | – | Resolved filter; defaults to false only when statuses is also omitted. |
| rules | string | – | Comma-separated rule keys, e.g. `java:S1234`. |
| severities | string | – | Comma-separated: INFO,MINOR,MAJOR,CRITICAL,BLOCKER. |
| statuses | string | – | Comma-separated: OPEN,CONFIRMED,REOPENED,RESOLVED,CLOSED. With no statuses/resolved, returns open issues. |
| types | string | – | Comma-separated: CODE_SMELL,BUG,VULNERABILITY. |
| Name | Type | Req | Description |
|---|---|---|---|
| branchAdvisory | – | – | – |
| byAuthor | array|null | – | Issues grouped by SCM author who introduced them (top authors by issue count). |
| byRule | array|null | – | Issues grouped by rule key (top rules by issue count). |
| bySeverity | array|null | – | Issues grouped by severity (BLOCKER, CRITICAL, MAJOR, MINOR, INFO). |
| byStatus | array|null | – | Issues grouped by lifecycle status (OPEN, CONFIRMED, REOPENED, RESOLVED, CLOSED). |
| byTag | array|null | – | Issues grouped by user-defined tag. |
| byType | array|null | – | Issues grouped by type (BUG, VULNERABILITY, CODE_SMELL). |
| pathPrefixTruncated | boolean | – | True when componentPathPrefix was supplied and the underlying scan hit the configured maximum issue count before exhausting Sonar. Totals/facets reflect only the scanned slice. |
| projectKey | string|null | – | Key of the project being summarised. |
| total | integer | – | Total number of issues matching the query. |
No examples provided.
getRule ~51
Get a Sonar rule. Returns title, severity, type, language, tags, and structured explanation and fix sections.
| Name | Type | Req | Description |
|---|---|---|---|
| ruleKey | string | yes | Rule key, e.g. `java:S1234` |
| Name | Type | Req | Description |
|---|---|---|---|
| descriptionSections | array|null | – | Structured description broken into sections (rationale, non-compliant code, compliant code, etc.). |
| htmlDescription | string|null | – | Full rule description as raw HTML (including code examples and formatting). |
| key | string|null | – | Unique rule key (e.g. 'java:S1186'). |
| lang | string|null | – | Language key (e.g. 'java', 'js', 'py'). |
| langName | string|null | – | Human-readable language name (e.g. 'Java', 'JavaScript', 'Python'). |
| name | string|null | – | Human-readable rule name. |
| repo | string|null | – | Repository key (language or technology identifier, e.g. 'java', 'js', 'py'). |
| severity | string|null | – | Default severity. Standard mode: BLOCKER, CRITICAL, MAJOR, MINOR, INFO. MQR mode: BLOCKER, HIGH, MEDIUM, LOW, INFO. |
| status | string|null | – | Rule lifecycle status: READY, DEPRECATED, or REMOVED. |
| tags | array|null | – | Tags categorising the rule (e.g. 'performance', 'java8', 'owasp-a1'). |
| type | string|null | – | Rule type: BUG, VULNERABILITY, CODE_SMELL, or SECURITY_HOTSPOT. |
No examples provided.
listComponents ~275
Browse or search a project's analysed component tree. Use returned `path` values as `componentPathPrefix`; Sonar paths may differ from repository paths. Returns component key, path, name, qualifier, and language. Use `qualifiers=DIR` to discover directories. Scope explicitly: omitting both `branch` and `pullRequest` uses the configured default (usually main). For non-main or PR work, pass the matching ref explicitly; discover it with `listProjectBranches` / `listProjectPullRequests`.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name; mutually exclusive with `pullRequest`. Omission uses the configured default (usually main). For non-main work, pass explicitly; use `listProjectBranches`. |
| limit | integer | – | Page size; server default if omitted. |
| offset | integer | – | Offset; default 0. |
| projectKey | string | – | Project key; omit only if the server has a default. Discover with `listProjects`. |
| pullRequest | string | – | PR key; mutually exclusive with `branch`; no default. For PR work, pass explicitly; use `listProjectPullRequests`. |
| qualifiers | string | – | Comma-separated component types, e.g. `DIR,FIL`; use `DIR` for path discovery. |
| query | string | – | Component name/path substring |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array|null | – | Components returned by SonarQube. |
| limit | integer | – | Effective page size. |
| offset | integer | – | Requested offset. |
| total | integer | – | Total matching component count reported by SonarQube. |
No examples provided.
listHotspots ~325
List project Security Hotspots that need human review. Defaults to `TO_REVIEW`; supports path and ref filters. Returns rule/category, vulnerability probability, message, and file location. Scope explicitly: omitting both `branch` and `pullRequest` uses the configured default (usually main). For non-main or PR work, pass the matching ref explicitly; discover it with `listProjectBranches` / `listProjectPullRequests`.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name; mutually exclusive with `pullRequest`. Omission uses the configured default (usually main). For non-main work, pass explicitly; use `listProjectBranches`. |
| componentPathPrefix | string | – | Sonar `componentPath` prefix relative to the project root; an exact file path is also allowed. Uses directory boundaries, so `src` does not match `srcExtra`. For Java/Kotlin packages use slashes. Son… |
| limit | integer | – | Page size; server default if omitted. |
| offset | integer | – | Offset; default 0. |
| projectKey | string | – | Project key; omit only if the server has a default. Discover with `listProjects`. |
| pullRequest | string | – | PR key; mutually exclusive with `branch`; no default. For PR work, pass explicitly; use `listProjectPullRequests`. |
| status | string | – | `TO_REVIEW` or `REVIEWED`; default `TO_REVIEW` |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array|null | – | Hotspots in this page. |
| limit | integer | – | Maximum number of items per page. |
| offset | integer | – | Zero-based offset of this page within the full result set. |
| pathPrefixTruncated | boolean | – | True when componentPathPrefix was supplied and the underlying scan hit the configured maximum hotspot count before exhausting Sonar. Tighten the prefix to see the rest. |
| total | integer | – | Total number of hotspots matching the query across all pages. |
No examples provided.
listIssues ~453
List project issues with optional severity, type, status, rule, path, and ref filters. Returns rule, severity, type, status, message, file location/text range, and cross-file flows. Defaults to open issues. Scope explicitly: omitting both `branch` and `pullRequest` uses the configured default (usually main). For non-main or PR work, pass the matching ref explicitly; discover it with `listProjectBranches` / `listProjectPullRequests`. If `branchAdvisory` is present, choose the branch matching the user's ref and retry explicitly.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Branch name; mutually exclusive with `pullRequest`. Omission uses the configured default (usually main). For non-main work, pass explicitly; use `listProjectBranches`. |
| componentPathPrefix | string | – | Sonar `componentPath` prefix relative to the project root; an exact file path is also allowed. Uses directory boundaries, so `src` does not match `srcExtra`. For Java/Kotlin packages use slashes. Son… |
| limit | integer | – | Page size; server default if omitted. |
| offset | integer | – | Offset; default 0. |
| projectKey | string | – | Project key; omit only if the server has a default. Discover with `listProjects`. |
| pullRequest | string | – | PR key; mutually exclusive with `branch`; no default. For PR work, pass explicitly; use `listProjectPullRequests`. |
| resolved | boolean | – | Resolved filter; defaults to false only when statuses is also omitted. |
| rules | string | – | Comma-separated rule keys, e.g. `java:S1234`. |
| severities | string | – | Comma-separated: INFO,MINOR,MAJOR,CRITICAL,BLOCKER. |
| statuses | string | – | Comma-separated: OPEN,CONFIRMED,REOPENED,RESOLVED,CLOSED. With no statuses/resolved, returns open issues. |
| types | string | – | Comma-separated: CODE_SMELL,BUG,VULNERABILITY. |
| Name | Type | Req | Description |
|---|---|---|---|
| branchAdvisory | – | – | – |
| items | array|null | – | Issues in this page. |
| limit | integer | – | Maximum number of items per page. |
| offset | integer | – | Zero-based offset of this page within the full result set. |
| pathPrefixTruncated | boolean | – | True when componentPathPrefix was supplied and the underlying scan hit the configured maximum issue count before exhausting Sonar. The returned `total` and `items` reflect only the scanned slice; tig… |
| total | integer | – | Total number of issues matching the query across all pages. |
No examples provided.
listProjectBranches ~67
List analysed project branches. Returns name, main/type flags, analysis date, quality gate, and issue counts; use the name as `branch` in other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | – | Project key; omit only if the server has a default. Discover with `listProjects`. |
| Name | Type | Req | Description |
|---|---|---|---|
| branches | array|null | – | List of branches with analysis status and issue counts. |
| projectKey | string|null | – | Key of the project these branches belong to. |
No examples provided.
listProjectPullRequests ~82
List project PR analyses. Returns key, title, source/base branches, URL, analysis date, quality gate, and issue counts; use the key as `pullRequest` in other tools. Returns empty when DevOps integration is unavailable.
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string | – | Project key; omit only if the server has a default. Discover with `listProjects`. |
| Name | Type | Req | Description |
|---|---|---|---|
| projectKey | string|null | – | Key of the project these pull requests belong to. |
| pullRequests | array|null | – | List of pull requests with analysis status and issue counts. |
No examples provided.
listProjects ~72
List projects, optionally filtered by name. Returns key, name, and qualifier; use the key as `projectKey` in other tools.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size; server default if omitted. |
| offset | integer | – | Offset; default 0. |
| query | string | – | Project name substring |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array|null | – | Projects in this page. |
| limit | integer | – | Maximum number of items per page. |
| offset | integer | – | Zero-based offset of this page within the full result set. |
| total | integer | – | Total number of projects matching the query across all pages. |
No examples provided.
How do I install the Sonar MCP Server server?
Sonar MCP Server runs locally as a container image, launched with docker run --rm -i -e SONAR_URL -e SONAR_TOKEN -e SONAR_DEFAULT_PROJECT_KEY ghcr.io/igorolv/sonar-mcp-server:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/igorolv/sonar-mcp-server:0.1.0
claude mcp add igorolv-sonar-mcp-server -- docker run --rm -i -e SONAR_URL -e SONAR_TOKEN -e SONAR_DEFAULT_PROJECT_KEY ghcr.io/igorolv/sonar-mcp-server:0.1.0
This image reads SONAR_URL, SONAR_TOKEN and SONAR_DEFAULT_PROJECT_KEY. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the Sonar MCP Server server?
Sonar MCP Server is listed in the public MCP registry as io.github.igorolv/sonar-mcp-server. Read-only SonarQube Community Build access for AI agents: issues, hotspots, rules, code snippets. This page covers its container image (ghcr.io/igorolv/sonar-mcp-server:0.1.0).
Is the Sonar MCP Server server safe to use?
Sonar MCP Server scores 51 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sonar MCP Server server expose?
Sonar MCP Server exposes 13 tools: getHotspot, listHotspots, getIssue, getIssueSnippets, getProjectIssuesBreakdown, and 8 more. Their descriptions and schemas cost roughly 2,647 tokens of context every time the server is loaded.
Is the Sonar MCP Server server still maintained?
Sonar MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Sonar MCP Server server under?
Sonar MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.