secscan-mcp
A portable MCP server for security scanning — works with any AI coding assistant that supports the Model Context Protocol: Cursor, VS Code, Claude Desktop, Windsurf, Zed, Continue, and more.
Scan codebases for hardcoded secrets, SAST issues, vulnerable dependencies, and IaC misconfigurations — one install, one normalized report format.
The built-in custom scanner works with no extra tools. Install optional CLIs for broader coverage (below).
Quick start
Requires Python 3.11+. If pip install secscan-mcp says "No matching distribution found", your default python3 is likely too old — use python3.11 -m pip install secscan-mcp or install Python 3.11+ first.
1. Install from PyPI:
pip install secscan-mcp
# or explicitly:
python3.11 -m pip install secscan-mcp
Or run without installing (requires uv):
uvx secscan-mcp
For MCP config with uvx, use "command": "uvx" and "args": ["secscan-mcp"] — see setup guide.
Install from source
git clone https://github.com/openjkai/secscan_mcp.git
cd secscan_mcp && pip install .
2. Add to your IDE — pick your client:
| IDE / client | Config file | Guide |
|---|---|---|
| Cursor | ~/.cursor/mcp.json |
setup → |
| VS Code | .vscode/mcp.json |
setup → |
| Claude Desktop | OS-specific (see guide) | setup → |
| Claude Code | ~/.claude/settings.json |
setup → |
| Windsurf | ~/.codeium/windsurf/mcp_config.json |
setup → |
| Others | — | Full setup guide |
Minimal config (works in Cursor, Claude Desktop, Windsurf):
{
"mcpServers": {
"secscan": {
"command": "uvx",
"args": ["secscan-mcp"]
}
}
}
If you installed with pip install secscan-mcp, you can use "command": "secscan-mcp" instead.
3. Verify — ask your agent: "Call list_available_scanners and scan_secrets on this project."
MCP tools
| Tool | Purpose |
|---|---|
list_available_scanners |
Which engines are installed on this machine |
scan_secrets |
Hardcoded credentials and secrets (optionally scan git commit history) |
scan_code |
SAST (semgrep, bandit) |
scan_dependencies |
Vulnerable packages (osv-scanner) |
scan_iac |
IaC misconfigurations (checkov) |
scan_all |
All available scanners, one unified report |
explain_finding |
Remediation hints for a rule_id |
Most scan tools accept path (directory to scan) and optional severity_threshold (critical, high, medium, low, info).
scan_secrets also accepts include_git_history (boolean). When true, scans past git commits for secrets removed from the working tree but still present in history — no extra tools required beyond git. scan_all accepts include_git_history too.
Suppressing false positives
Silence known-good findings without changing scanner behavior. Both mechanisms apply to every engine, and each report includes a suppressed count so nothing is hidden silently.
.secscanignore at the project root — gitignore-style path globs:
# ignore vendored code and test fixtures
vendor/
tests/fixtures/
*.min.js
Inline # nosecscan on the offending source line — suppress all rules there, or scope to specific rule IDs:
API_TOKEN = get_token() # real code, no marker
LEGACY_KEY = "AKIA..." # nosecscan
DEMO_JWT = "eyJ..." # nosecscan: hardcoded-jwt
Optional scanners
Install any of these to extend coverage. Missing CLIs are skipped — the server still runs.
| Engine | Category | Install (example) |
|---|---|---|
| gitleaks | secrets | brew install gitleaks |
| semgrep | SAST | pip install semgrep |
| bandit | SAST (Python) | pip install bandit |
| osv-scanner | dependencies | brew install osv-scanner |
| checkov | IaC | pip install checkov |
After installing, run list_available_scanners again to confirm.
Example prompts
- "Call
list_available_scannersand tell me what's installed." - "Run
scan_secretswith include_git_history on this repo — check if any secrets were ever committed." - "Run
scan_allwith severity_threshold high and summarize the findings." - "Explain the rule
internal-api-key." - "Add a
.secscanignorefor thetests/fixturesdirectory and re-run the scan."
Configuration
Environment variables (optional):
| Variable | Default | Description |
|---|---|---|
SECSCAN_DEFAULT_TIMEOUT_SECONDS |
300 |
Per-engine scan timeout |
SECSCAN_MAX_FINDINGS |
500 |
Max findings per report |
SECSCAN_GIT_MAX_COMMITS |
500 |
Max commits scanned in git history mode |
Pass via MCP config env block — see setup guide.
Development
make install-dev # editable install + dev tools
make check # lint + typecheck + test
See docs/CONTRIBUTING.md and PLAN.md.
License
MIT
Metadata
Release files for secscan-mcp 0.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| secscan_mcp-0.3.0.tar.gz | 28.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| secscan_mcp-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 58.0 kB
Release files / secscan_mcp-0.3.0.tar.gz
| Download URL | secscan_mcp-0.3.0.tar.gz |
|---|---|
| Size | 28.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f61e89dc02cc8171e405f3a8e8c8736536706e872b6fdc1190db2166d526ec64
|
|
BLAKE2b-256 checksum How to use checksums |
8e2e15d9f3409091cd776ced946994e3cd17bcec0d5d81dc20d9a89de05fdf7b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency logRelease files / secscan_mcp-0.3.0-py3-none-any.whl
| Download URL | secscan_mcp-0.3.0-py3-none-any.whl |
|---|---|
| Size | 29.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
36b05f8326f69edeb317e94d5c645ab4ceafbbf42662a455c15d9d4238623643
|
|
BLAKE2b-256 checksum How to use checksums |
5624bce414f6588e3dc22334cc9277e00a37ba59ce768db203f1062deed50527
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 27, 2026.
Transparency log