Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Unified OWASP MCP Top 10 scan — path or live tools/list, A–F grade, SARIF
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"owasp-scan": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-owasp-scan"
]
}
}
}Run this in your terminal
claude mcp add owasp-scan -- npx -y @guardbee/mcp-owasp-scanPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"owasp-scan": {
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-owasp-scan"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"owasp-scan": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@guardbee/mcp-owasp-scan"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account GuardBee, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.5.2) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Python MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Local-only Python MCP server for the Files.com API.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
🇬🇧 English | 🇹🇷 Türkçe | 🇨🇳 中文 | 🇯🇵 日本語 | 🇰🇷 한국어 | 🇧🇷 Português | 🇪🇸 Español | 🇩🇪 Deutsch
One CLI and MCP server for a unified [OWASP MCP Top 10](https://owasp.org/www-project-mcp-top-10/) check. It runs seven GuardBee auditors over a codebase in one pass, or grades a live MCP server's tool list, and reports every finding under its OWASP id with an A–F grade. Output as text, JSON or SARIF for GitHub code scanning.
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.
# Static scan of a repository, fail CI on high or critical findings
npx @guardbee/mcp-owasp-scan scan ./src --format=sarif --fail-on=high > owasp.sarif
npx @guardbee/mcp-owasp-scan live --url=https://mcp.example.com/mcp npx @guardbee/mcp-owasp-scan live --stdio=npx --arg=-y --arg=@modelcontextprotocol/server-filesystem --arg=.
npx @guardbee/mcp-owasp-scan catalog ./tools.json --format=json
As an MCP server (Claude Desktop, Cursor, VS Code):
{
"mcpServers": { "guardbee-owasp-scan": { "command": "npx", "args": ["-y", "@guardbee/mcp-owasp-scan"] } } }
| Mode | Input | What runs |
|---|---|---|
scan | A file or directory | secret-scanner, mcp-server-auditor, oauth-auditor, audit-gap-auditor, context-oversharing-auditor, toxic-flow-auditor, tool-poisoning-scanner |
live | --url= or --stdio= with --arg=… | Connects, calls tools/list, then toxic-flow-auditor and tool-poisoning-scanner |
catalog | A tools/list dump ({ "tools": [...] } or a bare array) | Same checks as live, offline |
scan reads TypeScript/JavaScript, Python (FastMCP, official SDK, low-level server) and Go (official go-sdk, mark3labs/mcp-go) MCP servers in full: tool definitions, handler sinks and OAuth rules. Other languages (Rust, Java, Kotlin, C#, Ruby, PHP, Swift) get the language-neutral rules only (secrets, URLs, config). The report's coverage lists every source file with its language, that depth (full or patterns) and the number of tool definitions found, plus a per-language summary (languages: in text output), so a file the scan could not read deeply is visible rather than silently passing.
--discover-shadow adds an MCP09 check to scan: it inventories the MCP servers configured on this machine (Cursor, Claude Desktop, Windsurf, VS Code) through mcp-config-auditor, and --allowlist= marks the approved ones.
| ID | Risk | Covered by |
|---|---|---|
| MCP01 | Token / credential exposure | secret-scanner, mcp-server-auditor |
| MCP02 | Privilege / excessive agency | mcp-server-auditor |
| MCP03 | Tool poisoning / rug pull surface | tool-poisoning-scanner (scan, live, catalog) |
| MCP04 | Supply chain | Not in this meta-scan: use mcp-dependency-auditor and mcp-slopsquat-scanner, which need the network |
| MCP05 | Command / code injection via tools | mcp-server-auditor |
| MCP06 | Prompt / context injection | Not in this meta-scan: use mcp-prompt-injection-scanner on the content an agent reads |
| MCP07 | Auth / OAuth misconfiguration | oauth-auditor |
| MCP08 | Lack of audit and telemetry | audit-gap-auditor |
| MCP09 | Shadow MCP servers | mcp-config-auditor (--discover-shadow) |
| MCP10 | Toxic flows / context oversharing | toxic-flow-auditor, context-oversharing-auditor (scan, live, catalog) |
| Grade | When |
|---|---|
| F | A lethal trifecta: one agent can read untrusted content, reach sensitive data and send data out |
| D | Any critical finding |
| C | Any high finding |
| B | Only medium or low findings |
| A | No findings |
| Option | Default | Meaning | ||||
|---|---|---|---|---|---|---|
| `--format=text\ | json\ | sarif` | text | Report format. SARIF uploads to GitHub code scanning | ||
| `--fail-on=any\ | critical\ | high\ | medium\ | none` | any | Exit 1 when a finding at or above this severity exists |
--max-files= | 5000 | Stop a path scan after this many files | ||||
--discover-shadow | off | Add the MCP09 host inventory to scan | ||||
--allowlist= | – | Approved servers for --discover-shadow |
Exit codes: 0 clean (or below --fail-on), 1 findings at or above --fail-on, 2 usage error.
| Tool | What it does |
|---|---|
owasp_scan_path | The scan mode over a path (path, maxFiles, discoverShadow, allowlistPath) |
owasp_scan_live | The live mode (url, or command with args) |
owasp_scan_catalog | The catalog mode on a JSON string |
list_owasp_coverage | The coverage table above |
- run: npx -y @guardbee/mcp-owasp-scan scan . --format=sarif --fail-on=high > owasp.sarif
Each auditor is also its own package with more options: mcp-secret-scanner, mcp-server-auditor, mcp-oauth-auditor, mcp-audit-gap-auditor, mcp-context-oversharing-auditor, mcp-toxic-flow-auditor, mcp-tool-poisoning-scanner, mcp-config-auditor. To enforce these rules at runtime instead of finding them in code, put mcp-security-proxy in front of your MCP servers.
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.