GSC Scanner — Claude Code MCP server: what it does, how to install
GSC Scanner is an MCP server for AI coding assistants: it scans code, secrets, and IaC, creates exploit proofs in a sandbox, and validates fixes.
Apache-2.0 ★ 18 updated 2026-10-27
claude mcp add --env GSC_ALLOWED_ROOTS=<GSC_ALLOWED_ROOTS> --transport stdio gsc-scanner -- docker run -i --rm -e GSC_ALLOWED_ROOTS ghcr.io/poliakarmai/gsc-scanner:v1What GSC Scanner does
GSC Scanner exposes ten MCP tools to coding assistants, such as scan_repo, scan_diff, get_poc, and verify_fix. Its rule set includes 67 detectors covering static application security testing, software composition analysis, exposed credentials, and IaC configurations.
Rather than stopping at plain rule matches, the tool generates runnable proofs-of-concept inside a sandbox. Once an agent drafts a patch, it can run verify_fix to confirm that the exploit no longer succeeds. The server acts strictly as a read-only inspector toward your repository files, leaving edits and pull requests to the developer.
The core engine runs inside the ghcr.io/poliakarmai/gsc-scanner:v1 Docker container, meaning a working Docker installation and the GSC_ALLOWED_ROOTS variable are required. You can attach an OpenAI-compatible API key or local Ollama endpoint for secondary checks, but the scanner runs in pure regex mode if no key is provided.
What it helps with
- scan codebases for leaked credentials and static code flaws
- generate safe proofs-of-concept to verify detected security issues
- confirm that code patches actually neutralize the exploit via
verify_fix - inspect uncommitted git diffs for insecure infrastructure definitions
Example prompts for the agent
- Run
scan_repoon this project and report any critical issues - Check the current git diff with
scan_diffbefore creating a pull request - Generate an exploit proof with
get_pocand confirm the patch withverify_fix
How to install GSC Scanner
Platform CLI
claude mcp add --env GSC_ALLOWED_ROOTS=<GSC_ALLOWED_ROOTS> --transport stdio gsc-scanner -- docker run -i --rm -e GSC_ALLOWED_ROOTS ghcr.io/poliakarmai/gsc-scanner:v1Replace <…> with your own values
Platform CLI
codex mcp add gsc-scanner --env GSC_ALLOWED_ROOTS=<GSC_ALLOWED_ROOTS> -- docker run -i --rm -e GSC_ALLOWED_ROOTS ghcr.io/poliakarmai/gsc-scanner:v1Replace <…> with your own values
Config file
{
"mcpServers": {
"gsc-scanner": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GSC_ALLOWED_ROOTS",
"ghcr.io/poliakarmai/gsc-scanner:v1"
],
"env": {
"GSC_ALLOWED_ROOTS": "<GSC_ALLOWED_ROOTS>"
}
}
}
}Replace <…> with your own values
Config file
{
"servers": {
"gsc-scanner": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"-e",
"GSC_ALLOWED_ROOTS",
"ghcr.io/poliakarmai/gsc-scanner:v1"
],
"env": {
"GSC_ALLOWED_ROOTS": "<GSC_ALLOWED_ROOTS>"
}
}
}
}Replace <…> with your own values
Platform CLI
gemini mcp add -e GSC_ALLOWED_ROOTS=<GSC_ALLOWED_ROOTS> gsc-scanner docker run -i --rm -e GSC_ALLOWED_ROOTS ghcr.io/poliakarmai/gsc-scanner:v1Replace <…> with your own values
Step by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about GSC Scanner
How do I install GSC Scanner in Claude Code?
Run `claude mcp add --env GSC_ALLOWED_ROOTS=<GSC_ALLOWED_ROOTS> --transport stdio gsc-scanner -- docker run -i --rm -e GSC_ALLOWED_ROOTS ghcr.io/poliakarmai/gsc-scanner:v1`.
What does GSC Scanner do?
It gives AI assistants 10 MCP tools to audit repositories for security flaws, build proof-of-concept tests, and verify whether proposed fixes work in an isolated environment.
Does GSC Scanner require an LLM API key?
No, an external API key is optional. Without one, the scanner operates in regex-only mode, while custom API keys or local Ollama endpoints are used for extra LLM validation.