Code Health Suite

io.github.neogeweb3Published by GitHub account neogeweb3v0.8.1Updated Nov 3, 2026

16 engines, 28 MCP tools for Python code quality. Zero external dependencies.

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Local Python code-quality server exposing 28 tools across 16 analysis engines for complexity, security, dead code, clones, tests and git health.

What you can do
  • Analyze complexity and get project health scores
  • Find dead code, unused imports and arguments
  • Run security scans with OWASP and CWE-mapped findings
  • Inspect import graphs, circular dependencies and module coupling
  • Detect code clones and assess test suite quality
  • Audit dependencies, type annotations, environment variables and git commits
When to use it
Useful when an assistant should review a Python codebase for maintainability, security and test quality, or produce scored health reports and change-impact analysis without leaving the chat.
Requirements
Runs as a local stdio process on the user's machine (desktop only). Needs Python 3.10+ and the code-health-suite package from PyPI, installed with pip or run via uvx. No external dependencies, accounts, API keys or environment variables are declared.
Before you install
It reads project source, git history and environment variable names, so results may expose sensitive details in the conversation. Analysis is read-only per the listed tools, but review any report before sharing it outside the project.

Installation

In SourceWeft

  1. Open Code Health Suite in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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)

json
{  "mcpServers": {    "code-health": {      "command": "code-health-suite"    }  }}

Install from PyPI

bash
pip install code-health-suite

Or with uvx (no install needed):

bash
uvx code-health-suite

Install from GitHub

bash
pip install git+https://github.com/nge/code-health-suite

Tools

#ToolEngineWhat it does
1analyze_complexitycomplexityPer-function CC, cognitive complexity, nesting, grades
2get_complexity_scorecomplexityProject health score 0-100
3find_dead_codedead-codeUnused imports, functions, variables, arguments
4security_scansecurityOWASP vulns, CWE-mapped findings
5get_security_scoresecuritySecurity health score 0-100
6analyze_importsimport-graphImport dependency graph, circular deps
7get_import_healthimport-graphImport architecture score 0-100
8find_clonesclone-detectType-1/2/3 code clone detection
9analyze_test_qualitytest-qualityTest suite metrics, anti-patterns
10full_health_checkall enginesCombined report with overall grade
11find_hotspotshotspotFiles with high git churn AND high complexity
12get_hotspot_scorehotspotProject churn-complexity score
13audit_dependenciesdep-auditOutdated/vulnerable dependency check
14analyze_change_impactchange-impactBlast radius of file changes
15get_coupling_scorechange-impactModule coupling metrics
16analyze_typestype-auditType annotation coverage
17get_type_scoretype-auditType coverage score 0-100
18audit_envenv-auditEnvironment variable audit
19audit_git_commitsgit-auditCommit quality audit (security + complexity)
20get_git_audit_scoregit-auditGit commit health score

Requirements

  • Python 3.10+
  • Zero external dependencies (stdlib only)

License

MIT

Source: README.md at commit d554ec9

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.8.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.