Skip to main content
Glama
MCP Code Sanitizer

MCP Code Sanitizer

by notasandy

🔍 mcp-code-sanitizer

Ein strenger, KI-gestützter Code-Reviewer, der Ihren Code direkt über Claude Desktop, Cursor oder einen beliebigen MCP-kompatiblen Agenten durch das Groq LLM laufen lässt.

Python FastMCP Groq License

Claude Desktop  ──MCP──►  code-sanitizer  ──REST──►  Groq API
                            (server.py)               (llama-3.3-70b)

✨ Funktionen

Tool

Beschreibung

analyze_code

Strenger Code-Review — Fehler, Schwachstellen, Bewertung 0–100

compare_code

Vergleicht zwei Versionen, findet Regressionen, empfiehlt Merge/request_changes

explain_code

Schritt-für-Schritt-Erklärung für Junior/Middle/Senior-Zielgruppen

generate_tests

Generiert pytest/jest/go-Tests mit Happy Path, Edge Cases und Sicherheitstests

analyze_file

Analysiert eine ganze Datei von der Festplatte mit parallelem Chunking

generate_report

Erstellt einen schönen HTML-Bericht aus jedem Analyseergebnis

cache_info

Cache-Statistiken und Bereinigung

Beispielantwort

{
  "summary": "Critical SQL injection and secret exposed in logs",
  "score": 23,
  "issues": [
    {
      "severity": "critical",
      "line": 2,
      "title": "SQL Injection",
      "description": "f-string directly interpolates user_id into query",
      "fix": "cursor.execute('SELECT * FROM users WHERE id = %s', (user_id,))"
    }
  ],
  "warnings": [{"title": "No exception handling", "description": "..."}],
  "suggestions": ["Consider using an ORM instead of raw SQL"]
}

Related MCP server: Claude Code Review MCP

🚀 Schnellstart

1. Repository klonen

git clone https://github.com/YOUR_USERNAME/mcp-code-sanitizer
cd mcp-code-sanitizer

2. Virtuelle Umgebung erstellen und Abhängigkeiten installieren

python -m venv venv

# macOS / Linux
source venv/bin/activate

# Windows
venv\Scripts\activate

pip install -r requirements.txt

3. Groq API-Schlüssel hinzufügen

Holen Sie sich einen kostenlosen Schlüssel unter console.groq.com/keys

cp .env.example .env
# Open .env and set GROQ_API_KEY=gsk_...

4. Server testen

python server.py

Stille bedeutet, dass es funktioniert – der Server wartet auf MCP-Anfragen über stdio.


🔌 Verbindung zu Claude Desktop

Suchen Sie Ihre Konfigurationsdatei und fügen Sie den Abschnitt mcpServers hinzu:

Betriebssystem

Konfigurationspfad

macOS

~/Library/Application Support/Claude/claude_desktop_config.json

Windows

%APPDATA%\Claude\claude_desktop_config.json

Linux

~/.config/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "code-sanitizer": {
      "command": "/full/path/to/venv/bin/python",
      "args": ["/full/path/to/server.py"],
      "env": {
        "GROQ_API_KEY": "gsk_your_key_here"
      }
    }
  }
}

Starten Sie Claude Desktop neu – Sie werden das 🔧-Symbol im Chat sehen.


🔌 Verbindung zu Cursor

Erstellen Sie .cursor/mcp.json in Ihrem Projektstammverzeichnis:

{
  "mcpServers": {
    "code-sanitizer": {
      "command": "/full/path/to/venv/bin/python",
      "args": ["/full/path/to/server.py"],
      "env": {"GROQ_API_KEY": "gsk_your_key_here"}
    }
  }
}

🧪 Testen über MCP Inspector

source venv/bin/activate  # or venv\Scripts\activate on Windows
fastmcp dev inspector server.py

Ein Browser-UI öffnet sich mit einer vollständigen Tool-Testoberfläche.


💬 Verwendung im Chat

Nachdem Sie eine Verbindung zu Claude Desktop hergestellt haben, schreiben Sie einfach:

Review this code for vulnerabilities:

def get_user(user_id):
    query = f"SELECT * FROM users WHERE id = {user_id}"
    return db.execute(query)

Oder rufen Sie explizit ein Tool auf:

Use analyze_file on /path/to/my_script.py
Generate tests for this function: ...
Compare these two versions and tell me if it got better: ...

🏗️ Architektur

