Guardx Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Guardx Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
<div align="center">
A keyless, defensive (blue-team) code-security auditor for the [Model Context Protocol](https://modelcontextprotocol.io). Let your AI assistant scan codebases for secrets, audit dependencies for known CVEs, and check passwords against breach data — all from natural language.
</div>
⚠️ Defensive use only. Every tool is read-only, privacy-preserving, and needs no API keys. Use it only on code and credentials you own or are authorized to assess.
Unlike offensive recon tools that probe live websites, this server inspects your own code and credentials — making it the blue-team companion to your red-team tooling.
requirements.txt (PyPI) and package.json (npm) against the free OSV.dev vulnerability database.<p align="center"> <img src="assets/scan_secrets.png" alt="scan_secrets output" width="800"> </p>
<p align="center"> <img src="assets/audit_dependencies.png" alt="audit_dependencies output" width="800"> </p>
<p align="center"> <img src="assets/check_pwned_password.png" alt="check_pwned_password output" width="800"> </p>
git clone https://github.com/harshzagade/guardx-mcp.git
cd guardx-mcp
# (recommended) create a virtual environment
python -m venv .venv
# Windows:
.venv\Scripts\activate
# macOS / Linux:
source .venv/bin/activate
pip install -r requirements.txtRequirements: Python 3.10+ and the mcp + httpx packages (installed via requirements.txt).
GuardX runs locally over stdio, so any MCP-capable client can launch it. In every example below, replace /absolute/path/to/guardx-mcp/server.py with the real path on your machine. If you used a virtual environment, point command at that env's Python (e.g. .venv/bin/python or .venv\Scripts\python.exe) instead of python.
💡 First, confirm the server starts on its own (it then waits for a client on stdin — pressCtrl+Cto exit): ``bash python server.py``
<details open> <summary><b>Claude Code</b> (CLI)</summary>
Register the server with one command:
claude mcp add guardx -- python /absolute/path/to/guardx-mcp/server.py--scope project to write it to a shared .mcp.json in your repo.claude mcp list, then use /mcp inside Claude Code.</details>
<details> <summary><b>Claude Desktop</b> (app)</summary>
Edit your claude_desktop_config.json:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.json{
"mcpServers": {
"guardx": {
"command": "python",
"args": ["/absolute/path/to/guardx-mcp/server.py"]
}
}
}Restart Claude Desktop; GuardX appears under the 🔌 tools menu.
</details>
<details> <summary><b>Gemini CLI</b> (& Gemini Code Assist)</summary>
Edit ~/.gemini/settings.json (global) or .gemini/settings.json (per-project). The Gemini Code Assist IDE extension reads the same file:
{
"mcpServers": {
"guardx": {
"command": "python",
"args": ["/absolute/path/to/guardx-mcp/server.py"]
}
}
}Then run gemini and use /mcp to confirm the server is connected.
</details>
<details> <summary><b>OpenAI Codex</b> (CLI & IDE extension)</summary>
Codex uses TOML and shares config between the CLI and the IDE extension. Either run:
codex mcp add guardx -- python /absolute/path/to/guardx-mcp/server.py…or hand-edit ~/.codex/config.toml ( note the underscore in mcp_servers):
[mcp_servers.guardx]
command = "python"
args = ["/absolute/path/to/guardx-mcp/server.py"]Codex only supports local stdio MCP servers — perfect for GuardX.
</details>
<details> <summary><b>Cursor</b> / <b>VS Code</b></summary>
Create .cursor/mcp.json in your project (or the global ~/.cursor/mcp.json):
{
"mcpServers": {
"guardx": {
"command": "python",
"args": ["/absolute/path/to/guardx-mcp/server.py"]
}
}
}VS Code (with MCP support) uses the same mcpServers shape in its settings.
</details>
Windows tip: in JSON, write paths with forward slashes (C:/Users/you/guardx-mcp/server.py) or escaped backslashes (C:\\Users\\you\\...).
Once connected, just ask your assistant in plain language:
| You say... | Tool used |
|---|---|
| "Scan `./my-project` for hardcoded secrets" | scan_secrets |
| "Audit `requirements.txt` for known vulnerabilities" | audit_dependencies |
| "Has the password `password123` been pwned?" | check_pwned_password |
check_pwned_password follows the k-anonymity model recommended by Have I Been Pwned:
➡️ Your password and its full hash never leave your machine.
| Tool | Signature | Description |
|---|---|---|
| Secret scanner | scan_secrets(path, max_findings=200) | Recursively scans a file or directory for hardcoded secrets. Skips binaries and common ignore dirs (.git, node_modules, …). Returns masked findings with file and line number. |
| Dependency auditor | audit_dependencies(path) | Parses a requirements.txt or package.json and checks each pinned dependency against OSV.dev. Returns CVE/GHSA ids and summaries. |
| Pwned-password check | check_pwned_password(password) | Checks a password against HIBP via k-anonymity. Reports breach count without transmitting the password. |
guardx-mcp/
├── server.py # MCP server + the three tools
├── requirements.txt # runtime dependencies (mcp, httpx)
├── assets/ # README screenshots
├── README.md
├── LICENSE # MIT
└── .gitignoreContributions are welcome! Ideas: more secret patterns, additional ecosystems (Go modules, Cargo, Maven), or an SBOM export. Please keep all contributions defensive in nature. Open an issue or a pull request.
Released under the MIT License.
<div align="center"> <sub>Built as a defensive blue-team companion. Scan responsibly. 🛡️</sub> </div>
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.