# io.github.PierreJanineh/tech-debt-mcp (npm · tech-debt-mcp)

MCP Server for analyzing technical debt across multiple programming languages

- Trust score: 80/100 (high trust)
- Change this week: +34
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `tech-debt-mcp`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pierrejanineh-tech-debt-mcp/tech-debt-mcp.md), [page](https://verifymcp.io/servers/pierrejanineh-tech-debt-mcp/tech-debt-mcp)

## Channel facts

- Registry: `npm`
- Package: `tech-debt-mcp`
- Version: `2.1.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (105 of 109), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (105 of 109), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to PierreJanineh/TechDebtMCP).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 70 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 955 tokens (~59/item across 16 items; 16 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add pierrejanineh-tech-debt-mcp -- npx -y tech-debt-mcp
```

### Codex

```bash
codex mcp add pierrejanineh-tech-debt-mcp -- npx -y tech-debt-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pierrejanineh-tech-debt-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "tech-debt-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pierrejanineh-tech-debt-mcp --command npx --arg -y --arg tech-debt-mcp
```

### Hermes

```yaml
mcp_servers:
  pierrejanineh-tech-debt-mcp:
    command: "npx"
    args: ["-y", "tech-debt-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "pierrejanineh-tech-debt-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "tech-debt-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 79, +53)

- [security improvement] Provenance: unverified → pass
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [security] The attested source repository moved: PierreJanineh/TechDebtMCP
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Stability: unverified → 0.23
- [functional] Licence: MIT

### 2026-08-01 (score 26, +5)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional improvement] MCP protocol: unverified → pass

### 2026-07-31 (score 21, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 28, +4)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −22)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 46)

First indexed and scored.

## MCP tools (16)

### `analyze_project` (~107 tokens)

Analyze an entire project for technical debt. Scans all supported files and returns a comprehensive report with issues, metrics, and recommendations.

Input parameters:

- `categories` (array): Optional: filter by debt categories
- `languages` (array): Optional: specific languages to analyze
- `maxFiles` (integer): Optional: maximum number of files to analyze (minimum: 1)
- `path` (string, required): Absolute path to the project root directory
- `severity` (string): Optional: minimum severity level

### `analyze_file` (~31 tokens)

Analyze a single file for technical debt issues.

Input parameters:

- `path` (string, required): Absolute path to the file to analyze

### `get_debt_summary` (~35 tokens)

Get a quick summary of technical debt in a project.

Input parameters:

- `path` (string, required): Absolute path to the project root directory

### `get_sqale_metrics` (~60 tokens)

Get SQALE technical debt metrics including remediation time, debt ratio, and rating.

Input parameters:

- `developmentTime` (number): Optional: estimated development time in hours for debt ratio calculation
- `path` (string, required): Absolute path to the project root directory

### `list_supported_languages` (~18 tokens)

List all programming languages supported by the analyzer.

### `get_recommendations` (~57 tokens)

Get prioritized recommendations for addressing technical debt.

Input parameters:

- `limit` (integer): Optional: maximum number of recommendations to return (default: 5, minimum: 1)
- `path` (string, required): Absolute path to the project root directory

### `get_issues_by_severity` (~47 tokens)

Get all issues of a specific severity level.

Input parameters:

- `path` (string, required): Absolute path to the project root directory
- `severity` (string, required): Severity level to filter by

### `get_issues_by_category` (~44 tokens)

Get all issues of a specific category.

Input parameters:

- `category` (string, required): Category to filter by
- `path` (string, required): Absolute path to the project root directory

### `add_custom_rule` (~119 tokens)

Add a custom pattern-based tech debt rule.

Input parameters:

- `category` (string, required): Debt category
- `flags` (string): Optional: regex flags (g, i, m, s, etc.)
- `id` (string, required): Unique identifier for the rule
- `languages` (array): Optional: apply only to specific languages
- `message` (string, required): Issue title/message
- `pattern` (string, required): Regex pattern to match
- `severity` (string, required): Issue severity level
- `suggestion` (string): Optional: how to fix the issue

### `remove_custom_rule` (~29 tokens)

Remove a custom rule by ID.

Input parameters:

- `id` (string, required): ID of the rule to remove

### `list_session_custom_rules` (~73 tokens)

List custom rules registered in this server session via add_custom_rule. Does NOT include customPatterns declared in .techdebtrc.json (those run inside analyze_project via AnalysisEngine but are not surfaced here). Renamed from list_custom_rules (TEC-51) for clarity; the old name is no longer registered.

### `execute_custom_rules` (~98 tokens)

Execute all custom rules against code or a file.

Input parameters:

- `code` (string): Source code content to analyze directly (maximum 500000 characters; alternative to path). Either path or code must be provided.
- `language` (string): Optional: programming language for filtering rules
- `path` (string): Absolute filesystem path to the file to analyze (maximum 500000 bytes). An empty string is treated the same as omitting the field.

### `validate_custom_pattern` (~72 tokens)

Validate a custom pattern before adding it as a rule.

Input parameters:

- `category` (string, required): Debt category
- `id` (string, required): Unique identifier for the rule
- `message` (string, required): Issue title/message
- `pattern` (string, required): Regex pattern to validate
- `severity` (string, required): Issue severity level

### `check_dependencies` (~47 tokens)

Analyze project dependencies across multiple package managers.

Input parameters:

- `includeDev` (boolean): Optional: include development dependencies (default: true)
- `path` (string, required): Absolute path to the project root directory

### `validate_config` (~49 tokens)

Validate a .techdebtrc.json configuration file for syntax and schema correctness.

Input parameters:

- `path` (string, required): Absolute path to the project root directory or directly to a .techdebtrc.json file

### `get_vulnerability_report` (~69 tokens)

Generate an offline dependency report listing all project dependencies for vulnerability review. Note: actual CVE lookups require Phase 2b online integration.

Input parameters:

- `includeDev` (boolean): Optional: include development dependencies (default: false)
- `path` (string, required): Absolute path to the project root directory

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pierrejanineh-tech-debt-mcp/tech-debt-mcp#diagnostics

## Score history

- 2026-08-03: 80
- 2026-08-02: 79
- 2026-08-01: 26
- 2026-07-31: 21
- 2026-07-30: 28
- 2026-07-28: 24
- 2026-07-27: 46

## Links

- npm package: https://www.npmjs.com/package/tech-debt-mcp
- Socket report: https://socket.dev/npm/package/tech-debt-mcp
- Repository: https://github.com/PierreJanineh/TechDebtMCP
- Changelog RSS feed: https://verifymcp.io/servers/pierrejanineh-tech-debt-mcp/tech-debt-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/pierrejanineh-tech-debt-mcp/tech-debt-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/pierrejanineh-tech-debt-mcp/tech-debt-mcp