Skip to content
CAI
Software that uses CAICheck a score

newbpydev/mcp-diagnostics-extension

66.2

Adequate · 21 September 2026

6.5k

lines of production code

TypeScript

with JavaScript

4

measurements over time

CAI band scale
CAI trend line
CAI lens gauges

What this system is

This system is a VS Code extension that monitors and exposes IDE diagnostics through the Model Context Protocol (MCP). It automatically deploys and manages an MCP server to provide real-time diagnostic data to AI agents via tools, resources, and notifications. The extension handles cross-platform server installation, configuration, and lifecycle management while enforcing type safety and robust testing coverage.

Features

Add MCP Diagnostics extension commands and enhanced status bar

The MCP Diagnostics extension now includes a new \ExtensionCommands\ class that registers four VS Code commands: \mcpDiagnostics.restart\ to restart the server, \mcpDiagnostics.showStatus\ to view a detailed status webview, \mcpDiagnostics.showSetupGuide\ to display configuration instructions, and \mcpDiagnostics.configureServer\ to automatically deploy and configure the server. The extension also introduces a real-time, color-coded status bar that displays error and warning counts, updates automatically when diagnostics change, and provides interactive feedback for server state.

src/commands · high confidence

Added cross-platform utility functions for IDE configuration and server installation

New utility classes and functions were added to src/shared/utils to handle platform-specific logic. CrossPlatformUtils provides methods to retrieve IDE configuration paths for VS Code, Cursor, and Windsurf across Windows, macOS, and Linux, as well as platform-aware spawn options and command names. ServerInstallUtils introduces functions to determine the correct installation directory for the MCP Diagnostics server, compare semantic versions to decide if an upgrade is needed, and perform an atomic copy of the server binary with hash verification and rollback support.

src/shared/utils · high confidence

Added scripts for asset conversion, MCP server bootstrapping, and deployment validation

The scripts directory now includes three new files to support the extension's build and runtime environment. scripts/convert-assets.js converts SVG assets to PNG for the VS Code Marketplace. scripts/mcp-server.js provides a standalone Node.js bootstrap for the MCP server, handling module path resolution and cross-platform compatibility. scripts/validate-package.sh and scripts/validate-sprint4-deployment.js provide automated validation for package integrity, dependency inclusion, and Sprint 4 auto-deployment functionality.

scripts · high confidence

Added test workspace with TypeScript and ESLint configurations

A new test workspace has been added to the project, containing configuration files (.eslintrc.json, tsconfig.json) and sample source files (example.ts, typescript-issues.ts, utils.js) designed to trigger specific TypeScript and ESLint errors and warnings. This provides a dedicated environment for validating diagnostic tools and linting rules against known issues.

test-workspace · high confidence

Introduce diagnostics monitoring and performance tracking

Added the DiagnosticsWatcher class to monitor VS Code diagnostic changes and convert them into a standardized ProblemItem format via the new DiagnosticConverter. The DiagnosticsWatcher implements debounced event handling and resource disposal to prevent memory leaks. Additionally, a new PerformanceMonitor utility was introduced to track execution times and provide performance metrics for diagnostic processing and MCP responses.

src/core/diagnostics · high confidence

MCP Diagnostics Extension: Full activation, MCP server, and deployment logic

The extension now fully activates by initializing a DiagnosticsWatcher to monitor VS Code's problems panel, starting an MCP server to expose diagnostics to AI agents, and deploying a bundled MCP server binary to the user's directory. The activation process uses dependency injection for testability, registers extension commands and status bar updates, and handles optional MCP server registration. The architecture follows Clean Architecture principles with separate layers for core logic, infrastructure, and commands.

src · high confidence

MCP integration now exposes diagnostic data as tools, resources, and real-time notifications

The MCP infrastructure now provides a complete integration layer for AI agents and other MCP clients. Users can query diagnostic problems via three new tools (getProblems, getProblemsForFile, getProblemsForWorkspace) and access static or dynamic resources (summaries, file-specific, and workspace-specific diagnostics). Additionally, the extension supports real-time push notifications for diagnostic changes, allowing clients to subscribe to 'problemsChanged' events. Configuration validation ensures cross-platform compatibility and proper server setup.

src/infrastructure/mcp · high confidence

Standardize project configuration and documentation structure

The project's configuration and documentation structure has been standardized and expanded. A \.versionrc.json\ file was added to define the changelog generation format, commit types, and release scripts. Documentation files (CURSOR\_SETUP.md, MCP\_SERVER\_GUIDE.md, QUICK\_SETUP.md, TROUBLESHOOTING.md) were created or updated to reflect the latest features and setup instructions. Additionally, the \.gitignore\ and \.vscodeignore\ files were updated to exclude more build outputs, test files, and IDE-specific directories, while the \commitlint.config.js\ was added to enforce conventional commit message standards.

(repo-wide) · high confidence

Behavioural changes

Removed generated code coverage reports

