@codacy/codacy-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 1 tool tried
Contacts while installing and starting: nothing
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @codacy/codacy-mcp@0.7.3
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
1 tool that takes no input and looks read-only was called once with nothing. 1 returned a result.
codacy_list_tools | Returned a result 0.4 s · 58,325 characters |
During the calls (not necessarily because of them) it first contacted: app.codacy.com.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
codacy_get_pattern toolUuid, patternId
Get the definition of a specific pattern. Common use cases: - When the user asks for the definition of a specific pattern - When the user asks for more information about an issue found by Codacy Common mistakes: - Using this tool with the wrong toolUuid - Using this tool with the wrong patternId
codacy_list_tools cursor, limit
List all code analysis tools available in Codacy.
codacy_cli_analyze provider, organization, repository, rootPath, file, tool
Run quality analysis locally using Codacy CLI. Use this tool to analyze the quality of a repository using Codacy command line. Common use cases: - When the user asks for an analysis of a repository - When the user asks to scan the code - When the user wants to analyze based on Codacy configuration - When the user wants to apply fixes based on Codacy configuration and analysis - When the user wants Codacy results immediately without waiting for the next scheduled analysis Common mistakes: - Using this tool to know the status of a repository - Using this tool without specifying the rootPath - Using this tool to know current results from Codacy. Use codacy_get_repository_with_analysis instead. - Filling the tool parameter when not asked specifically for it. - Using this tool for a organization other than the current one - Using this tool with the wrong organization name (if you are not sure, use the codacy_list_organizations tool to validate the organization name) - Using this tool without specifying the repository name - Using this tool for a repository other than the current one - Using this tool with the wrong repository name (if you are not sure, use the codacy_list_organization_repositories tool to validate the repository name)
codacy_cli_install provider, organization, repository
Install the Codacy CLI used for local analysis. Common use cases: - When the user tried to use Codacy CLI and it is not installed Common mistakes: - Using this tool for a organization other than the current one - Using this tool with the wrong organization name (if you are not sure, use the codacy_list_organizations tool to validate the organization name) - Using this tool without specifying the repository name - Using this tool for a repository other than the current one - Using this tool with the wrong repository name (if you are not sure, use the codacy_list_organization_repositories tool to validate the repository name)
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | not stated |
| Source | not stated |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-0BhNaIGU+ADzcJvGCoPUE6bQhzaVXWFCfK+sG3N0fvPM3ZMyYDRcdD5bKqTnSQOy06wIq53nu8L4XbdhfWgS/g== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 0.7.3 | 2026-11-16 | Starts with no setup | 4 |
| 0.7.2 | 2026-11-12 | Starts with no setup | 4 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40codacy/codacy-mcp)
New version out? Ask for a fresh report.