Skip to main content

Mantivor CLI

Scan the MCP servers in your Mantivor organisation from a terminal or a CI pipeline, and fail the build when a scan finds something.

Mantivor is a hosted security scanner for Model Context Protocol servers. This package is its command-line client: it talks to the hosted API over HTTPS and does nothing else, which is why it installs in about 2.7 MB from two direct dependencies (httpx and typer-slim). The scanning happens on our side, not on your runner.

You need a Mantivor organisation to use this. Sign up free at mantivor.io — the free tier covers one server.

uv tool install mantivor     # or: pipx install mantivor
mantivor login
mantivor scan --hosted <server-id>

Commands

Command What it does
mantivor login Store an API key (prompted, never echoed, never an argv flag)
mantivor logout Remove the stored key
mantivor auth status Show which credential is active, without printing it
mantivor scan --hosted <id> Scan a server in your organisation
mantivor findings List findings, newest first

mantivor --help lists every flag.

CI

Set VORLOX_API_KEY instead of running mantivor login — a pipeline has no terminal to prompt at, and a key passed as a command-line flag lands in the build log. The variable takes precedence over a stored credential, so a job is never affected by whoever last logged in on the runner.

export VORLOX_API_KEY=vlx_live_...
mantivor scan --hosted <server-id> --fail-on high

--fail-on takes info, low, medium, high or critical, and is unset by default.

Exit codes: 0 scan completed and the gate passed, 1 scan completed and a finding met or exceeded --fail-on, 2 the scan could not run at all (no credential, refused, unreachable). 1 and 2 are kept distinct so a pipeline can tell "we found something" from "we never looked".

The environment variables are spelled VORLOX_* — VORLOX_API_KEY and VORLOX_API_URL. That is not a typo and not stale documentation: Vorlox was this product's former name, and the variables keep the old spelling so existing pipelines do not break. They are the correct, current names.

Before the CLI can scan a server

A person must add the server in the Mantivor dashboard and confirm they are authorised to scan it. An API key cannot do this for itself — a pipeline must not be able to manufacture the authorisation for the target it then scans. The server's page shows its ID once it is confirmed.

Your key needs the scans:write scope to scan, and findings:read to read findings. Scopes are fixed when a key is created; to change them, mint a new key. Create keys at Settings → API keys in the dashboard.

Scope of this package

Hosted commands only. Scanning a local MCP server from your own machine (--name / --endpoint / --transport) is not part of this package — the detectors are not shipped here. Passing those flags prints an explanation rather than an unknown-option error.

Licence

Proprietary. Installing and running it against your own Mantivor organisation is permitted; redistribution and modification are not. The full terms ship in the package as LICENSE.

Support: mantivor.io/support · Questions about the licence: contact@mantivor.io

Metadata

Release files for mantivor 0.1.2

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

Built distribution (wheel)

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

Release files / mantivor-0.1.2-py3-none-any.whl

Download URL mantivor-0.1.2-py3-none-any.whl
Size 24.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
052ada543e7e8072eddbba0961fefe518893555a94ee8544e431ccb76af2c113
BLAKE2b-256 checksum
How to use checksums
3d82e03074c9daf7a4b9a4066c05152bf19e274c08ce062dec25a7b1f32eef60
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 Aug 9, 2026.

Transparency log

Security for mantivor 0.1.2

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 1 file in this release has been uploaded with provenance metadata.

Attestation for mantivor-0.1.2-py3-none-any.whl

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 Aug 9, 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.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.2 This release

1 release file Full provenance

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