Enables GitHub Copilot to run local security scans on generated code, including SAST, secrets, SCA/SBOM, containers, and configuration checks, with tools to validate files/buffers, list findings, and fix findings.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@gadriel Run a Gadriel security scan on this repo and summarize the findings."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Security scanning for the code Copilot writes: SAST, secrets, dependencies (SCA/SBOM), containers and configuration, including AI-specific risks like prompt injection and the OWASP LLM Top 10 — 3,000+ rules, scanned on your machine. Gadriel plugs into Copilot as an MCP server plus repository instructions, prompts, and reviewer agents.
Part of the Gadriel AI Security Harness, alongside VS Code, Claude Code, Codex, and Cursor.
Easiest — the VS Code extension. Install
Gadriel AI Security Harness
from the Marketplace. It registers the gadriel MCP server for Copilot
automatically and adds a Gadriel: Scan Repository command — no config to
edit.
Or add the MCP server yourself. The server is published to the
GitHub MCP Registry as
io.github.Gadriel-ai/gadriel, so it shows up in VS Code's MCP: Browse
Servers and Copilot Chat's @mcp search — add it in a click. To wire it
per-repo instead, drop this .vscode/mcp.json into your project (needs Node for
npx, or npm install -g gadriel):
{ "servers": { "gadriel": { "type": "stdio", "command": "npx", "args": ["-y", "gadriel@1.4.1", "code", "mcp"] } } }Add the Copilot guidance (optional). Copy the .github/ directory into your
repo so Copilot knows how to use Gadriel:
Path | What |
| repo-wide guidance, auto-applied |
| 17 topic rules, scoped by |
|
|
| 8 reviewer agents |
Related MCP server: vibecheck
In Copilot Chat (agent mode), just ask: "Run a Gadriel security scan on this
repo and summarize the findings," or invoke a prompt like /gadriel-scan. The
gadriel MCP tools — validate_file, findings_for_path, fix_finding,
validate_buffer, and more — are available to Copilot directly.
No automatic edit guardrail here. Copilot/VS Code has no edit-time hook (Cursor and Codex do), so scanning runs on request via the MCP tools and prompts rather than blocking each edit.
Enterprise: Copilot Business/Enterprise can allowlist the gadriel MCP
server through managed MCP policy.
Privacy: code is scanned locally and never uploaded. First run registers
an anonymous device credential with app.gadriel.ai (a random device id — no
hostname, username, or keys); set GADRIEL_NO_ANONYMOUS_AUTH=1 to skip. See
the privacy policy.
The registry listing is (re)published by .github/workflows/publish-mcp.yml
(GitHub OIDC — an org namespace can only be published from CI in a Gadriel-ai
repo). After a new gadriel npm release, bump server.json and the
.vscode/mcp.json pin, then re-run that workflow.
This repository is Apache-2.0. The gadriel scanner it runs is
proprietary, under the Gadriel terms.
This server cannot be deployed
Zero-config MCP security scanner for AI-generated apps. 25K+ vulnerability patterns.
Threat modeling, code/cloud/pipeline scanning, shadow-AI discovery, compliance checks and fixes.
Zero-install security baseline for AI coding agents — OWASP/CWE-cited rules over MCP.
Remote MCP for Copilot CLI switch gate MCP, structured receipts, audit logs, and reviewer-ready evid