MCP Server Auditor
概览
作者提供的说明(英文原文)
Scans MCP server tool definitions for excessive agency, injection sinks, hardcoded secrets
PopNx MCP 的三大支柱
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
- 用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
- 我们的基础检查i1 项中通过 0 项依据公开信息检查;尚未扫描代码
- 使用情况i起步阶段↓ 438/周 · ★ –
它能帮你做什么
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
- 连接方式: 在你的电脑上运行
- 传输方式: stdio
- 分类: 网络安全
安装
选择你使用的 AI 应用,然后复制设置。
安装之前
- 基础检查:1 项中通过 0 项
- 在你的电脑上运行,拥有你的用户账户的权限(文件、网络、应用)。
- 注册中心没有列出需要填写的密钥。
你需要
- npm已安装 Node.js(用于 npx 命令)
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"auditor": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-server-auditor"
]
}
}
}在终端中运行这条命令
claude mcp add auditor -- npx -y @guardbee/mcp-server-auditor或者自己复制设置
粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"auditor": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-server-auditor"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
或者自己复制设置
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"auditor": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-server-auditor"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它能做什么
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
基础检查i
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日
- ! 注意
作者与仓库一致
发布者(4hmetuyar)不是仓库所有者(GuardBee);可能是其他人代为上架的
- … 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
- … 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
- – 不适用
端点有响应
它在你的电脑上运行,没有互联网端点
- – 不适用
使用 OAuth 登录
在你的电脑上运行,改用本地设置
- … 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与“网络安全”中的其他服务器比较i
- 星标数多于此分类中其他 1001 个服务器的 0%
- 发布到注册中心的时间比此分类中其他 1001 个服务器的 52% 更新
- 基础检查结果等于或优于此分类中其他 1001 个服务器的 18%
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
常见问题
MCP Server Auditor 安全吗?
它在 1 项适用的基础检查中通过了 0 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
它需要哪些密钥或代码?
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在我的电脑上运行还是在云端?
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
它还在维护吗?
GitHub 仓库最后更新于–,最新版本(0.1.5)于40天前进入注册中心。
哪些应用可以使用它?
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js。
有什么可以替代它?
同一分类中有:Zeqqat, EchelonGraph CVE & Exposure, KillerSkills
替代选择
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
EchelonGraph CVE & Exposure
CVE, KEV, EPSS, SBOM and advisory lookups; per-CVE exposure from Shodan data (© Shodan). Keyless.
KillerSkills
Security verdicts for agent skills and MCP servers, from sandbox runs, before you install them.
作者的 README
打开 README
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
@guardbee/mcp-server-auditor
🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch
An MCP (Model Context Protocol) server that scans other MCP servers' tool definitions for insecure patterns.
While ai-code-scanner looks at general LLM/AI integration code, this package specifically looks at an MCP server itself: how privileged a tool defined via server.tool(...) is, how loose its parameters are, which dangerous sinks (shell/filesystem/HTTP/SQL) its handler passes tool input into directly. The MCP ecosystem is growing fast, but there's no common tool yet for auditing these servers' security.
Telemetry is off by default. With
GUARDBEE_TELEMETRY=1it sends the server, tool, success, duration and short parameter values such as a file path; longer strings and fields likecontent,tokenorpasswordare replaced with a placeholder. See@guardbee/mcp-telemetry.
Claude ──► mcp-server-auditor ──► An MCP server's source code
│ ├─ Excessive agency (execSync(input.command), a tool named "run_shell") ├─ Unsafe input (fetch(input.url) → SSRF, SQL string interpolation) ├─ Loose schema (a parameter typed z.any()/z.unknown()) ├─ Secrets exposure (a hardcoded API key in a schema default, the entire process.env) └─ Network exposure (wildcard CORS)
Features
- 10 patterns, 5 categories — excessive-agency, unsafe-input, loose-schema, secrets-exposure, network-exposure
- Python and Go servers: tool input followed from the tool definition (FastMCP parameters, low-level
arguments, go-sdk typed args, mcp-gorequest.RequireString(...)) through plain assignments into shell, file write/delete, HTTP and SQL calls - Every finding includes why it's risky and what to do about it (
recommendation) — not just "found it" - SARIF 2.1.0 output — CI/CD integration (GitHub Code Scanning, etc.)
- Config file support via
guardbee.yml - A positive and a negative (false-positive) test for every pattern, with vulnerable and clean Python and Go fixtures
Quick Start
Claude Desktop / MCP Client
{
"mcpServers": { "guardbee-mcp-server-auditor": { "command": "npx", "args": ["-y", "@guardbee/mcp-server-auditor"] } } }
CLI (CI/CD)
npx @guardbee/mcp-server-auditor scan ./src --fail-on=high --format=sarif > results.sarif
MCP Tools
| Tool | Description |
|---|---|
scan_text | Scans a given text/code snippet |
scan_file | Scans a single file |
scan_directory | Recursively scans a directory (node_modules, .git, dist skipped automatically) |
list_patterns | Lists all supported patterns by category |
Detected Patterns
| Category | Pattern | Severity | OWASP | What it means |
|---|---|---|---|---|
| excessive-agency | shell_exec_from_tool_input | critical | MCP05:2025 | A tool handler passes tool input directly into a shell call like execSync/spawn |
| excessive-agency | eval_of_tool_input | critical | MCP05:2025 | Tool input is executed as code via eval()/new Function() |
| excessive-agency | unrestricted_shell_tool_name | high | MCP05:2025 | A tool name (run_shell, execute_sql, etc.) implies shell/SQL execution directly |
| unsafe-input | fs_write_from_raw_tool_input | high | A path from tool input flows into a file write/delete call with no validation (path traversal) | |
| unsafe-input | ssrf_fetch_from_tool_input | high | A URL from tool input flows directly into fetch/axios with no allowlist (SSRF) | |
| unsafe-input | sql_injection_via_tool_input | critical | MCP05:2025 | Tool input is interpolated into a SQL string via a template literal |
| loose-schema | overly_permissive_tool_schema | medium | A tool parameter is typed z.any()/z.unknown() — accepts anything | |
| secrets-exposure | hardcoded_secret_in_tool_schema | critical | A credential-shaped schema field's default value is a hardcoded literal | |
| secrets-exposure | full_env_exposed_to_tool_caller | critical | The entire process.env is spread/stringified/returned (not one named variable) | |
| network-exposure | permissive_cors_on_server | medium | Wildcard CORS (Access-Control-Allow-Origin: *) or cors() with no options |
Python and Go
Python (.py) and Go (.go) files also get a tool-input flow check. The tool's input names come from its definition, are followed through plain assignments in the handler (command = f"du {directory}"), and a finding is reported when one reaches a sink call:
| Pattern | Severity | Sinks |
|---|---|---|
python_shell_from_tool_input | critical | subprocess.*, os.system, os.popen, asyncio.create_subprocess_* |
python_eval_of_tool_input | critical | eval, exec |
python_fs_write_from_tool_input | high | open(..., "w"/"a"/"x"), os.remove/rename/…, shutil.rmtree/move, Path(...).write_text/unlink |
python_ssrf_from_tool_input | high | requests.*, httpx.*, client.get(...), urlopen (URL argument) |
python_sql_injection_via_tool_input | critical | cursor.execute(f"...{x}..."), % / .format / + |
go_shell_from_tool_input | critical (sh -c), high (argument list) | exec.Command, exec.CommandContext |
go_fs_write_from_tool_input | high | os.WriteFile, os.Remove, os.RemoveAll, os.Rename, os.Create, os.OpenFile for writing |
go_ssrf_from_tool_input | high | http.Get/Post/NewRequest…, client.Get |
go_sql_injection_via_tool_input | critical | db.Query…/Exec… with fmt.Sprintf or + |
File findings are skipped when the handler checks the path against a base directory (is_relative_to, commonpath, .parents, filepath.IsLocal, filepath.Rel, strings.HasPrefix), and HTTP findings when it checks a host allowlist. Tools named run_shell, execute_sql etc. are reported for both languages. Rust, Java, Kotlin, C# and other languages get the language-neutral patterns only.
These are heuristic findings — a static text-pattern scan, not a full AST/type analysis. Designed for a low false-positive rate, but every finding should still be reviewed manually.
Configuration (guardbee.yml)
mcp-server-auditor:
fail-on: high # any | critical | high | medium | low | none max-files: 5000 exclude:
- ".test.ts"
- "fixtures/"
Development
npm run build
npm test
License
MIT — GuardBee
Feedback
Questions, ideas, or a false positive? Start a thread in GitHub Discussions or open an issue. If GuardBee is useful to you, a ⭐ on the repository helps others find it.