tech-debt-mcp

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Security

Grade A, and why

tech-debt-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

plugin/.claude-plugin/plugin.json · 28 lines

What it actually says

{
  "$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
  "name": "tech-debt-mcp",
  "displayName": "Tech Debt MCP",
  "version": "2.1.0",
  "description": "Static technical-debt analysis across 14 languages, exposed as MCP tools and resources (SQALE ratings, debt summaries, custom rules, dependency vulnerabilities).",
  "author": {
    "name": "Pierre Janineh",
    "url": "https://github.com/PierreJanineh"
  },
  "homepage": "https://github.com/PierreJanineh/TechDebtMCP#readme",
  "repository": "https://github.com/PierreJanineh/TechDebtMCP",
  "license": "MIT",
  "keywords": [
    "mcp",
    "tech-debt",
    "static-analysis",
    "code-quality",
    "sqale"
  ],
  "mcpServers": {
    "tech-debt-mcp": {
      "command": "npx",
      "args": ["-y", "tech-debt-mcp@latest"]
    }
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

Related

Other plugins, from other repositories