shakerscan
The ShakerScan client: public posture checks plus the MCP adapter and Hunt CLI for a ShakerScan instance, without the engine. Use the public service with no account, or point the client at a local engine, VPS, or self-hosted Enterprise gateway and hand it to an agent or script.
pipx install shakerscan # or: uv tool install shakerscan
shakerscan check example.com # free public posture check, no engine/account
shakerscan mcp # public MCP when no instance is configured
shakerscan doctor --url https://scanner.example.com --token-file ./token
shakerscan mcp --url https://scanner.example.com --token-file ./token
shakerscan hunt --url https://scanner.example.com --token-file ./token list
shakerscan approve <request-id> # allow what a Hunt asks for, in your own terminal
shakerscan record https://app.example.com # browse in a recorded browser (needs shakerscan[record])
It installs the same shakerscan command name as the engine installer
(curl -fsSL https://install.shakerscan.com | sh): mcp, hunt, doctor and version work
without Docker, and any engine subcommand (start, stop, status, update, ...) is handed to
a local engine install when one exists. The adapter and CLI are the runtime's own code, vendored
at build time, and the tools an agent sees come from the instance's live contracts.
Python 3.10 or newer, no third-party dependencies (a USB/NFC security key for shakerscan approve
on Enterprise needs pipx inject shakerscan fido2; shakerscan record needs the record extra,
pipx install 'shakerscan[record]', then python -m playwright install chromium), AGPL-3.0-only. Documentation:
https://github.com/andriyze/shakerscan/blob/main/docs/client.md
With no local, remote, or saved ShakerScan instance configured, check and mcp use the hardcoded https://pub.shakerscan.com service. Once an instance is configured, the client prefers that instance for all such requests and never falls back to public on failure.
1 maintainer
Metadata
1 maintainer
Release files for shakerscan 0.11.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 | Provenance | |
|---|---|---|---|---|
| shakerscan-0.11.0.tar.gz | 343.3 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| shakerscan-0.11.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 818.3 kB
Release files / shakerscan-0.11.0.tar.gz
| Download URL | shakerscan-0.11.0.tar.gz |
|---|---|
| Size | 343.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2a71219af81934c826182482d75549ef3ed3f7fdd39fac3731792c4e2ec7613f
|
|
BLAKE2b-256 checksum How to use checksums |
282981973c5dcc5afad5ed6f218f55c23fdb5bc58162ca15aa1e02c0644cbb66
|
| 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 Oct 18, 2026.
Transparency logRelease files / shakerscan-0.11.0-py3-none-any.whl
| Download URL | shakerscan-0.11.0-py3-none-any.whl |
|---|---|
| Size | 475.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3106356bcdcb711f8313a8117be96afdb99f304bbdd6bcb80b3c95d1b07572df
|
|
BLAKE2b-256 checksum How to use checksums |
60b8ae94c013924f03a4462383469374d8ed4c63bad7d54bc6ba71b5f9d489c1
|
| 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 Oct 18, 2026.
Transparency logSecurity for shakerscan 0.11.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.
Attestation for shakerscan-0.11.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 Oct 18, 2026.
Transparency logA 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
