aevrin 0.1.4

Aevrin MCP Security Scanner CLI — scan a GitHub repo, local path, or live MCP server.

aevrin

Aevrin MCP Security Scanner CLI. Wraps the same open-source scanner binaries and normalization logic (aevrin-scanner-core) that the Aevrin backend uses, run locally against your own machine. Results save to your Aevrin dashboard automatically once you're logged in — pass --no-upload for a purely local, ephemeral scan.

Install

pip install aevrin

Requires Docker (each scanner runs in its own disposable container — see the main repo README for why).

Usage

aevrin scan ./my-mcp-server
aevrin scan github.com/owner/repo
aevrin scan https://my-live-server.example.com --json
aevrin scan ./my-mcp-server --fail-on high
aevrin scan ./my-mcp-server --no-upload   # skip saving to your dashboard (e.g. in CI)

Target type is auto-detected: a github.com URL scans the full pipeline (static analysis, secrets, dependencies, tool-description checks); any other http(s):// URL is treated as a live MCP server (manifest-level checks only); anything that exists on disk is scanned as a local path (full pipeline, no cloning).

Flags

Flag	Behavior
--json	Machine-readable JSON on stdout instead of a formatted table.
--no-upload	Skip saving the result to your Aevrin dashboard (on by default once logged in). Useful in CI, or for a purely local, ephemeral scan.
--fail-on <severity>	Minimum severity that causes a non-zero exit code. One of critical, high, medium, low, info. Defaults to high (both critical and high findings fail the build).

Exit codes

Code	Meaning
0	Clean — no findings at or above the --fail-on threshold.
1	Findings at or above the --fail-on threshold were found.
2	Misuse — bad arguments, a target that couldn't be resolved, or every scan stage failed to run. A dashboard-save failure does not set this — it's a warning on stderr, not a scan failure.

Results go to stdout; stage progress and diagnostics go to stderr — safe to pipe --json output without stage-progress noise mixed in.

Example output

[✓] static analysis
[✓] secrets
[✓] dependencies
[✓] tool description check
[✓] aggregating

Target: ./my-mcp-server
Score:  62/100  Significant risk — do not deploy as-is

┏━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┓
┃ Severity ┃ Title                ┃ OWASP category                      ┃ Tool    ┃
┡━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━┩
│ CRITICAL │ Hardcoded secret     │ MCP01: Token Mismanagement          │ trivy   │
│ HIGH     │ subprocess shell true│ MCP05: Command Injection, ...       │ semgrep │
└──────────┴──────────────────────┴──────────────────────────────────────┴─────────┘

Development

uv sync
uv run pytest tests -v
uv run ruff check .
uv run mypy src