repo-forensics MCP — Cas d'usage, Installer & Démo en direct

Pourquoi l'utiliser

Fonctionnalités clés

18 scanners covering distinct threat surfaces
Skill-specific: SKILL.md poisoning, Unicode smuggling, OpenClaw patterns
MCP-specific: tool poisoning, rug-pull enablers
Correlation engine connects findings across scanners to catch compound attacks
Zero dependencies — pure audit, safe to run on anything

Démo en direct

Aperçu en pratique

repo-forensics-skill.replay ▶ prêt

0/0

Installer

Choisissez votre client

~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "repo-forensics-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ],
      "_inferred": true
    }
  }
}

Ouvrez Claude Desktop → Settings → Developer → Edit Config. Redémarrez après avoir enregistré.

~/.cursor/mcp.json · .cursor/mcp.json

{
  "mcpServers": {
    "repo-forensics-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ],
      "_inferred": true
    }
  }
}

Cursor utilise le même schéma mcpServers que Claude Desktop. La config projet l'emporte sur la globale.

VS Code → Cline → MCP Servers → Edit

{
  "mcpServers": {
    "repo-forensics-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ],
      "_inferred": true
    }
  }
}

Cliquez sur l'icône MCP Servers dans la barre latérale Cline, puis "Edit Configuration".

~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "repo-forensics-skill": {
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ],
      "_inferred": true
    }
  }
}

Même format que Claude Desktop. Redémarrez Windsurf pour appliquer.

~/.continue/config.json

{
  "mcpServers": [
    {
      "name": "repo-forensics-skill",
      "command": "git",
      "args": [
        "clone",
        "https://github.com/alexgreensh/repo-forensics",
        "~/.claude/skills/repo-forensics"
      ]
    }
  ]
}

Continue utilise un tableau d'objets serveur plutôt qu'une map.

~/.config/zed/settings.json

{
  "context_servers": {
    "repo-forensics-skill": {
      "command": {
        "path": "git",
        "args": [
          "clone",
          "https://github.com/alexgreensh/repo-forensics",
          "~/.claude/skills/repo-forensics"
        ]
      }
    }
  }
}

Ajoutez dans context_servers. Zed recharge à chaud à la sauvegarde.

claude mcp add repo-forensics-skill -- git clone https://github.com/alexgreensh/repo-forensics ~/.claude/skills/repo-forensics

Une seule ligne. Vérifiez avec claude mcp list. Supprimez avec claude mcp remove.

Cas d'usage

Usages concrets : repo-forensics

Audit a third-party skill before you clone it into ~/.claude/skills

👤 Anyone installing skills from strangers on GitHub ⏱ ~15 min beginner

Quand l'utiliser : Someone sent you a cool-looking skill link. Before clone, you want to know if it's safe.

Prérequis

repo-forensics installed — git clone https://github.com/alexgreensh/repo-forensics ~/.claude/skills/repo-forensics

Déroulement

Point at the target repo URL

Use repo-forensics. Scan https://github.com/<author>/<skill> with the skill_threats, secrets, dataflow, and lifecycle scanners. Report findings.✓ Copié

→ Per-scanner report with severity flags
Read correlated findings

Any correlations across scanners — e.g. a secret-leak path plus a lifecycle hook?✓ Copié

→ Correlation summary

Résultat : A go / no-go decision grounded in scanner output, not vibes.

Pièges

Trusting a green scan as full proof of safety — Scanners are strong floor, not a ceiling — still read SKILL.md

Combiner avec : github · filesystem

Audit an MCP server for tool poisoning and rug-pull patterns

👤 Teams onboarding a new MCP into a production agent stack ⏱ ~20 min intermediate

Quand l'utiliser : Before adding a new MCP server to an agent with real permissions.

Déroulement

Run MCP-focused scanners

Scan this MCP server repo with mcp_security, skill_threats, integrity, and dast.✓ Copié

→ Findings focused on tool descriptions and install scripts
Check git history for identity spoofing

Run git_forensics on the same repo — any spoofed commits?✓ Copié

→ Author / signing analysis

Résultat : An MCP security dossier before you wire it into your agent.

Run post-incident scanners after a suspicious install

👤 Anyone who just ran npm/pip install and feels uneasy ⏱ ~15 min intermediate

Quand l'utiliser : Install finished with unexpected behavior; you want to know if something landed.

Déroulement

Run post_incident + entropy scans

Run post_incident scanner on ~/.npm and the current project. Also entropy scan the installed packages.✓ Copié

→ Flags for suspicious cached artifacts or encoded payloads

Résultat : Evidence of whether to rotate secrets and rebuild.

Pièges

Running scans from the potentially-compromised shell — Run from a fresh shell or another machine when in doubt

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

repo-forensics-skill + github

Pull a PR's diff and scan only the added files

Fetch PR #123 and run repo-forensics just on the files it adds.✓ Copié

repo-forensics-skill + filesystem

Scan a locally cloned repo and save a JSON report

Scan ./suspicious-repo and write findings.json next to it.✓ Copié

Outils

Ce que ce MCP expose

Outil	Entrées	Quand appeler
skill_threats	repo path	Any skill audit
mcp_security	repo path	MCP audits
secrets	repo path	Always
dataflow	repo path	Suspicious egress concerns
lifecycle	repo path	Pre-install
git_forensics	repo path	Checking maintainer identity
entropy	repo path	Obfuscation suspected
sast	repo path	General code risk

Coût et limites

Coût d'exécution

Quota d'API: None
Tokens par appel: Moderate — scanner output summarization can grow
Monétaire: Free
Astuce: Run only the scanners relevant to the threat model (skills → skill_threats; MCP → mcp_security)

Sécurité

Permissions, secrets, portée

Stockage des identifiants : None — scanner is read-only

Sortie de données : Local-only by default

Ne jamais accorder : Write access to the repo under audit

This is a defensive tool. Don't use scanner output to stress-test your own targets — it's not a pentest kit.

Dépannage

Erreurs courantes et correctifs

Scanner reports 0 findings on obviously sketchy repo

Ensure you ran against the full repo path, not a subset; check scanner selection

Vérifier : repo-forensics list-scanners

False positives flood the report

Filter by severity; focus on high/critical; use correlation to prioritize

Alternatives

repo-forensics vs autres

Alternative	Quand l'utiliser	Compromis
claude-cybersecurity	Your code needs OWASP-style app security review rather than supply-chain vetting	Different focus — app logic vs install-time threats
gitleaks / trufflehog	You only need secret scanning	Single-scanner, not correlation

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills