com.mcparmory/codacy
PYPI · MCPARMORY-CODACY · 2 COMPONENTS · SCANNED SEP 20
Analyze code quality, security issues, and coverage across repositories
Available components
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 Security87
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- 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
- License check failed: the license (MIT License) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 130 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 36654 tokens (~155/item across 236 items; 236 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 Management83
- Stability observed for 25 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 19 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 236 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/codacy MCP server?
com.mcparmory/codacy runs locally as a PyPI package, launched with uvx mcparmory-codacy. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-codacy
claude mcp add com-mcparmory-codacy -- uvx mcparmory-codacy
{
"mcpServers": {
"com-mcparmory-codacy": {
"command": "uvx",
"args": [
"mcparmory-codacy"
]
}
}
} {
"servers": {
"com-mcparmory-codacy": {
"command": "uvx",
"args": [
"mcparmory-codacy"
]
}
}
} codex mcp add com-mcparmory-codacy -- uvx mcparmory-codacy
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-codacy": {
"type": "local",
"command": [
"uvx",
"mcparmory-codacy"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-codacy --command uvx --arg mcparmory-codacy
mcp_servers:
com-mcparmory-codacy:
command: "uvx"
args: ["mcparmory-codacy"] {
"McpServers": {
"com-mcparmory-codacy": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-codacy"
]
}
}
} assistant mcp add com-mcparmory-codacy -t stdio -c uvx -a mcparmory-codacy
{
"mcpServers": {
"com-mcparmory-codacy": {
"command": "uvx",
"args": [
"mcparmory-codacy"
]
}
}
} 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.
- 20 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 15 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +15
- Malware scan: unverified → pass ▲ security
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 20 Sept 2026 · Analysed pypi/mcparmory-codacy@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 41 packages
| Packages resolved | 41 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
search_dependency_repositories Search Dependency Repositories ~166
Search for repositories within an organization that use a specific SBOM dependency, returning a paginated list of matches. Optionally filter results to a subset of repositories by name.
| Name | Type | Req | Description |
|---|---|---|---|
| dependencyFullName | string | yes | The fully qualified name of the SBOM dependency to search for across repositories. |
| limit | string | – | Maximum number of repositories to return per page. Accepts values between 1 and 100. |
| provider | string | yes | The Git provider hosting the organization. Use the short identifier for the target platform. |
| remoteOrganizationName | string | yes | The organization name as it appears on the Git provider. |
| repositoriesFilter | array | – | An optional list of repository names to restrict the search to. Order is not significant; each item should be a repository name string. |
No output schema declared.
No examples provided.
search_entities Search Entities ~57
Search across Codacy entities such as Organizations and Repositories by name or ID. Restricted to Codacy admins only.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | A search string used to filter results by matching against entity names or IDs such as organizations or repositories. |
No output schema declared.
No examples provided.
search_organization_repositories Search Organization Repositories with Analysis ~165
Search repositories within an organization on a specified Git provider, returning results enriched with analysis information. Supports filtering by repository name and paginated results.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Maximum number of repositories to return per request. Accepts values between 1 and 100 inclusive. |
| names | array | – | Filter results to only the specified repository names. Each item should be a repository name string; order does not affect results. |
| provider | string | yes | The Git provider hosting the organization. Use the short identifier for the target platform (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider. Must match the exact organization identifier used by the provider. |
No output schema declared.
No examples provided.
search_repositories_with_security_findings Search Repositories with Security Findings ~171
Searches repositories within an organization for security findings, returning matching results with their associated security data. If no filters are applied, defaults to returning the 10 repositories with the highest number of findings.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
| repositories | array | – | List of repository names to narrow results to specific repositories; order is not significant. If omitted, all repositories in the organization are considered. |
| segments | array | – | List of segment IDs to filter repositories by organizational segment; order is not significant. If omitted, all segments are included. |
No output schema declared.
No examples provided.
search_repository_issues Search Repository Issues ~139
Searches and returns issues found by Codacy in a specific repository, equivalent to the Issues page view. Supports filtering via request body to narrow results by category, severity, or other criteria.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | string | – | Maximum number of issues to return per request. Accepts values between 1 and 100. |
| provider | string | yes | Identifier for the Git provider hosting the repository, such as GitHub, GitLab, or Bitbucket. |
| remoteOrganizationName | string | yes | The organization or account name as it appears on the Git provider. |
| repositoryName | string | yes | The repository name within the specified organization on the Git provider. |
No output schema declared.
No examples provided.
search_sbom_dependencies Search SBOM Dependencies ~363
Search and filter SBOM (Software Bill of Materials) dependencies used across an organization, returning vulnerability and license risk details for matched components. Supports filtering by severity, repository, segment, and text search against component identifiers.
| Name | Type | Req | Description |
|---|---|---|---|
| columnOrder | string | – | Direction in which to sort the results relative to the chosen sort column. Use `asc` for ascending or `desc` for descending order. |
| findingSeverities | array | – | List of vulnerability severity levels to include in results. Order is not significant; valid values are `Critical`, `High`, `Medium`, and `Low`. |
| limit | string | – | Maximum number of dependency records to return per request. Accepts values between 1 and 100. |
| provider | string | yes | The Git provider hosting the organization. Use the short identifier for the target platform. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider. |
| repositories | array | – | List of repository names within the organization to restrict results to. Order is not significant; each item should be a repository name string. |
| riskCategories | array | – | List of license risk category labels to filter dependencies by. Order is not significant; each item should be a valid license risk category string. |
| segments | array | – | List of segment IDs to restrict results to. Order is not significant; each item should be an integer segment identifier. |
| sortColumn | string | – | Field by which to sort the returned results. Use `severity` to order by the dependency's vulnerability severity, or `ossfScore` to order by the OpenSSF scorecard score. |
| text | string | – | Free-text search string matched against SBOM component fields including package URL (purl) and full component name. |
No output schema declared.
No examples provided.
search_sbom_repositories Search SBOM Repositories ~152
Search and list repositories within an organization that contain SBOM (Software Bill of Materials) dependency information, optionally filtering by specific dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Optional request body to filter repositories by specific dependencies. Each item should be a dependency identifier in the format 'ecosystem/package-name'. |
| limit | string | – | Maximum number of repositories to return per request. Accepts values between 1 and 100. |
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The exact organization name as it appears on the specified Git provider. |
No output schema declared.
No examples provided.
search_security_category_finding Search Security Category Findings ~159
Retrieves security categories with their associated findings for an organization, optionally filtered by repositories or segments. If no filters are provided, returns the 10 categories with the highest finding counts.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
| repositories | array | – | List of repository names to scope the results to; omit to include all repositories in the organization. Order is not significant. |
| segments | array | – | List of segment IDs to filter results by; omit to include all segments. Order is not significant. |
No output schema declared.
No examples provided.
search_security_findings_history Search Security Findings History ~151
Retrieves the historical evolution of security findings over time for an organization, optionally filtered by specific repositories or segments. Useful for tracking security posture trends and identifying improvements or regressions.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider hosting the organization. Use the short identifier for the target platform. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider. |
| repositories | array | – | List of repository names to scope the history results to. When omitted, results cover all repositories in the organization. Order is not significant. |
| segments | array | – | List of segment IDs to filter the history results by. Segments represent logical groupings within the organization. Order is not significant. |
No output schema declared.
No examples provided.
search_security_items Search Security Items ~389
Search and filter security and risk management (SRM) items across repositories in an organization. Supports filtering by priority, status, category, scan type, and more to help identify and triage security issues.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | array | – | List of security categories to filter by. Use the special value `_other_` to include items that have no assigned security category. Order is not significant. |
| dastTargetUrls | array | – | List of DAST target URLs to filter results to only items associated with those targets. Order is not significant. |
| direction | string | – | The direction in which to sort results, either ascending or descending. |
| limit | string | – | Maximum number of security items to return per request. Must be between 1 and 100. |
| priorities | array | – | List of priority levels to filter security items by. Refer to SrmPriority for valid values. Order is not significant. |
| provider | string | yes | The Git provider hosting the organization. Identifies which platform to query. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider. |
| repositories | array | – | List of repository names within the organization to restrict results to. Order is not significant. |
| scanTypes | array | – | List of scan types to filter results by, such as static analysis, dependency scanning, secrets detection, and others. Order is not significant. |
| searchText | string | – | Free-text search string to match against security item content, such as titles or descriptions. |
| segments | array | – | List of segment IDs to filter security items by. Segments represent logical groupings within the organization. Order is not significant. |
| sort | string | – | The field by which to sort the returned security items. |
| statuses | array | – | List of statuses to filter security items by. Refer to SrmStatus for valid values. Order is not significant. |
No output schema declared.
No examples provided.
set_default_branch Set Default Branch ~124
Sets the default branch for a specified repository on Codacy. The target branch must already be enabled on Codacy before it can be designated as the default.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | yes | Name of the branch to designate as the new default; this branch must already be enabled on Codacy. |
| provider | string | yes | Short code identifying the Git provider hosting the repository. |
| remoteOrganizationName | string | yes | Name of the organization on the Git provider that owns the repository. |
| repositoryName | string | yes | Name of the repository within the organization on the Git provider. |
No output schema declared.
No examples provided.
set_default_coding_standard Set Default Coding Standard ~146
Sets or unsets a specific coding standard as the default for an organization, controlling which coding standard is automatically applied to new projects.
| Name | Type | Req | Description |
|---|---|---|---|
| codingStandardId | string | yes | The unique numeric identifier of the coding standard to set or unset as the default. |
| isDefault | boolean | yes | When true, designates this coding standard as the organization's default; when false, removes its default status. |
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
No output schema declared.
No examples provided.
set_default_email Set Default Email ~47
Designates a specified email address as the primary default for the authenticated user, automatically removing the default status from any previously designated email. Only one email address can hold default status at a time.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
set_default_gate_policy Set Default Gate Policy ~117
Sets a specified gate policy as the default for an organization, ensuring it is applied automatically when no other policy is explicitly assigned.
| Name | Type | Req | Description |
|---|---|---|---|
| gatePolicyId | string | yes | The unique numeric identifier of the gate policy to designate as the default. |
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The exact name of the organization as it appears on the Git provider platform. |
No output schema declared.
No examples provided.
set_default_gate_policy_to_codacy_builtin Set Default Gate Policy to Codacy Builtin ~92
Sets the built-in Codacy gate policy as the default quality gate for the specified organization, replacing any previously configured default policy.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., GitHub, GitLab, or Bitbucket). |
| remoteOrganizationName | string | yes | The exact organization name as it appears on the Git provider platform. |
No output schema declared.
No examples provided.
set_file_ignored_state Set File Ignored State ~178
Ignore or unignore a specific file in a repository, controlling whether Codacy includes it in analysis. Use this to suppress analysis on generated, vendored, or otherwise irrelevant files.
| Name | Type | Req | Description |
|---|---|---|---|
| filepath | string | yes | The relative path to the file within the repository, starting from the repository root. |
| ignored | boolean | yes | Set to true to ignore the file (exclude it from analysis) or false to unignore it (re-include it in analysis). |
| provider | string | yes | Short identifier for the Git provider hosting the repository (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The organization or account name as it appears on the Git provider. |
| repositoryName | string | yes | The repository name as it appears under the organization on the Git provider. |
No output schema declared.
No examples provided.
set_issue_ignored_state Set Issue Ignored State ~188
Ignore or unignore a specific code analysis issue in a repository, optionally providing a predefined reason and comment to justify the action.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Free-text comment providing additional context or justification for the ignore action, supplementing the predefined reason. |
| ignored | boolean | yes | Set to true to ignore the issue or false to unignore it and restore it to an active state. |
| issueId | string | yes | Unique identifier of the issue to update. |
| provider | string | yes | Short code identifying the Git provider hosting the repository. |
| reason | string | – | Predefined category explaining why the issue is being ignored; required when ignoring an issue to ensure consistent classification. |
| remoteOrganizationName | string | yes | Name of the organization or account on the Git provider that owns the repository. |
| repositoryName | string | yes | Name of the repository within the organization on the Git provider. |
No output schema declared.
No examples provided.
set_organization_join_mode Set Organization Join Mode ~150
Updates the membership join mode for an organization on a specified Git provider, controlling how new members are admitted (automatically, admin-approved automatically, or by request).
| Name | Type | Req | Description |
|---|---|---|---|
| joinMode | string | yes | The join mode to apply to the organization: 'auto' allows anyone to join automatically, 'adminAuto' grants automatic access after admin approval, and 'request' requires members to submit a join reque… |
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The exact name of the organization as it appears on the Git provider. |
No output schema declared.
No examples provided.
start_organization_metrics_collection Start Organization Metrics Collection ~102
Initiates data collection for any missing metrics within the specified organization. The organization must have metrics support enabled before calling this endpoint.
| Name | Type | Req | Description |
|---|---|---|---|
| metrics | array | – | List of specific metric identifiers to start collecting. If omitted, collection is initiated for all missing metrics. Order is not significant. |
| provider | string | yes | Short code identifying the Git provider hosting the organization. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider. |
No output schema declared.
No examples provided.
submit_pattern_feedback Submit Pattern Feedback ~195
Submits user feedback on an enriched tool pattern for a specific organization, indicating whether the pattern is considered relevant and optionally providing a written explanation.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback | string | – | Optional free-text explanation describing why the enriched pattern is considered irrelevant or problematic, providing additional context for the negative feedback. |
| patternId | string | yes | The identifier of the specific pattern within the tool that the feedback applies to. |
| provider | string | yes | Short code identifying the Git hosting provider (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| reactionFeedback | boolean | yes | Boolean vote on the enriched pattern's relevance — true indicates the pattern is considered good or relevant, false indicates it is not. |
| remoteOrganizationName | string | yes | The name of the organization on the specified Git provider whose context scopes this feedback. |
| toolUuid | string | yes | The unique UUID identifying the tool whose pattern is being reviewed. |
No output schema declared.
No examples provided.
sync_organization_name Sync Organization Name ~97
Synchronizes the organization's display name in Codacy with the current name from the specified Git provider, ensuring both systems remain consistent.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short code identifying the Git provider hosting the organization, such as gh for GitHub, gl for GitLab, or bb for Bitbucket. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider, used to locate the correct organization for synchronization. |
No output schema declared.
No examples provided.
sync_repository Sync Repository with Provider ~104
Synchronizes a repository's name and visibility settings in Codacy with the current state from the upstream Git provider. Useful after renaming or changing the visibility of a repository directly on the provider.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short identifier for the Git provider hosting the repository. |
| remoteOrganizationName | string | yes | The organization or account name as it appears on the Git provider. |
| repositoryName | string | yes | The repository name as it appears under the organization on the Git provider. |
No output schema declared.
No examples provided.
trigger_dast_analysis Trigger DAST Analysis ~123
Enqueues a Dynamic Application Security Testing (DAST) analysis for a specified target within an organization. Use this to initiate a security scan against a previously configured DAST target.
| Name | Type | Req | Description |
|---|---|---|---|
| dastTargetId | string | yes | Unique numeric identifier of the DAST target to be analyzed. Must reference an existing target configured under the organization. |
| provider | string | yes | Short code identifying the Git provider hosting the organization, such as GitHub, GitLab, or Bitbucket. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
No output schema declared.
No examples provided.
trigger_pull_request_ai_review Trigger Pull Request AI Review ~126
Triggers an AI-powered code review for a specific pull request in a repository. Initiates automated analysis and feedback generation for the pull request's changes.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short code identifying the Git hosting provider for the repository. |
| pullRequestNumber | string | yes | The numeric identifier of the pull request to be reviewed, as assigned by the Git provider. |
| remoteOrganizationName | string | yes | Name of the organization or account on the Git provider that owns the repository. |
| repositoryName | string | yes | Name of the repository within the organization on the Git provider. |
No output schema declared.
No examples provided.
unfollow_repository Unfollow Repository ~109
Stops following a repository in the specified organization on a Git provider, removing it from the list of monitored repositories.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short identifier for the Git provider hosting the repository (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The name of the organization on the Git provider that owns the repository. |
| repositoryName | string | yes | The name of the repository within the specified Git provider organization to unfollow. |
No output schema declared.
No examples provided.
unignore_security_item Unignore Security Item ~123
Restores a previously ignored security and risk management item to an active state within the specified organization. Only items that have been explicitly ignored can be unignored.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The exact organization name as it appears on the Git provider platform. |
| srmItemId | string | yes | The unique UUID identifying the security and risk management item to be unignored. |
No output schema declared.
No examples provided.
unlink_jira_ticket Unlink Jira Ticket ~219
Removes the association between a Jira ticket and a specific repository element (such as an issue, finding, file, or dependency) within an organization. Use this to detach a previously linked Jira ticket from a code analysis element.
| Name | Type | Req | Description |
|---|---|---|---|
| elementId | string | yes | The unique identifier of the specific repository element (of the type specified by elementType) from which the Jira ticket will be unlinked. |
| elementType | string | yes | The type of repository element from which the Jira ticket will be unlinked. Must be one of: issue, finding, file, or dependency. |
| jiraTicketIdentifier | string | yes | The unique numeric identifier of the Jira ticket to unlink. This is the internal Jira ticket ID, not the human-readable issue key. |
| provider | string | yes | The Git provider hosting the organization. Use the short identifier for the provider (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The name of the organization as it appears on the Git provider platform. |
No output schema declared.
No examples provided.
update_coding_standard_repositories Update Coding Standard Repositories ~175
Links or unlinks a set of repositories to a specified coding standard within an organization. If the coding standard is in draft state, changes take effect only upon promoting it.
| Name | Type | Req | Description |
|---|---|---|---|
| codingStandardId | string | yes | Unique numeric identifier of the coding standard to update. |
| link | array | yes | List of repository names to associate with the coding standard. Order is not significant; each item should be the repository's name as it appears on the Git provider. |
| provider | string | yes | Identifier for the Git provider hosting the organization. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider. |
| unlink | array | yes | List of repository names to dissociate from the coding standard. Order is not significant; each item should be the repository's name as it appears on the Git provider. |
No output schema declared.
No examples provided.
update_current_user Update Current User ~64
Updates profile settings for the currently authenticated user. Only the fields provided will be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | The display name to assign to the authenticated user's profile. |
| shouldDoClientQualification | boolean | – | Whether the system should trigger client qualification checks for this user. |
No output schema declared.
No examples provided.
update_gate_policy Update Gate Policy ~453
Updates an existing quality gate policy for an organization, allowing modification of thresholds, severity filters, and default status. Quality gate policies define the criteria that must be met for a pull request or commit to pass code quality checks.
| Name | Type | Req | Description |
|---|---|---|---|
| complexityThreshold | string | – | The maximum allowed complexity value introduced by new code; the gate fails if this threshold is exceeded. Must be zero or greater. |
| coverageThresholdWithDecimals | number | – | The minimum required change in coverage percentage; the gate fails if coverage varies by less than this value. Accepts negative values to allow coverage decreases up to a specified amount, with a max… |
| diffCoverageThreshold | string | – | The minimum required diff coverage percentage; the gate fails if diff coverage falls below this value. Must be between 0 and 100 inclusive. |
| duplicationThreshold | string | – | The maximum number of new duplicated code blocks allowed before the quality gate fails. |
| gatePolicyId | string | yes | The unique numeric identifier of the gate policy to update. |
| gatePolicyName | string | – | The human-readable display name for the gate policy. |
| isDefault | boolean | – | When true, this gate policy becomes the default applied to all repositories in the organization that do not have an explicitly assigned policy. |
| minimumSeverity | string | – | The minimum severity level of issues that count toward the issue threshold. Severity levels map to the UI as: Info → Minor, Warning → Medium, High → High, Error → Critical. |
| provider | string | yes | The short code identifying the Git provider hosting the organization. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
| securityIssueMinimumSeverity | string | – | The minimum severity level of security issues that count toward the security issue threshold. Severity levels map to the UI as: Info → Minor, Warning → Medium, High → High, Error → Critical. |
| securityIssueThreshold | string | – | The maximum number of new security issues allowed before the quality gate fails. Must be zero or greater. |
| threshold | string | yes | The maximum number of new issues allowed before the quality gate fails. Must be zero or greater. |
No output schema declared.
No examples provided.
update_gate_policy_repositories Update Gate Policy Repositories ~202
Links or unlinks a set of repositories to a specified gate policy within an organization. Allows simultaneous association and disassociation of repositories in a single request.
| Name | Type | Req | Description |
|---|---|---|---|
| gatePolicyId | string | yes | The unique numeric identifier of the gate policy to which repositories will be linked or unlinked. |
| link | array | yes | List of repository names to associate with the gate policy. Order is not significant; each item should be the repository's name as it appears on the Git provider. |
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The exact organization name as it appears on the Git provider platform. |
| unlink | array | yes | List of repository names to disassociate from the gate policy. Order is not significant; each item should be the repository's name as it appears on the Git provider. |
No output schema declared.
No examples provided.
update_organization_billing Update Organization Billing ~99
Updates the billing information for a specified organization on a given Git provider. Use this to modify billing details associated with the organization's Codacy account.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The exact name of the organization as it appears on the specified Git provider. |
No output schema declared.
No examples provided.
update_repository_integration_settings Update Repository Integration Settings ~388
Updates the Git provider integration settings for a specific repository, controlling which Codacy features are active such as status checks, pull request comments, AI reviews, and coverage summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| aiEnhancedComments | boolean | – | Enables or disables AI-enhanced comments on pull requests; when combined with Suggested Fixes (GitHub only), the AI comments also include fix suggestions. |
| aiPullRequestReviewer | boolean | – | Enables or disables the AI Pull Request Reviewer, which automatically analyzes pull requests and posts comments on code quality and potential issues. Available on GitHub only. |
| aiPullRequestReviewerAutomatic | boolean | – | Enables or disables automatic triggering of the AI Pull Request Reviewer on each new pull request; after the initial automatic review, subsequent reviews must be explicitly requested. Available on Gi… |
| commitStatus | boolean | – | Enables or disables commit status checks, which report Codacy analysis results directly on commits and pull requests. |
| coverageSummary | boolean | – | Enables or disables a coverage summary comment on pull requests showing coverage changes. Available on GitHub only. |
| provider | string | yes | Short identifier for the Git provider hosting the repository. |
| pullRequestComment | boolean | – | Enables or disables inline issue annotations posted as pull request comments for each identified code issue. |
| pullRequestSummary | boolean | – | Enables or disables pull request summary comments that aggregate all issues found in the analysis. |
| pullRequestUnifiedSummary | boolean | – | Enables or disables a unified pull request summary that combines both coverage and analysis results into a single comment. Available on GitHub only. |
| remoteOrganizationName | string | yes | The organization or account name as it appears on the Git provider. |
| repositoryName | string | yes | The repository name as it appears under the organization on the Git provider. |
| suggestions | boolean | – | Enables or disables suggested code fixes posted as pull request comments. Available on GitHub only. |
No output schema declared.
No examples provided.
update_repository_quality_settings Update Repository Quality Settings ~341
Updates the quality gate thresholds for a specific repository, defining the criteria under which the repository is considered healthy or unhealthy across issues, duplication, coverage, and complexity metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| fileComplexityValueThreshold | string | – | The complexity score above which a file is considered complex within this repository. Must be zero or greater. |
| fileDuplicationBlockThreshold | string | – | The number of cloned blocks above which a file is considered duplicated within this repository. Must be zero or greater. |
| maxComplexFilesPercentage | string | – | The maximum acceptable percentage of complex files; the repository is flagged as unhealthy if this threshold is exceeded. Must be a non-negative integer representing a percentage. |
| maxDuplicatedFilesPercentage | string | – | The maximum acceptable percentage of duplicated files; the repository is flagged as unhealthy if this threshold is exceeded. Must be a non-negative integer representing a percentage. |
| maxIssuePercentage | string | – | The maximum acceptable percentage of files with issues; the repository is flagged as unhealthy if this threshold is exceeded. Must be a non-negative integer representing a percentage. |
| minCoveragePercentage | string | – | The minimum required code coverage percentage; the repository is flagged as unhealthy if coverage falls below this threshold. Must be a non-negative integer representing a percentage. |
| provider | string | yes | The Git provider hosting the repository, identified by a short code (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| remoteOrganizationName | string | yes | The name of the organization or account on the Git provider that owns the repository. |
| repositoryName | string | yes | The name of the repository within the specified Git provider organization. |
No output schema declared.
No examples provided.
upload_dast_report Upload DAST Report ~206
Uploads a Dynamic Application Security Testing (DAST) scan report to Codacy for the specified organization and tool. The report is parsed and integrated into the organization's security findings dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Base64-encoded file content for upload. The binary file containing the DAST scan results. For ZAP reports, ensure the `@generated` timestamp field is in English locale using the format `EEE, d MMM yy… |
| provider | string | yes | Short identifier for the Git provider hosting the organization. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the remote Git provider. |
| reportFormat | string | yes | The format of the uploaded report file. Must match the structure expected for the specified tool. |
| toolName | string | yes | The DAST tool that generated the report. Currently only ZAP (OWASP Zed Attack Proxy) is supported. |
No output schema declared.
No examples provided.
upload_image_sbom Upload Image SBOM ~178
Uploads a Software Bill of Materials (SBOM) for a Docker image to the specified organization, enabling vulnerability tracking and dependency analysis. Accepts SBOM files in SPDX or CycloneDX format.
| Name | Type | Req | Description |
|---|---|---|---|
| environment | string | – | The deployment environment associated with the Docker image (e.g., production, staging), used to contextualize the SBOM within a specific runtime environment. |
| image_ref | string | – | Full Docker image reference in the format 'repositoryName/imageName:tag' |
| provider | string | yes | Short code identifying the Git provider hosting the organization. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider. |
| sbom | string | yes | Base64-encoded file content for upload. The SBOM file to upload, provided as binary data in either SPDX or CycloneDX format. |
No output schema declared.
No examples provided.
What is the com.mcparmory/codacy MCP server?
com.mcparmory/codacy is an MCP server listed in the public MCP registry as com.mcparmory/codacy. Analyze code quality, security issues, and coverage across repositories. This page covers its PyPI package (mcparmory-codacy).
Is the com.mcparmory/codacy MCP server safe to use?
com.mcparmory/codacy scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 com.mcparmory/codacy MCP server expose?
com.mcparmory/codacy exposes 236 tools: list_organization_repositories_with_analysis, search_organization_repositories, get_repository_analysis, list_repository_tools, list_tool_conflicts, and 231 more. Their descriptions and schemas cost roughly 36,654 tokens of context every time the server is loaded.
Is the com.mcparmory/codacy MCP server still maintained?
com.mcparmory/codacy is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.