MCP Code Review Server
A code review tool that generates detailed HTML review documents by comparing branches or commits, with author filtering and intelligent analysis.
Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.
How we verified
Verified is a snapshot. Live keeps it current, and builds your track record.
⚡ Connect GitHub → continuous verification on every pushwhy connect →Who stands behind it
xlian-fe
Source: Glama
Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →
Install from
The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.
These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.
get_changed_files获取变更文件的路径列表。支持两种模式： 模式一：分支对比模式（需要 target_branch） 对比开发分支与目标分支之间的代码差异。 模式二：Commit Hash 模式（需要 from_commit，不需要 target_branch） 指定一个起始 commit hash，获取该 commit 之后到开发分支的所有变更。适用于不想指定目标分支的场景。 使用流程： 1. 调用此工具获取变更文件路径列表 2. 根据每个文件的完整路径名称，生成简短的中文功能描述（10-20字） 3. 将描述通过 file_descriptions 参数传给 generate_code_review 工…
generate_code_review生成代码Review报告。支持两种模式： 模式一：分支对比模式（需要 target_branch） 对比开发分支与目标分支的代码差异。 模式二：Commit Hash 模式（需要 from_commit，不需要 target_branch） 指定一个起始 commit hash，获取该 commit 之后到开发分支的所有变更并生成报告。 使用场景： - 迭代结束后，需要在小组内分享代码改动 - 代码评审会议前准备Review材料 - 记录本次迭代的技术细节 使用方式： 直接调用此工具即可。如果不传 file_descriptions，系统会返回变更文件列表，你需要根据每个文件的完整路径…
list_branch_authors列出变更范围内所有提交的作者信息，帮助用户确认自己的Git用户名。支持两种模式： 模式一：分支对比模式（需要 target_branch） 模式二：Commit Hash 模式（需要 from_commit，不需要 target_branch） 使用场景： - 不确定自己的Git用户名时，先查看提交作者列表 - 了解本次迭代有哪些人参与了代码提交
Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.
Model Context Protocol (MCP) TypeScript SDK does not enable DNS rebinding protection by default
Tool annotations
No tools have read-only/destructive annotations
Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.
All four hints declared on every tool
6/6 tools missing one or more hints — get_changed_files (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); generate_code_review (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_branch_authors (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +3 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.
For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.
License file
No license file
Add a LICENSE file (MIT, Apache-2.0, etc.).
Tests exist
No test files found
Add tests that exercise each declared tool.
Production dependencies are patched
0 critical, 1 high severity in production deps — @modelcontextprotocol/sdk@0.5.0 (high)
Run npm audit fix, or upgrade the affected packages to a non-vulnerable version.
Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.
[](https://m8ven.ai/mcp/xlian-fe/mcp-xl-code-review)?variant=verified from the URL.Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.
https://m8ven.ai/api/mcp/tool-check