Code Audit MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_scanC | 执行完整的代码安全审计扫描，包括AST解析、漏洞检测和报告生成。支持Python、JavaScript、TypeScript、Go、Java、PHP等多种语言。 |
| audit_quick_scanA | 快速扫描，仅检测critical和high级别的漏洞。适合CI/CD流程中的快速检查。 |
| audit_analyze_fileA | 对单个文件进行详细的代码安全分析，包括AST解析、函数提取和漏洞检测。 |
| build_call_graphB | 构建代码的函数调用关系图，用于分析代码结构和数据流。 |
| analyze_data_flowB | 分析代码中的数据流，追踪用户输入到敏感函数的数据传播路径。 |
| check_dependenciesC | 检查项目依赖的安全风险，包括已知漏洞的依赖版本检测。 |
| get_exploitation_guideB | 获取漏洞的详细复现操作指南，包括攻击载荷、PoC代码和修复建议。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Tools have distinct purposes overall, but some overlap exists between audit_quick_scan and audit_scan (quick subset of full scan) and between analyze_data_flow and build_call_graph (both related to code analysis). Descriptions help differentiate, but agents might occasionally misselect.
Naming is mixed: 'audit_' prefix is used inconsistently (audit_analyze_file combines verbs), and verbs vary (analyze, audit, build, check, get). While readable, there is no strict verb_noun pattern throughout.
With 7 tools, the server is well-scoped for a code audit domain. Each tool covers a necessary function without bloat, and the count is appropriate for the complexity of the domain.
The tool set covers major aspects of code auditing: scanning (full/quick/single file), data flow analysis, call graph, dependency checking, and exploitation guides. Minor gaps like a dedicated report listing are absent but not critical for typical workflows.