Skip to main content

aevrin

PyPI version Python versions License Downloads Publish status

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

python3 -m pip install --upgrade aevrin

The same CLI is also available through npm:

npm install --global aevrin

Requires Docker using Linux containers (each scanner runs in its own disposable container). On Docker Desktop, assign at least 4 GB of memory and permit bind mounts from the system temporary directory. Scanner images are version-pinned and pulled automatically when missing.

Usage

aevrin scan mcp "npx -y @playwright/mcp"   # scan a server by its launch command
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); another public https:// URL is treated as a live MCP server (runtime description checks only); anything that exists on disk is scanned as a local path (full pipeline, no cloning). Private, loopback, metadata, credential-bearing, and plain-HTTP live targets are rejected. Aevrin never executes submitted stdio MCP commands.

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).
--remote Scan a local folder on Aevrin's servers instead of this machine, so no Docker or scanner binary is needed locally. Local paths only.

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 Couldn't start, authentication, quota, API, target, or flag error.
3 Incomplete: a required scanner category did not execute. This is never treated as a clean pass.

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 ┃ Rule     ┃ Title                   ┃ Affected tools                 ┃
┡━━━━━━━━━━╇━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ CRITICAL │ AS-006   │ Arbitrary Code Execution│ browser_run_code_unsafe        │
│ LOW      │ AS-011   │ Missing Rate Limits x5  │ browser_navigate, browser_ta…  │
└──────────┴──────────┴─────────────────────────┴────────────────────────────────┘

Other commands

aevrin login / logout           # browser device-code login, credentials in ~/.aevrin
aevrin agent scan               # what the AI coding agents on this machine may do
aevrin agent scan --json        # versioned snapshot; never contains a credential value
aevrin hook setup               # log in the Claude Code hook, print its settings snippet
aevrin hook allow <target>      # short-lived override after a hook block
aevrin findings triage <id> <status> [--reason ...]

agent scan reads configuration only: no agent is started and nothing from a config file is executed. Nothing leaves the machine without --upload. Full reference: https://mcp.aevrin.net/docs/cli.

Development

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

Metadata

Release files for aevrin 0.6.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for aevrin 0.6.0
File Size Uploaded Provenance
aevrin-0.6.0.tar.gz 143.4 kB With provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for aevrin 0.6.0
File Interpreter ABI Platform
aevrin-0.6.0-py3-none-any.whl Python 3 none any Details

Total release size: 188.4 kB

Release files / aevrin-0.6.0.tar.gz

Download URL aevrin-0.6.0.tar.gz
Size 143.4 kB
Tags Source
SHA-256 checksum
How to use checksums
2399e4cf4dec78c12715720a3a15fea0a83b5f55af7c8ab884ec49cc46c26fed
BLAKE2b-256 checksum
How to use checksums
e621b91ff83c4465bdd07b2fe9871a4a7d247e04bea1e72e2e35dddc7d6148fe
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.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 Sep 29, 2026.

Transparency log

Release files / aevrin-0.6.0-py3-none-any.whl

Download URL aevrin-0.6.0-py3-none-any.whl
Size 45.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
a32fc7affc0015e2b3fb30ecd44a293db5a06216e6eaaf26283c944ef3e47344
BLAKE2b-256 checksum
How to use checksums
3465fc3644960f121b7e63f6aa19c7c81e2bc793adae880a281eb3c8235a469d
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.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 Sep 29, 2026.

Transparency log

Security for aevrin 0.6.0

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.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for aevrin-0.6.0.tar.gz

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 Sep 29, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page