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 →
add_billing_card Add Billing Card ~102
Adds a payment card to the specified organization's billing profile using a Stripe token. The token must be obtained from the Stripe /v1/tokens API prior to calling this endpoint.
| 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 specified Git provider. |
No output schema declared.
No examples provided.
add_codacy_badge Add Codacy Badge ~99
Creates a pull request that adds the Codacy static analysis badge to the repository's README. Only applies to public GitHub repositories that do not already have the badge; the pull request is created asynchronously and may fail after a successful response.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
add_enterprise_token Add Enterprise Token ~82
Adds a GitHub Enterprise account token with read permissions for the authenticated user, enabling access to enterprise-level resources and repositories.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git hosting provider associated with the enterprise account token being added. |
| token | string | yes | The GitHub Enterprise personal access token with read permissions to be stored and used for authenticating enterprise-level resource requests. |
No output schema declared.
No examples provided.
add_organization Add Organization ~161
Registers an organization from a Git provider with Codacy, enabling code quality analysis and management for that organization's repositories.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The display name of the organization as it appears on the Git provider. |
| products | array | – | A list of Codacy products to enable for the organization, where each item represents a product identifier. Order is not significant. |
| provider | string | yes | The Git provider that hosts the organization, such as GitHub, GitLab, or Bitbucket. |
| remoteIdentifier | string | yes | The unique identifier for the organization on the Git provider, used to locate and link the organization remotely. |
| type | string | yes | Specifies whether the entity is a personal account or a shared organization, which determines available features and permissions. |
No output schema declared.
No examples provided.
add_organization_members Add Organization Members ~74
Adds people to an organization on the specified Git provider, assigning them as members or committers based on whether they have a pending join request.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 platform. |
No output schema declared.
No examples provided.
add_repository Add Repository ~86
Adds a new repository to an existing Codacy organization, enabling code quality analysis and tracking for that repository.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider that hosts the repository, identifying the source platform where the repository resides. |
| repositoryFullPath | string | yes | The full path of the repository on the Git provider, beginning at the organization level with each path segment separated by a forward slash. |
No output schema declared.
No examples provided.
apply_organization_provider_settings Apply Organization Provider Settings ~99
Applies the organization's default provider settings to all repositories within the specified Git provider organization. Use this to propagate updated integration settings uniformly across all repositories at once.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider hosting the organization, identified by its 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. |
No output schema declared.
No examples provided.
assign_security_manager Assign Security Manager ~132
Promotes an existing organization member to the Security Manager role within the specified Git provider organization. This grants the user elevated permissions to oversee and manage security-related settings and findings.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Identifier for the Git provider hosting the organization. Use the short code for the desired provider (e.g., GitHub, GitLab, Bitbucket). |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
| userId | string | yes | The unique numeric identifier of the organization member to be assigned the Security Manager role. Must correspond to an existing member of the organization. |
No output schema declared.
No examples provided.
bulk_ignore_repository_issues Bulk Ignore Repository Issues ~212
Ignores a batch of issues in a specified repository, suppressing them from analysis results. Accepts up to 50 issue IDs per request, with an optional reason and comment for audit purposes.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | An optional free-text comment providing additional context or explanation for ignoring the specified issues. |
| issueIds | array | yes | An unordered list of unique issue IDs to ignore. Maximum of 50 IDs per request; each item should be a valid issue identifier. |
| 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). |
| reason | string | – | An optional reason categorizing why the issues are being ignored, used for tracking and audit purposes. |
| 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.
bulk_update_coding_standard_tool_patterns Bulk Update Coding Standard Tool Patterns ~348
Enable or disable multiple code patterns for a specific tool within a coding standard. Use optional filters to target a subset of patterns by language, category, severity, tags, or search term, or omit all filters to apply the update to every pattern in the tool.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | string | – | Comma-separated list of pattern categories to restrict which patterns are updated. Valid values are Security, ErrorProne, CodeStyle, Compatibility, UnusedCode, Complexity, Comprehensibility, Document… |
| codingStandardId | string | yes | Numeric identifier of the coding standard to update patterns within. |
| enabled | boolean | yes | Whether to enable or disable the matched code patterns; true enables them and false disables them. |
| languages | string | – | Comma-separated list of programming language names to restrict which patterns are updated. |
| provider | string | yes | Short code identifying the Git provider hosting the organization. |
| recommended | boolean | – | Restricts the update to patterns based on their recommended status; true targets only recommended patterns, false targets only non-recommended patterns. |
| remoteOrganizationName | string | yes | Exact name of the organization as it appears on the Git provider. |
| search | string | – | Free-text string used to filter patterns by name or description before applying the update. |
| severityLevels | string | – | Comma-separated list of severity levels to restrict which patterns are updated. Valid values are Error, High, Warning, and Info. |
| tags | string | – | Comma-separated list of pattern tags to restrict which patterns are updated. |
| toolUuid | string | yes | UUID of the tool whose code patterns will be updated within the coding standard. |
No output schema declared.
No examples provided.
bulk_update_repository_tool_patterns Bulk Update Repository Tool Patterns ~382
Bulk enables or disables code patterns for a specific tool in a repository. Use optional filters to target a subset of patterns by language, category, severity, tags, or search term; omit all filters to apply the change to every pattern for the tool.
| Name | Type | Req | Description |
|---|---|---|---|
| categories | string | – | Comma-separated list of pattern categories to restrict the update. Valid values are `Security`, `ErrorProne`, `CodeStyle`, `Compatibility`, `UnusedCode`, `Complexity`, `Comprehensibility`, `Documenta… |
| enabled | boolean | yes | Set to `true` to enable all matched code patterns, or `false` to disable them. |
| languages | string | – | Comma-separated list of programming language names to restrict the update to patterns applicable to those languages only. |
| provider | string | yes | Short code identifying the Git provider hosting the repository. |
| recommended | boolean | – | When set to `true`, restricts the update to recommended patterns only; when set to `false`, restricts it to non-recommended patterns only. Omit to include patterns regardless of recommended status. |
| 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. |
| search | string | – | Free-text search string used to filter patterns by name or description before applying the bulk update. |
| severityLevels | string | – | Comma-separated list of severity levels to restrict the update. Valid values are `Error`, `High`, `Warning`, and `Info`. |
| tags | string | – | Comma-separated list of pattern tags to restrict the update to patterns that carry any of the specified tags. |
| toolUuid | string | yes | UUID that uniquely identifies the tool whose patterns will be updated. |
No output schema declared.
No examples provided.
bypass_pull_request_analysis Bypass Pull Request Analysis ~140
Bypasses the analysis status check for a specific pull request, allowing it to proceed regardless of analysis results. Useful when overriding blocking analysis gates in CI/CD workflows.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short code identifying the Git provider hosting the repository (e.g., gh for GitHub, gl for GitLab, bb for Bitbucket). |
| pullRequestNumber | string | yes | The numeric identifier of the pull request whose analysis status should be bypassed. |
| 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.
change_organization_billing_plan Change Organization Billing Plan ~92
Changes the billing plan for a specified organization on a Git provider. Available plan codes can be retrieved using the list_payment_plans operation.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider hosting the organization, identified by a short code (e.g., GitHub, GitLab, Bitbucket). |
| remoteOrganizationName | string | yes | The exact name of the organization as it appears on the Git provider. |
No output schema declared.
No examples provided.
check_organization_leave_eligibility Check Organization Leave Eligibility ~92
Checks whether the authenticated user is eligible to leave the specified organization, returning either confirmation or the specific reasons preventing them from leaving.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short code identifying the Git provider hosting the organization (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.
check_repository_quickfix_suggestions Check Repository Quickfix Suggestions ~151
Checks whether a repository has any available quick fix suggestions for issues on a specified branch. If no branch is provided, the repository's default branch is used.
| Name | Type | Req | Description |
|---|---|---|---|
| branch | string | – | Name of a branch enabled on Codacy for this repository. Must be a branch tracked by Codacy, as returned by the listRepositoryBranches endpoint. Defaults to the main branch configured in Codacy reposi… |
| provider | string | yes | Short code identifying the Git provider hosting the repository. |
| 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 specified Git provider organization. |
No output schema declared.
No examples provided.
check_submodules_enabled Check Submodules Enabled ~90
Checks whether the submodules option is currently enabled for a specified organization on a Git provider. Useful for verifying organization-level repository settings before performing submodule-dependent operations.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short code identifying the Git provider for the organization, such as GitHub, GitLab, or Bitbucket. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the specified Git provider. |
No output schema declared.
No examples provided.
configure_branch_analysis Configure Branch Analysis ~157
Enable or disable Codacy analysis for a specific repository branch. Use this to control which branches are actively analyzed within a given organization and repository.
| Name | Type | Req | Description |
|---|---|---|---|
| branchName | string | yes | The exact name of the branch within the repository to configure. |
| isEnabled | boolean | – | Set to true to enable Codacy analysis on this branch, or false to disable it. |
| provider | string | yes | Short code identifying 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.
configure_coding_standard_tool Configure Coding Standard Tool ~157
Toggle a tool's enabled status and update its code patterns within a draft coding standard. Only the code patterns included in the request body are modified, with a maximum of 1000 code patterns configurable per call.
| Name | Type | Req | Description |
|---|---|---|---|
| codingStandardId | string | yes | The numeric identifier of the draft coding standard to configure. Only draft coding standards can be updated. |
| 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. |
| toolUuid | string | yes | The UUID uniquely identifying the tool to configure within the coding standard. |
No output schema declared.
No examples provided.
configure_provider_settings Configure Provider Settings ~361
Creates or updates Git provider integration settings for an organization, controlling which Codacy features are active such as status checks, pull request annotations, AI-powered reviews, and coverage summaries.
| Name | Type | Req | Description |
|---|---|---|---|
| aiEnhancedComments | boolean | – | Enables or disables AI-enhanced pull request comments; when combined with Suggested Fixes (GitHub only), AI comments also include inline code 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. Supported 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. Supported on Gi… |
| commitStatus | boolean | – | Enables or disables Codacy commit status checks, which report analysis results directly on commits and pull requests. |
| coverageSummary | boolean | – | Enables or disables coverage summary reporting on pull requests. Supported on GitHub only. |
| provider | string | yes | Short identifier for the Git provider platform hosting the organization. |
| pullRequestComment | boolean | – | Enables or disables inline issue annotations posted as pull request comments by Codacy. |
| pullRequestSummary | boolean | – | Enables or disables pull request summary comments that aggregate Codacy issue findings. |
| pullRequestUnifiedSummary | boolean | – | Enables or disables a unified pull request summary that combines both coverage and analysis results into a single Codacy comment. Supported on GitHub only. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
| suggestions | boolean | – | Enables or disables AI-generated suggested code fixes posted on pull requests. Supported on GitHub only. |
No output schema declared.
No examples provided.
configure_repository_language_settings Configure Repository Language Settings ~168
Updates the language response settings for a specific repository, controlling which programming languages are recognized and analyzed. Use this to tailor language detection behavior for a given repository within an organization.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | array | yes | The complete list of languages to configure for this repository. Each item should represent a language identifier; order is not significant, and the full desired set must be provided as this replaces… |
| 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.
configure_repository_tool Configure Repository Tool ~207
Enable or disable an analysis tool and its patterns for a specific repository. Changes are applied immediately without checking whether the repository is linked to a coding standard.
| Name | Type | Req | Description |
|---|---|---|---|
| enabled | boolean | – | Set to true to enable the tool for analysis or false to disable it entirely for this repository. |
| patterns | array | – | List of pattern objects to enable or disable for this tool; each item should specify the pattern identifier and its desired enabled state. Order is not significant. |
| provider | string | yes | Identifier for 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 specified organization on the Git provider. |
| toolUuid | string | yes | UUID uniquely identifying the analysis tool to configure. |
| useConfigurationFile | boolean | – | Set to true to have the tool read its settings from a configuration file in the repository, or false to use Codacy-managed settings. |
No output schema declared.
No examples provided.
create_api_token Create API Token ~73
Creates a new account-level API token for the authenticated user, optionally scoped to a specific expiration date. API tokens are used to authenticate requests to the Codacy.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresAt | string | – | Optional expiration date and time for the API token in ISO 8601 format. If omitted, the token does not expire. |
No output schema declared.
No examples provided.
create_coding_standard Create Coding Standard ~227
Creates a new draft coding standard for an organization, optionally using an existing repository or coding standard as a template. The draft must be promoted to become effective; use promoteDraftCodingStandard to complete that step.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | array | yes | List of programming languages the new coding standard will cover. Order is not significant; each item should be a supported language name. |
| name | string | yes | Human-readable name for the new coding standard, used to identify it within the organization. |
| provider | string | yes | Short code identifying the Git provider hosting the organization (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. |
| sourceCodingStandard | string | – | Numeric identifier of an existing coding standard to use as a template, carrying over its enabled repositories and default coding standard status to the new one. |
| sourceRepository | string | – | Name of an existing repository within the same organization to use as a template for tool and language settings when creating the new coding standard. |
No output schema declared.
No examples provided.
create_coding_standard_from_preset Create Coding Standard from Preset ~367
Creates a new coding standard for an organization by selecting preset severity levels across key code quality categories. Optionally sets the new standard as the organization's default.
| Name | Type | Req | Description |
|---|---|---|---|
| bestPractices | string | yes | Preset level for best practice rules, controlling how strictly deviations from recommended coding conventions are flagged. Accepts values from 1 (least strict) to 4 (most strict). |
| bugRisk | string | yes | Preset level for bug risk rules, controlling how strictly potential bugs and error-prone patterns are flagged. Accepts values from 1 (least strict) to 4 (most strict). |
| codeStyle | string | yes | Preset level for code style rules, controlling how strictly formatting and stylistic inconsistencies are flagged. Accepts values from 1 (least strict) to 4 (most strict). |
| documentation | string | yes | Preset level for documentation rules, controlling how strictly missing or inadequate code documentation is flagged. Accepts values from 1 (least strict) to 4 (most strict). |
| isDefault | boolean | yes | When set to true, this coding standard will automatically become the default applied to all repositories in the organization. |
| name | string | – | A human-readable label for the new coding standard to help identify it within the organization. |
| 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. |
| security | string | yes | Preset level for security rules, controlling how strictly security vulnerabilities and unsafe coding patterns are flagged. Accepts values from 1 (least strict) to 4 (most strict). |
No output schema declared.
No examples provided.
create_compliance_standard Create Compliance Standard ~145
Creates a new compliance standard for the specified organization on a Git provider. Use this to establish compliance frameworks, such as AI risk policies, that govern code quality and usage rules across the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| complianceType | string | yes | The category of compliance standard to create. Currently supports AI risk compliance, which enforces policies around AI-generated code usage. |
| name | string | yes | A human-readable display name for the compliance standard being created. |
| provider | string | yes | Short code identifying the Git provider hosting the organization (e.g., GitHub, GitLab, Bitbucket). |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
No output schema declared.
No examples provided.
create_dast_target Create DAST Target ~221
Creates a new Dynamic Application Security Testing (DAST) target for a specified organization, defining the URL and type of application to be scanned for vulnerabilities.
| Name | Type | Req | Description |
|---|---|---|---|
| apiDefinitionUrl | string | – | The URL pointing to the API definition file (e.g., an OpenAPI or GraphQL schema), required when the target type is 'openapi' or 'graphql'. |
| provider | string | yes | Short code identifying the Git provider hosting the organization (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. |
| targetType | string | – | Specifies the type of DAST target to scan: 'webapp' for standard web applications, 'openapi' for REST APIs described by an OpenAPI specification, or 'graphql' for GraphQL APIs. Defaults to 'webapp' i… |
| url | string | yes | The fully qualified URL of the application or API endpoint to be scanned. Must be a valid URI. |
No output schema declared.
No examples provided.
create_gate_policy Create Gate Policy ~432
Creates a new quality gate policy for an organization on a Git provider, defining thresholds for issues, duplication, coverage, and complexity that must be met for a gate to pass.
| Name | Type | Req | Description |
|---|---|---|---|
| complexityThreshold | string | – | The maximum cumulative complexity value allowed before the quality gate fails; must be zero or greater. |
| coverageThresholdWithDecimals | number | – | The minimum change in coverage percentage required to pass the quality gate; use a negative value to allow coverage to decrease by that amount (e.g., -0.02 allows up to a 2% drop). Must be at most 1.… |
| diffCoverageThreshold | string | – | The minimum diff coverage percentage required to pass the quality gate; must be between 0 and 100 inclusive. |
| duplicationThreshold | string | – | The maximum number of new duplicated blocks allowed before the quality gate fails. |
| gatePolicyName | string | yes | A unique, human-readable name to identify this gate policy within the organization. |
| isDefault | boolean | – | When true, this policy becomes the default gate policy applied to repositories in the organization that have no explicitly assigned policy. |
| minimumSeverity | string | – | The minimum severity level of issues counted toward the issue threshold. Severity levels map to the UI as: Info → Minor, Warning → Medium, High → High, Error → Critical. |
| 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. |
| securityIssueMinimumSeverity | string | – | The minimum severity level of security issues counted 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.
create_jira_ticket Create Jira Ticket ~328
Creates a new Jira ticket linked to a specific Codacy organization, associating it with one or more code elements such as issues, findings, files, or dependencies.
| Name | Type | Req | Description |
|---|---|---|---|
| createJiraTicketElements | array | yes | List of code element identifiers to associate with the Jira ticket; each item should correspond to an element of the specified elementType. Order is not significant. |
| description_body | string | – | Main body text of the Jira ticket description. Use newlines to separate paragraphs. |
| description_bullet_points | array | – | Optional list of bullet point strings to append after the body text |
| description_heading | string | – | Optional heading text to appear at the top of the Jira ticket description (rendered as a level-2 heading) |
| dueDate | string | – | Optional target completion date for the ticket, specified in YYYY-MM-DD format. |
| elementType | string | yes | The category of code element the Jira ticket will be associated with, such as a code issue, security finding, file, or dependency. |
| issueTypeId | string | yes | The numeric identifier of the Jira issue type (e.g., Bug, Task, Story) to assign to the new ticket. |
| jiraProjectId | string | yes | The unique numeric identifier of the Jira project in which the ticket will be created. |
| 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. |
| summary | string | yes | A short, descriptive title summarizing the purpose or content of the Jira ticket. |
No output schema declared.
No examples provided.
create_post_commit_hook Create Post Commit Hook ~124
Creates a post-commit hook integration for a repository, enabling Codacy to receive commit notifications and trigger analysis automatically after each push.
| 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 or account on the Git provider under which the repository resides. |
| repositoryName | string | yes | The name of the repository within the specified Git provider organization for which the post-commit hook will be created. |
No output schema declared.
No examples provided.
create_repository_token Create Repository Token ~108
Creates a new API token scoped to a specific repository, enabling authenticated access to that repository's resources via the Codacy.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short code identifying 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 platform. |
| repositoryName | string | yes | The repository name within the specified organization on the Git provider. |
No output schema declared.
No examples provided.
decline_organization_join_requests Decline Organization Join Requests ~115
Declines pending requests from users seeking to join a specified organization on a Git provider. Targets the organization by provider and name, rejecting the specified user emails.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Identifier for the Git provider hosting the organization. Use the short code 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. This must match the exact organization identifier used by the provider. |
No output schema declared.
No examples provided.
delete_billing_subscription Delete Billing Subscription ~93
Permanently removes the billing subscription for a specified organization on a given Git provider. This action cancels the organization's current billing plan and cannot be undone.
| 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 specified Git provider. |
No output schema declared.
No examples provided.
delete_coding_standard Delete Coding Standard ~120
Permanently deletes a coding standard from the specified organization. This action is irreversible and removes all associated rule configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| codingStandardId | string | yes | The unique numeric identifier of the coding standard to delete, as returned when the coding standard was created or listed. |
| 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. |
No output schema declared.
No examples provided.
delete_dast_target Delete DAST Target ~108
Permanently deletes a DAST (Dynamic Application Security Testing) target from the specified organization. This removes the target configuration and stops any associated security scans.
| Name | Type | Req | Description |
|---|---|---|---|
| dastTargetId | string | yes | The unique numeric identifier of the DAST target to delete. |
| 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.
delete_dormant_accounts Delete Dormant Accounts ~63
Permanently deletes Codacy user accounts identified as dormant, based on a CSV file exported from GitHub Enterprise. Restricted to Codacy administrators only.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | – | Raw CSV content exported from GitHub Enterprise identifying the dormant user accounts to be deleted. |
No output schema declared.
No examples provided.
delete_enterprise_token Delete Enterprise Token ~68
Deletes the stored GitHub Enterprise account token for the authenticated user. Once removed, the token will no longer be used to access enterprise-level resources.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Identifier for the Git provider whose enterprise token should be deleted. Accepts short provider codes representing supported Git hosting services. |
No output schema declared.
No examples provided.
delete_gate_policy Delete Gate Policy ~109
Permanently deletes a specific gate policy from an organization on the specified Git provider. This action is irreversible and removes all associated policy configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| gatePolicyId | string | yes | The unique numeric identifier of the gate policy to delete. |
| provider | string | yes | Short code identifying the Git provider for the organization (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.
delete_image_sboms Delete Image SBOMs ~143
Deletes all Software Bill of Materials (SBOMs) associated with a specific container image in the given organization. This action is irreversible and removes all SBOM records for the specified image.
| Name | Type | Req | Description |
|---|---|---|---|
| imageName | string | yes | The name of the container image whose SBOMs should be deleted. Must match the image name used when the SBOMs were originally uploaded. |
| 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.
delete_image_tag_sbom Delete Image Tag SBOM ~150
Deletes the SBOM (Software Bill of Materials) associated with a specific image and tag combination within an organization. This action permanently removes the SBOM data for the given image/tag pair.
| Name | Type | Req | Description |
|---|---|---|---|
| imageName | string | yes | The name of the container image whose SBOM entry is being deleted. |
| 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. |
| tag | string | yes | The specific tag of the container image whose SBOM entry is being deleted. |
No output schema declared.
No examples provided.
delete_integration Delete Integration ~78
Permanently removes the connected Git provider integration for the authenticated user. Once deleted, the user will need to re-authenticate to restore access for that provider.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The identifier for the Git provider whose integration should be deleted. Accepted values include short codes for supported providers such as GitHub, GitLab, and Bitbucket. |
No output schema declared.
No examples provided.
delete_jira_integration Delete Jira Integration ~83
Removes the Jira integration and all associated resources from the specified organization on a Git provider. This action is irreversible and will disconnect Jira from the organization.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short code identifying the Git provider hosting the organization. Use the provider's abbreviated identifier. |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
No output schema declared.
No examples provided.
delete_organization Delete Organization ~95
Permanently removes an organization from Codacy by deleting its association with the specified Git provider. This action cannot be undone and will remove all related configuration and data within Codacy.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short identifier for the Git provider hosting the organization, such as GitHub, GitLab, or 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.
delete_organization_join_request Delete Organization Join Request ~116
Cancels or removes a pending request for a user to join an organization on the specified Git provider. Identified by the provider, organization name, and the user's account identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| accountIdentifier | string | yes | The unique numeric identifier of the user account whose join request should be deleted. |
| provider | string | yes | Short code identifying the Git provider hosting the organization (e.g., GitHub, GitLab, Bitbucket). |
| remoteOrganizationName | string | yes | The organization's name as it appears on the Git provider platform. |
No output schema declared.
No examples provided.
delete_repository Delete Repository ~120
Permanently removes the specified repository from the organization on the given Git provider. This action cannot be undone and will remove all associated data from Codacy.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 exact name of the organization on the Git provider that owns the repository. |
| repositoryName | string | yes | The exact name of the repository within the specified organization on the Git provider. |
No output schema declared.
No examples provided.
delete_repository_token Delete Repository Token ~126
Permanently deletes a specific API token associated with a repository by its unique ID. This revokes any access previously granted through that token.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | Short code identifying the Git provider hosting the organization and repository. |
| remoteOrganizationName | string | yes | The organization or account name as it appears on the Git provider platform. |
| repositoryName | string | yes | The repository name as it appears under the organization on the Git provider platform. |
| tokenId | string | yes | The numeric identifier of the repository API token to delete. Obtain this ID from the list repository tokens operation. |
No output schema declared.
No examples provided.
delete_user_token Delete User Token ~70
Permanently deletes a specific API token belonging to the authenticated user. Once deleted, any integrations or clients using this token will lose access immediately.
| Name | Type | Req | Description |
|---|---|---|---|
| tokenId | string | yes | The unique numeric identifier of the API token to delete. Obtain this ID from the list of tokens associated with the authenticated user's account. |
No output schema declared.
No examples provided.
duplicate_coding_standard Duplicate Coding Standard ~121
Creates a copy of an existing coding standard within the specified organization, preserving all rules and configurations from the original. Useful for creating variations of a standard without modifying the source.
| Name | Type | Req | Description |
|---|---|---|---|
| codingStandardId | string | yes | The unique numeric identifier of the coding standard to duplicate. |
| 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. |
No output schema declared.
No examples provided.
estimate_organization_billing Estimate Organization Billing ~151
Retrieves a billing cost estimation for an organization based on a specified payment plan and optional promotional code. Useful for previewing pricing before committing to a plan.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentPlanCode | string | yes | The code identifying the payment plan to estimate costs for. Available plan codes can be retrieved using the listPaymentPlans operation. |
| promoCode | string | – | An optional promotional code to apply discounts or adjustments to the billing estimation. |
| 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.
export_enterprise_seats_csv Export Enterprise Seats CSV ~101
Exports a CSV file containing seat allocation and usage data for a specified enterprise on a given Git provider. Useful for auditing license consumption and user activity across the enterprise.
| Name | Type | Req | Description |
|---|---|---|---|
| enterpriseName | string | yes | The unique slug (URL-friendly identifier) of the enterprise whose seat data should be exported. |
| provider | string | yes | The Git provider hosting the enterprise, identified by a short slug (e.g., GitHub, GitLab, Bitbucket). |
No output schema declared.
No examples provided.
export_organization_people_csv Export Organization People to CSV ~97
Generates and returns a CSV file listing all people in the specified organization, including their name, email, last login date, and last analysis date.
| Name | Type | Req | Description |
|---|---|---|---|
| provider | string | yes | The Git provider hosting the organization, identified by its 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.
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.