io.github.PierreJanineh/tech-debt-mcp
NPM · TECH-DEBT-MCP
MCP Server for analyzing technical debt across multiple programming languages
Available components
Last scanned (8 hours ago)
Scores higher than 93% of npm servers
Category Testing and QA
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects toml 4.3.0, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to PierreJanineh/TechDebtMCP). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 164 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 955 tokens (~59/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "execute_custom_rules" implies "execute" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: 0.97 → pass security
- 2 Nov 26 −1
- Stability: pass → 0.97 functional
- 31 Oct 26 +1
- CVE-2026-118773 affects this package: high ▼ security
- CVE-2026-118764 affects this package: high ▼ security
- Security disclosure: unverified → pass ▲ functional
- 30 Oct 26 −1
- Security disclosure: pass → unverified ▼ functional
- 27 Oct 26 +1
- CVE-2026-114142 affects this package: high ▼ security
- Stability: 0.97 → pass security
- 26 Oct 26 −1
- Stability: pass → 0.97 functional
- 23 Oct 26 −5
- CVE-2026-114141 affects this package: high ▼ security
- CVE-2026-114144 affects this package: high ▼ security
- CVE-2026-114143 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 +1
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/tech-debt-mcp@2.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | PierreJanineh/TechDebtMCP |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/PierreJanineh/TechDebtMCP/.github/workflows/publish.yml@refs/tags/v2.1.0 |
| Rekor log index | 1619276525 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b240e8124b7f2d76241c9d8401f084f2023e3cb5130838be20c74944d44b7c7d5349989b80c16889aaf010125e3b9f8dba95e5a9c9623aae3a8e83fa9 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-3g3m-2fjr-6pw4 | CVE-2026-118773 | medium | yes | |
| GHSA-g3hv-75wg-m249 | CVE-2026-118764 | medium | yes | |
| GHSA-4qx8-w7c3-pj3p | CVE-2026-114141 | high | yes | |
| GHSA-9j65-hcg3-gc64 | CVE-2026-114143 | high | yes | |
| GHSA-9qmh-m7c6-f92p | CVE-2026-114144 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-h895-cgqg-jf52 | CVE-2026-114142 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 103 packages
| Packages resolved | 103 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_custom_rule ~119
Add a custom pattern-based tech debt rule.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Debt category |
| flags | string | – | Optional: regex flags (g, i, m, s, etc.) |
| id | string | yes | Unique identifier for the rule |
| languages | array | – | Optional: apply only to specific languages |
| message | string | yes | Issue title/message |
| pattern | string | yes | Regex pattern to match |
| severity | string | yes | Issue severity level |
| suggestion | string | – | Optional: how to fix the issue |
No output schema declared.
No examples provided.
analyze_file ~31
Analyze a single file for technical debt issues.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the file to analyze |
No output schema declared.
No examples provided.
analyze_project ~107
Analyze an entire project for technical debt. Scans all supported files and returns a comprehensive report with issues, metrics, and recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Absolute path to the project root directory |
| severity | string | – | Optional: minimum severity level |
No output schema declared.
No examples provided.
check_dependencies ~47
Analyze project dependencies across multiple package managers.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDev | boolean | – | Optional: include development dependencies (default: true) |
| path | string | yes | Absolute path to the project root directory |
No output schema declared.
No examples provided.
execute_custom_rules ~98
Execute all custom rules against code or a file.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
get_debt_summary ~35
Get a quick summary of technical debt in a project.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the project root directory |
No output schema declared.
No examples provided.
get_issues_by_category ~44
Get all issues of a specific category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Category to filter by |
| path | string | yes | Absolute path to the project root directory |
No output schema declared.
No examples provided.
get_issues_by_severity ~47
Get all issues of a specific severity level.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the project root directory |
| severity | string | yes | Severity level to filter by |
No output schema declared.
No examples provided.
get_recommendations ~57
Get prioritized recommendations for addressing technical debt.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Optional: maximum number of recommendations to return (default: 5, minimum: 1) |
| path | string | yes | Absolute path to the project root directory |
No output schema declared.
No examples provided.
get_sqale_metrics ~60
Get SQALE technical debt metrics including remediation time, debt ratio, and rating.
| Name | Type | Req | Description |
|---|---|---|---|
| developmentTime | number | – | Optional: estimated development time in hours for debt ratio calculation |
| path | string | yes | Absolute path to the project root directory |
No output schema declared.
No examples provided.
get_vulnerability_report ~69
Generate an offline dependency report listing all project dependencies for vulnerability review. Note: actual CVE lookups require Phase 2b online integration.
| Name | Type | Req | Description |
|---|---|---|---|
| includeDev | boolean | – | Optional: include development dependencies (default: false) |
| path | string | yes | Absolute path to the project root directory |
No output schema declared.
No examples provided.
list_session_custom_rules ~73
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_supported_languages ~18
List all programming languages supported by the analyzer.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
remove_custom_rule ~29
Remove a custom rule by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | ID of the rule to remove |
No output schema declared.
No examples provided.
validate_config ~49
Validate a .techdebtrc.json configuration file for syntax and schema correctness.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Absolute path to the project root directory or directly to a .techdebtrc.json file |
No output schema declared.
No examples provided.
validate_custom_pattern ~72
Validate a custom pattern before adding it as a rule.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | Debt category |
| id | string | yes | Unique identifier for the rule |
| message | string | yes | Issue title/message |
| pattern | string | yes | Regex pattern to validate |
| severity | string | yes | Issue severity level |
No output schema declared.
No examples provided.
How do I install the io.github.PierreJanineh/tech-debt-mcp server?
io.github.PierreJanineh/tech-debt-mcp runs locally as an npm package, launched with npx -y tech-debt-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · tech-debt-mcp
claude mcp add pierrejanineh-tech-debt-mcp -- npx -y tech-debt-mcp
What is the io.github.PierreJanineh/tech-debt-mcp server?
io.github.PierreJanineh/tech-debt-mcp is listed in the public MCP registry as io.github.PierreJanineh/tech-debt-mcp. MCP Server for analyzing technical debt across multiple programming languages. This page covers its npm package (tech-debt-mcp).
Is the io.github.PierreJanineh/tech-debt-mcp server safe to use?
io.github.PierreJanineh/tech-debt-mcp scores 90 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.PierreJanineh/tech-debt-mcp server expose?
io.github.PierreJanineh/tech-debt-mcp exposes 16 tools: analyze_project, analyze_file, get_debt_summary, get_sqale_metrics, list_supported_languages, and 11 more. Their descriptions and schemas cost roughly 955 tokens of context every time the server is loaded.
Is the io.github.PierreJanineh/tech-debt-mcp server still maintained?
io.github.PierreJanineh/tech-debt-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.PierreJanineh/tech-debt-mcp server under?
io.github.PierreJanineh/tech-debt-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.