Code Health Suite
16 analysis engines, 28 MCP tools for Python code quality. Zero external dependencies.
Quick Start
As MCP Server (Claude Desktop / Claude Code)
{
"mcpServers": {
"code-health": {
"command": "code-health-suite"
}
}
}
Install from PyPI
pip install code-health-suite
Or with uvx (no install needed):
uvx code-health-suite
Install from GitHub
pip install git+https://github.com/nge/code-health-suite
Tools
| # | Tool | Engine | What it does |
|---|---|---|---|
| 1 | analyze_complexity |
complexity | Per-function CC, cognitive complexity, nesting, grades |
| 2 | get_complexity_score |
complexity | Project health score 0-100 |
| 3 | find_dead_code |
dead-code | Unused imports, functions, variables, arguments |
| 4 | security_scan |
security | OWASP vulns, CWE-mapped findings |
| 5 | get_security_score |
security | Security health score 0-100 |
| 6 | analyze_imports |
import-graph | Import dependency graph, circular deps |
| 7 | get_import_health |
import-graph | Import architecture score 0-100 |
| 8 | find_clones |
clone-detect | Type-1/2/3 code clone detection |
| 9 | analyze_test_quality |
test-quality | Test suite metrics, anti-patterns |
| 10 | full_health_check |
all engines | Combined report with overall grade |
| 11 | find_hotspots |
hotspot | Files with high git churn AND high complexity |
| 12 | get_hotspot_score |
hotspot | Project churn-complexity score |
| 13 | audit_dependencies |
dep-audit | Outdated/vulnerable dependency check |
| 14 | analyze_change_impact |
change-impact | Blast radius of file changes |
| 15 | get_coupling_score |
change-impact | Module coupling metrics |
| 16 | analyze_types |
type-audit | Type annotation coverage |
| 17 | get_type_score |
type-audit | Type coverage score 0-100 |
| 18 | audit_env |
env-audit | Environment variable audit |
| 19 | audit_git_commits |
git-audit | Commit quality audit (security + complexity) |
| 20 | get_git_audit_score |
git-audit | Git commit health score |
Requirements
- Python 3.10+
- Zero external dependencies (stdlib only)
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for code-health-suite 0.8.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| code_health_suite-0.8.1.tar.gz | 229.6 kB | With provenance | Details for code_health_suite-0.8.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| code_health_suite-0.8.1-py3-none-any.whl | Python 3 | none | any | Details for code_health_suite-0.8.1-py3-none-any.whl |
Total release size: 360.5 kB
Release files / code_health_suite-0.8.1.tar.gz
| Download URL | code_health_suite-0.8.1.tar.gz |
|---|---|
| Size | 229.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
22d3c111a6f7ffe1adc7b91d53f0943fb32d9aaab97892dda66153d8d561a6c9
|
|
BLAKE2b-256 checksum How to use checksums |
b316c1fd7db5978adaf12dd2838b3008ff729a0a6a9e22d98e471909508c478d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 19, 2026.
Transparency logRelease files / code_health_suite-0.8.1-py3-none-any.whl
| Download URL | code_health_suite-0.8.1-py3-none-any.whl |
|---|---|
| Size | 130.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34c764b7a29f36932ec657345c1dd5402654a3c249d5e00d7fcd1f7f89b75463
|
|
BLAKE2b-256 checksum How to use checksums |
b0ca39d40febd67f1dd6cf0c36b78a38eaa15df10aba71db17afe3043bda986b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 19, 2026.
Transparency logSecurity for code-health-suite 0.8.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for code_health_suite-0.8.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