mcp-code-sanitizer/
├── server.py          # FastMCP entry point (39 lines)
├── config.py          # Constants — keys, limits, mappings
├── groq_client.py     # Groq API client with auto-retry on rate limits
├── cache.py           # In-memory cache with TTL
├── prompts.py         # System prompts for all tools
└── tools/
    ├── analyze.py     # analyze_code
    ├── compare.py     # compare_code
    ├── explain.py     # explain_code
    ├── tests.py       # generate_tests
    ├── file_tool.py   # analyze_file (chunking + parallel analysis)
    ├── cache_tool.py  # cache_info
    └── report.py      # generate_report (HTML)

⚙️ Konfiguration

Alle Einstellungen erfolgen über Umgebungsvariablen oder .env:

Variable

Standard

Beschreibung

GROQ_API_KEY

—

Erforderlich. Erhältlich unter console.groq.com

GROQ_MODEL

llama-3.3-70b-versatile

Groq-Modell

CACHE_TTL

3600

Cache-TTL in Sekunden

CACHE_MAX

200

Maximale Cache-Einträge

Verfügbare Groq-Modelle

Modell

Geschwindigkeit

Qualität

llama-3.3-70b-versatile

⚡⚡

⭐⭐⭐⭐⭐ (Standard)

llama-3.1-8b-instant

⚡⚡⚡

⭐⭐⭐

mixtral-8x7b-32768

⚡⚡

⭐⭐⭐⭐


📦 Anforderungen

fastmcp>=2.3.0
httpx>=0.27.0
python-dotenv>=1.0.0

🤝 Mitwirken

PRs und Issues sind willkommen! Besonders interessiert an:

  • Unterstützung für andere LLM-Anbieter (OpenAI, Anthropic)

  • Neue Tools (Sicherheitsaudit, Abhängigkeitsprüfung, Komplexitätsanalyse)

  • Prompt-Verbesserungen


📄 Lizenz

MIT — tun Sie, was Sie wollen. Ein GitHub-Stern wäre geschätzt ⭐


Available Tools

7 tools
analyze_codeC

Strict analysis of a code fragment using Groq LLM.

Inputs: code (required), language, context. Returns: result

analyze_fileA

Analyzes a whole code file from disk. Automatically detects language by file extension. Large files are split into chunks and analyzed in parallel.

Inputs: file_path (required), language, context. Returns: result

cache_infoA

Shows cache statistics or clears the cache Args: clear: True - clears the cache, False - shows statistics.

Returns: JSON with cache stats or clear result.

Inputs: clear. Returns: result

compare_codeA

Compares two versions of code and evaluates whether the change is an improvement.

Performs a structured diff analysis: identifies what improved, what regressed, and what changed neutrally. Returns a merge recommendation based on the findings. Useful for code review, refactoring validation, and AI-generated code verification.

Inputs: code_before (required), code_after (required), language, context. Returns: result

explain_codeA

Explains what code does - step by step and clearly. Args: code: Code to explain. language: Programming language. audience: Target audience level - junior, middle, or senior. Returns: JSON with step-by-step explanation, key concepts, and gotchas.

Inputs: code (required), language, audience. Returns: result

generate_reportA

Generates a beautiful HTML report from analyze_code or analyze_file results. Args: analysis_json: JSON string from analyze_code or analyze_file. output_path: Path to save the HTML file (optional). source_name: File/fragment name for the report title. Returns: JSON with fields: html, saved_to, length.

Inputs: analysis_json (required), output_path, source_name. Returns: result

generate_testsA

Generates tests for the provided code. Args: code: Code to generate tests for. language: Programming language. framework: Test framework (optional - pytest, jest, unittest, etc.). Returns: JSON with test cases, runnable test code, and coverage estimate.

Inputs: code (required), language, framework. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: code fragment analysis, whole file analysis, cache management, code comparison, code explanation, report generation, and test generation. No overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using snake_case (e.g., analyze_code, generate_tests). No inconsistencies in style.

    Tool Count5/5

    7 tools is a well-scoped set for code analysis and sanitization tasks, covering the core operations without being overwhelming or too sparse.

    Completeness4/5

    The tool surface covers analysis, comparison, explanation, test generation, and reporting. A minor gap is the lack of code transformation or refactoring tools, but the set is reasonable for the stated domain.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      A server that enables interaction with PostgreSQL, MySQL, MariaDB, or SQLite databases through Claude Desktop using natural language queries.
      1
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables comprehensive security scanning of code projects, detecting vulnerabilities in dependencies, code patterns (XSS, eval, etc.), and exposed secrets, with detailed reports in Spanish prioritized by severity.
      4
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      AI-powered code review tool that detects AI-generated code defects invisible to traditional linters — hallucinated packages, deprecated APIs, cross-file contradictions, hidden security anti-patterns, and over-engineering. Works as a standalone CLI, GitHub Action, or MCP server. Supports TypeScript, Python, Java, Go, and Kotlin. Free for individuals, no API key required.
      4
      41
      Business Source 1.1