analyze_codeLABSCO SUMMARY
A reviewer that gives you a number and a diff, not an opinion.
The version comparison is the tool that changes a workflow: point it at before and after, and it tells you whether the change introduced a regression and whether it should be merged.
What it is
An MCP server that sends code to a Llama model hosted on Groq for review and returns structured findings — severity, line, title, description and a suggested fix — alongside a score from 0 to 100. It reviews snippets or whole files, compares versions, generates tests and builds reports.
What you get
- A strict review of a snippet: bugs, security issues, and a score from 0 to 100
- Findings as structured JSON with severity, line number, description and a fix
- Two versions compared, regressions detected, and a merge or request_changes recommendation
- A step-by-step explanation pitched at a junior, middle or senior audience
- Pytest, jest or go test generated — happy path, edge cases and security
- A whole file from disk analysed with parallel chunking
- An HTML report built from any analysis result
- Cache statistics, and the cache cleared
Requirements
A recent Python and a free Groq API key in GROQ_API_KEY, obtainable without a card. Code you submit is sent to the Groq API to be reviewed.
Setup effort
One command plus a key — uvx mcp-code-sanitizer, then supply credentials
USE CASES
01
Getting a security read on code an agent just wrote
Review the snippet and get back the issues by severity and line, each with a concrete fix rather than a warning.
02
Checking a refactor did not break anything
Compare the two versions, see the regressions named, and take the merge or request_changes call.
03
Covering a file you inherited with tests
Analyse the file end to end, then generate a suite that includes the edge and security cases, not only the happy path.
04
Explaining a gnarly function to someone new
Get the walkthrough written for the level of the person who has to maintain it.
05
Handing findings to someone who will not read JSON
Turn any analysis result into an HTML report you can send on.
06
Keeping repeated reviews cheap
Check what the cache is holding, and clear it when the code has moved on.
7 tools
Listed in project docs. Your client may show a different list.
compare_codeexplain_codegenerate_testsanalyze_filegenerate_reportcache_infoBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
- uvx on PATH
- GROQ_API_KEY in your environment
Where it runs
All 4 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
uvx mcp-code-sanitizerMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add code-sanitizer -e GROQ_API_KEY=<YOUR_GROQ_API_KEY> -- uvx mcp-code-sanitizerClaude Desktop, Cursor
JSON
{
"mcpServers": {
"code-sanitizer": {
"command": "uvx",
"args": [
"mcp-code-sanitizer"
],
"env": {
"GROQ_API_KEY": "<YOUR_GROQ_API_KEY>"
}
}
}
}VS Code
VS CODE · JSON
{
"servers": {
"code-sanitizer": {
"command": "uvx",
"args": [
"mcp-code-sanitizer"
],
"env": {
"GROQ_API_KEY": "<YOUR_GROQ_API_KEY>"
}
}
}
}
