io.github.PierreJanineh/tech-debt-mcp
NPM · TECH-DEBT-MCP · SCANNED AUG 3
MCP Server for analyzing technical debt across multiple programming languages
Available components
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 →
Supply Chain Security87
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (105 of 109), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (105 of 109), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency97
- 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 70 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · tech-debt-mcp
claude mcp add pierrejanineh-tech-debt-mcp -- npx -y tech-debt-mcp
codex mcp add pierrejanineh-tech-debt-mcp -- npx -y tech-debt-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"pierrejanineh-tech-debt-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"tech-debt-mcp"
],
"enabled": true
}
}
} openclaw mcp add pierrejanineh-tech-debt-mcp --command npx --arg -y --arg tech-debt-mcp
mcp_servers:
pierrejanineh-tech-debt-mcp:
command: "npx"
args: ["-y", "tech-debt-mcp"] {
"mcpServers": {
"pierrejanineh-tech-debt-mcp": {
"command": "npx",
"args": [
"-y",
"tech-debt-mcp"
]
}
}
} 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 Aug 26 +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.
- 2 Aug 26 +53
- Provenance: unverified → pass ▲ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- 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 security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Maintenance: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- License: unverified → pass ▲ functional
- Schema quality: unverified → excellent ▲ functional
- Stability: unverified → 0.23 ▲ functional
- Licence: MIT functional
- 1 Aug 26 +5
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- MCP protocol: unverified → pass ▲ functional
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +4
- Malware scan: pass → unverified ▼ security
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 46
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance verified
Ecosystem: npm · Outcome: verified
Reason: verified
- 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:
- https://slsa.dev/provenance/v1
- Subject digest:
- sha512:b240e8124b7f2d76241c9d8401f084f2023e3cb5130838be20c74944d44b7c7d5349989b80c16889aaf010125e3b9f8dba95e5a9c9623aae3a8e83fa9
- Discovery method:
- attestation_endpoint
Dependencies 105 packages
105 packages in the resolved dependency tree · 105 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.