Code ReviewSAFE
A MCP server for code reviews
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
A custom MCP server that performs code reviews using Repomix and LLMs.
Features
- Flatten codebases using Repomix
- Analyze code with Large Language Models
- Get structured code reviews with specific issues and recommendations
- Support for multiple LLM providers (OpenAI, Anthropic, Gemini)
- Handles chunking for large codebases
Installation
# Clone the repository git clone https://github.com/yourusername/code-review-server.git cd code-review-server # Install dependencies npm install # Build the server npm run build
Configuration
Create a .env file in the root directory based on the .env.example template:
cp .env.example .env
Edit the .env file to set up your preferred LLM provider and API key:
# LLM Provider Configuration LLM_PROVIDER=OPEN_AI OPENAI_API_KEY=your_openai_api_key_here
Usage
As an MCP Server
The code review server implements the Model Context Protocol (MCP) and can be used with any MCP client:
# Start the server node build/index.js
The server exposes two main tools:
analyze_repo: Flattens a codebase using Repomixcode_review: Performs a code review using an LLM
When to Use MCP Tools
This server provides two distinct tools for different code analysis needs:
analyze_repo
Use this tool when you need to:
- Get a high-level overview of a codebase's structure and organization
- Flatten a repository into a textual representation for initial analysis
- Understand the directory structure and file contents without detailed review
- Prepare for a more in-depth code review
- Quickly scan a codebase to identify relevant files for further analysis
Example situations:
- "I want to understand the structure of this repository before reviewing it"
- "Show me what files and directories are in this codebase"
- "Give me a flattened view of the code to understand its organization"
code_review
Use this tool when you need to:
- P
8ac8bf655b5dOBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add code-review-server -- npx -y [email protected]
{
"mcpServers": {
"code-review-server": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (11)
10 read · 1 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
analyze_codebase_structure | read | |
analyze_repo | read | |
best_practices_review | read | Review code for adherence to best practices |
code_review | read | |
comprehensive_quality_review | read | |
comprehensive_review | read | Perform a comprehensive code review |
performance_review | read | Review code for performance issues |
repository_analysis | read | Analyze an entire repository using Repomix |
review_code | write | Create a code review for a specific file |
scan_repo | read | Scan a repository directory for code files |
security_review | read | Review code for security vulnerabilities |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (12)
bun.lockb
import { executeRepomix, RepomixOptions } from "../../src/repomix.js";dotenv, node-fetch, repomix, zod, @modelcontextprotocol/sdk, @types/node, bun-types, typescript
dotenv, node-fetch, repomix, zod, @modelcontextprotocol/sdk, @types/node, bun-types, typescript
load_dotenv() # load environment variables from .env
// Load environment variables
// Load environment variables
// Load environment variables
load_dotenv() # load environment variables from .env
curl -LsSf https://astral.sh/uv/install.sh | sh
curl -LsSf https://astral.sh/uv/install.sh | sh
Gates applied: no_behavioural_pass, no_license.
8ac8bf655b5dfull audit observations/trust-audit/mcp-server/crazyrabbitltc__code-review.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | 8ac8bf655b5d | SAFE | B | 89 | first audit |
Questions
What is the Code Review MCP server?
A MCP server for code reviews
What tools does Code Review expose?
11 in total: 10 read-only, 1 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Code Review safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Code Review need?
No credential environment variables were found in its source, so it appears to need none.
How does Code Review run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as code-review-server at 0.1.0.
How current is this page?
The grade is for one exact copy of the source (8ac8bf655b5d), read on 2026-10-08. The repository is watched and re-audited when it changes.