MCP Code Sanitizer
🔍 mcp-code-sanitizer
Claude Desktop、Cursor、またはMCP互換エージェントから直接Groq LLMを使用してコードをレビューする、厳格なAI駆動型コードレビューツールです。
Claude Desktop ──MCP──► code-sanitizer ──REST──► Groq API
(server.py) (llama-3.3-70b)✨ 機能
ツール | 説明 |
| 厳格なコードレビュー — バグ、脆弱性、0〜100のスコア評価 |
| 2つのバージョンを比較し、リグレッションを検出し、マージまたは変更リクエストを推奨 |
| ジュニア/ミドル/シニア層に向けたステップバイステップの解説 |
| 正常系、エッジケース、セキュリティテストを含むpytest/jest/goテストを生成 |
| ディスク上のファイル全体を並列チャンク処理で分析 |
| 分析結果から美しいHTMLレポートを作成 |
| キャッシュ統計の表示とクリア |
レスポンス例
{
"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
🚀 クイックスタート
1. リポジトリのクローン
git clone https://github.com/YOUR_USERNAME/mcp-code-sanitizer
cd mcp-code-sanitizer2. 仮想環境の作成と依存関係のインストール
python -m venv venv
# macOS / Linux
source venv/bin/activate
# Windows
venv\Scripts\activate
pip install -r requirements.txt3. Groq APIキーの追加
console.groq.com/keys で無料キーを取得してください。
cp .env.example .env
# Open .env and set GROQ_API_KEY=gsk_...4. サーバーのテスト
python server.py何も表示されなければ正常に動作しています。サーバーはstdio経由でMCPリクエストを待機しています。
🔌 Claude Desktopへの接続
設定ファイルを見つけて mcpServers セクションを追加します:
OS | 設定パス |
macOS |
|
Windows |
|
Linux |
|
{
"mcpServers": {
"code-sanitizer": {
"command": "/full/path/to/venv/bin/python",
"args": ["/full/path/to/server.py"],
"env": {
"GROQ_API_KEY": "gsk_your_key_here"
}
}
}
}Claude Desktopを再起動すると、チャット内に 🔧 アイコンが表示されます。
🔌 Cursorへの接続
プロジェクトのルートに .cursor/mcp.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"}
}
}
}🧪 MCP Inspectorによるテスト
source venv/bin/activate # or venv\Scripts\activate on Windows
fastmcp dev inspector server.pyブラウザUIが開き、完全なツールテストインターフェースが利用可能になります。
💬 チャットでの使用方法
Claude Desktopに接続した後、以下のように入力するだけです:
Review this code for vulnerabilities:
def get_user(user_id):
query = f"SELECT * FROM users WHERE id = {user_id}"
return db.execute(query)または、明示的にツールを呼び出します:
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: ...🏗️ アーキテクチャ
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)⚙️ 設定
すべての設定は環境変数または .env ファイル経由で行います:
変数 | デフォルト | 説明 |
| — | 必須。console.groq.comで取得 |
|
| Groqモデル |
|
| キャッシュのTTL(秒) |
|
| キャッシュの最大エントリ数 |
利用可能なGroqモデル
モデル | 速度 | 品質 |
| ⚡⚡ | ⭐⭐⭐⭐⭐ (デフォルト) |
| ⚡⚡⚡ | ⭐⭐⭐ |
| ⚡⚡ | ⭐⭐⭐⭐ |
📦 要件
fastmcp>=2.3.0
httpx>=0.27.0
python-dotenv>=1.0.0🤝 コントリビューション
プルリクエストやIssueを歓迎します!特に以下に関心があります:
他のLLMプロバイダー(OpenAI、Anthropic)のサポート
新しいツール(セキュリティ監査、依存関係チェック、複雑性分析)
プロンプトの改善
📄 ライセンス
MIT — 自由にご利用ください。GitHubでスターをいただけると励みになります ⭐
🔗 リンク
Available Tools
7 toolsanalyze_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
Scored across 7 tools
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.
All tool names follow a consistent verb_noun pattern using snake_case (e.g., analyze_code, generate_tests). No inconsistencies in style.
7 tools is a well-scoped set for code analysis and sanitization tasks, covering the core operations without being overwhelming or too sparse.
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
Related MCP Connectors
AI code governance and code review for Claude Code, Copilot and Cursor. Checks rules and security.
AI-powered codebase analysis — call graphs, security, dead code, complexity. 150+ tools.
Checks AI-written code for leaked keys and made-up packages, on your machine. Never uploads code.
Scores your code across 12 areas, with findings, fix prompts, and re-assessment in your AI agent
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceA server that enables interaction with PostgreSQL, MySQL, MariaDB, or SQLite databases through Claude Desktop using natural language queries.1-
- AlicenseAqualityDmaintenanceAn MCP server that provides code review functionality using OpenAI, Google, and Anthropic models, serving as a "second opinion" tool that works with any MCP client.134MIT
- AlicenseAqualityDmaintenanceEnables 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.4MIT
- AlicenseAqualityDmaintenanceAI-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.441Business Source 1.1