Analyze coupling metrics across the codebase. Identifies modules with high fan-out (too many dependencies) and tightly coupled clusters.

Analyze a codebase for dead code — functions, classes, and modules that are defined but never referenced. Returns findings with file paths, line numbers, severity, and fix suggestions.

Probe a remote MCP server: Streamable HTTP / SSE handshake (initialize + tools/list), a known-bad tools/call error-shape probe, and a Streamable HTTP diagnostic matrix (WRONG_METHOD, WRONG_ACCEPT, MISSING_SESSION, GET_VS_POST, SESSION_STICKY_MISMATCH). HTTP 200 is not treated as healthy.

Detect architectural drift — violations of intended layer boundaries (e.g., UI importing from data layer, reverse dependencies).

Detect circular dependencies between modules using DFS-based cycle detection. Returns cycles with involved files and impact assessment.

Get a detailed explanation of a specific code health finding, including why it matters, potential risks, and detailed remediation steps.

Run a complete codebase health scan: dead code, circular dependencies, coupling metrics, and architectural drift. Returns an overall health score (0-100) and prioritized findings.