Security MCP for vibe coding. 313 rules, 25 tools for AI-generated code.
Security MCP for vibe coding. 313 rules, 25 tools for AI-generated code. The guardvibe mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.
Works with Claude Code, Cursor, Gemini CLI, Codex, VS Code (Copilot), Windsurf, and any MCP-compatible coding agent.
Installation goes through your MCP client rather than a global install: point it at guardvibe on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Everything the assistant can do here goes through one of these:
check_code — Analyze a code snippet for security issuescheck_project — Scan multiple files with security scoring (A-F)scan_directory — Scan a project directory from diskscan_staged — Pre-commit scan of git-staged files — diff-aware (blocks only newly-staged lines; diff_aware:false for whole files)scan_dependencies — Check all dependencies for known CVEs (OSV) — annotates each vulnerable package with reachability (is it actually imported in your source?)scan_secrets — Detect leaked secrets, API keys, tokenscheck_dependencies — Check individual packages against OSVcheck_package_health — Typosquat detection, maintenance status, adoption metricscompliance_report — Map security findings to compliance controls (SOC2, PCI-DSS, HIPAA, GDPR, ISO27001, EU AI Act)export_sarif — SARIF v2.1.0 export for CI/CD integrationget_security_docs — Security best practices and guidesfix_code — Auto-fix suggestions with concrete patches for AI agentsYou will need one environment variable: ANTHROPIC_BASE_URL. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Guardvibe's toolset — check_code, check_project, scan_directory and 11 more — is a fair guide to whether it matches your workflow. It is maintained by goklab; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| check_code | Analyze a code snippet for security issues |
| check_project | Scan multiple files with security scoring (A-F) |
| scan_directory | Scan a project directory from disk |
| scan_staged | Pre-commit scan of git-staged files — **diff-aware** (blocks only newly-staged lines; diff_aware:false for whole files) |
| scan_dependencies | Check all dependencies for known CVEs (OSV) — annotates each vulnerable package with **reachability** (is it actually imported in your source?) |
| scan_secrets | Detect leaked secrets, API keys, tokens |
| check_dependencies | Check individual packages against OSV |
| check_package_health | Typosquat detection, maintenance status, adoption metrics |
| compliance_report | Map security findings to compliance controls (SOC2, PCI-DSS, HIPAA, GDPR, ISO27001, EU AI Act) |
| export_sarif | SARIF v2.1.0 export for CI/CD integration |
| get_security_docs | Security best practices and guides |
| fix_code | **Auto-fix suggestions** with concrete patches for AI agents |
| secure_this | **Close the loop** — scan, apply only the fixes that verifiably land (each re-scanned, rolled back on regression), return the verified code + a definition-of-done gate |
| audit_config | Audit project configuration files for cross-file security misconfigurations |
{
"mcpServers": {
"guardvibe": {
"command": "npx",
"args": ["-y", "guardvibe"],
"env": {
"ANTHROPIC_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ANTHROPIC_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.