The static assets and scripts used to render the Istanbul code coverage reports have been removed from the \coverage\ and \coverage/lcov-report\ directories. This includes CSS stylesheets (e.g., \base.css\, \prettify.css\), JavaScript files (e.g., \block-navigation.js\, \sorter.js\), and the HTML index pages that display the test coverage statistics. Users will no longer have access to the local HTML-based code coverage reports generated by the test suite.

coverage, coverage/lcov-report · high confidence

Shared types and constants refactored with Zod validation schemas

The shared layer now enforces type safety at runtime using Zod schemas for core types like ProblemItem, Position, Range, and DiagnosticsChangeEvent, replacing the previous plain TypeScript interfaces. Constants such as DEFAULT\_CONFIG, PERFORMANCE\_THRESHOLDS, ERROR\_CODES, and EVENT\_NAMES have been restructured and enriched with additional properties (e.g., memoryUsageMb, PERFORMANCE\_WARNING event) and detailed JSDoc comments. The VSCODE\_SEVERITY\_MAP is now explicitly typed as a Record\<number, ProblemSeverity\>, and MCP\_TOOLS now includes full input schemas for each tool.

src/shared · medium confidence

Fixes

Configure commit-msg and pre-commit hooks via Husky

Added .husky/commit-msg and .husky/pre-commit scripts to enforce commit message linting and pre-commit linting/formatting checks, resolving deprecation warnings and aligning the configuration with current best practices.

.husky · medium confidence

Test coverage

Added end-to-end tests for MCP diagnostics and auto-deployment; Added integration tests for MCP server and auto-deployment workflows; Added integration tests for extension activation and lifecycle; Added tests for critical dependency resolution; Added unit tests for DiagnosticsWatcher, DiagnosticConverter, and PerformanceMonitor; Added unit tests for MCP infrastructure components; Added unit tests for MCP server utility functions; Added unit tests for cross-platform and server installation utilities; Added unit tests for extension activation, deactivation, and error handling; Added unit tests for server deployment logic; Added unit tests for shared module constants, types, and schema validation; Added unit tests for the ExtensionCommands module; Added unit tests for the VsCodeApiAdapter; Expanded test suite for extension activation, deactivation, and error handling.

Dependencies

Updated dependencies and tooling for the MCP Diagnostics Extension

The extension's dependencies have been updated, including bumping the Model Context Protocol (MCP) SDK to version 1.12.3 and Zod to 3.25.56. Development tooling has been expanded with the addition of Husky, Commitlint, and standard-version, while the VS Code engine requirement has been adjusted to ^1.96.0 to improve compatibility.

(dependencies) · medium confidence

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

How this codebase got here

Score

  • CAI 63 → 66 (+3.1)
  • Rubric changed (rubric-2026.08.19 → rubric-2026.09.15) — scores are not directly comparable.

Lenses

  • Code Health 85 → 82 (-2.4)
  • Architecture 100 → 81 (-19.3)
  • Maturity 75 → 72 (-2.7)
  • Readiness 64 → 70 (+5.6)
  • Security 50 → 59 (+8.5)

Resolved (80)

  • Coverage not included — suite not readable by the collector
  • Critical CVE: [GHSA redacted] (package-lock.json)
  • Critical CVE: [GHSA redacted] (package-lock.json)
  • Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • …and 60 more

New (110)

  • ClassTooLong: McpServerRegistration (src/infrastructure/mcp/McpServerRegistration.ts)
  • ConfigurationValidator.validateCursorConfig (cognitive 24) (src/infrastructure/mcp/ConfigurationValidator.ts)
  • ConfigurationValidator.validateCursorConfig (cyclomatic 16) (src/infrastructure/mcp/ConfigurationValidator.ts)
  • ConfigurationValidator.validateVSCodeConfig (cognitive 27) (src/infrastructure/mcp/ConfigurationValidator.ts)
  • ConfigurationValidator.validateVSCodeConfig (cyclomatic 18) (src/infrastructure/mcp/ConfigurationValidator.ts)
  • ConfigurationValidator.validateWindsurfConfig (cognitive 21) (src/infrastructure/mcp/ConfigurationValidator.ts)
  • Critical CVE: [GHSA redacted] (package-lock.json)
  • Critical CVE: [GHSA redacted] (package-lock.json)
  • Dependency advisory scan runs only on code events
  • FunctionTooLong: extension.activate (src/extension.ts)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • High CVE: [GHSA redacted] (package-lock.json)
  • …and 90 more

Written by watchdog.canine.dev from the codebase's own history, inside the signed delivery this page is composed from.

Survey your own repository

newbpydev/mcp-diagnostics-extension was measured the same way every project in this corpus was: the same rubric, at a pinned commit, with the result published in full. Point a surveyor at a repository you know and see whether you agree with it.

About this page

  • The score is its most recent published measurement, taken on 21 September 2026 at a pinned commit. It is not a live figure and does not change until the project is measured again.
  • Measured at commit e0e62a6e8bde3f5d8bdbe89059469693f49580bb — the exact code this score is about.
  • Scored under rubric-2026.09.15 — the same rubric and the same method as every other entry in this index.
  • Measured by watchdog.canine.dev using codehealth-analyzer preprod-b84573e22831.