verity-redteam-core (Verity RedTeam Free)
Open-core empirical security scanner for MCP servers and database-connected AI agents. Apache-2.0.
Quickstart
uv run verity scan
uv run verity test --demo
uv run verity test --sql "SELECT id FROM users"
uv run verity serve
verity scan— zero-Docker workstation discovery and static scanning across local AI client configs, with credential scrubbing.verity test— deterministic probing ofstdioorHTTP/SSEMCP servers, or a single SQL string via--sql, including in-memory demo targets.verity serve— zero-framework stdlib JSON-RPC 2.0 MCP server for external IDE agents.
uv run verity test --demo probes four in-memory synthetic targets with zero Docker:
┌────────────────────────────────┬─────────┬────────┐
│ Target │ CWE │ Result │
├────────────────────────────────┼─────────┼────────┤
│ SQLite Basic Target │ CWE-89 │ VULN │
│ PostgreSQL Multi-Tenant Target │ CWE-639 │ VULN │
│ MongoDB NoSQL Target │ CWE-943 │ VULN │
│ MCP Code Execution Target │ CWE-94 │ VULN │
└────────────────────────────────┴─────────┴────────┘
Capabilities
- Deterministic SQL AST guard (
sqlglot): blocks comment-split queries, stacked statements, and unauthorized catalog access; enforces tenant filters, projection masking, identifier allowlists, and statement timeouts. - Passport fingerprinting: canonical SHA-256 tool hashing for stable server identification.
- OSV vulnerability lookup: offline advisory matching via
mcp-vulnerabilities. - Static rule screening: 13-rule
StaticRuleEvaluatorfor MCP tool schemas at sub-millisecond latency.
Free vs Enterprise
| Capability | verity-redteam-core (Free) |
verity-pro (Enterprise) |
|---|---|---|
| Workstation discovery (9 clients) | ✅ | ✅ |
| 13 static rule screening | ✅ | ✅ |
| Deterministic SQL AST guard | ✅ | ✅ |
| Zero-Docker demo targets | ✅ | ✅ |
| Terminal / Markdown / HTML reports | ✅ | ✅ |
| Snowflake RBAC & time-travel guard | — | ✅ |
| Live database verification oracles | — | ✅ |
| SARIF v2.1.0 export | — | ✅ |
| Penetration automation & canary lab | — | ✅ |
Extensibility
verity-redteam-core is the single source of the runtime abstraction barrier. Enterprise
extensions are discovered dynamically through Python entry points — no core code is
patched or branched:
from importlib.metadata import entry_points
for ep in entry_points(group="verity.plugins"):
ep.load()
A plugin package registers itself in its own pyproject.toml:
[project.entry-points."verity.plugins"]
enterprise = "verity_pro.plugin:register_pro_extensions"
When no plugin is installed, Pro-only actions return a structured
PRO_FEATURE_REQUIRED payload instead of raising ImportError, so core always runs
standalone.
Development
uv sync --extra dev
uv run pytest tests/ -q
uv run ruff check src tests
License
Apache License 2.0 — see LICENSE.
Metadata
Release files for verity-redteam-core 0.1.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 | Actions |
|---|---|---|---|---|
| verity_redteam_core-0.1.0.tar.gz | 104.8 kB | With provenance | Details for verity_redteam_core-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| verity_redteam_core-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for verity_redteam_core-0.1.0-py3-none-any.whl |
Total release size: 239.4 kB
Release files / verity_redteam_core-0.1.0.tar.gz
| Download URL | verity_redteam_core-0.1.0.tar.gz |
|---|---|
| Size | 104.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e50db317fec1722ec88e91ec54a4a7501536462ef30be53c00b9db38972d9e05
|
|
BLAKE2b-256 checksum How to use checksums |
b7e8627206656457544204ec171858af80a3d1ad088b92e7d6c62a38e96e5929
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 17, 2026.
Transparency logRelease files / verity_redteam_core-0.1.0-py3-none-any.whl
| Download URL | verity_redteam_core-0.1.0-py3-none-any.whl |
|---|---|
| Size | 134.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0c2977341e2a26e9fe584795421b6db02e6c22dca0bd887b61ab5f5090a38b87
|
|
BLAKE2b-256 checksum How to use checksums |
fac9bcb30be3bfdc0c833d7c36756cb5323a155a415abbf49bc938ef70c7764f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 17, 2026.
Transparency logSecurity for verity-redteam-core 0.1.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
Both files in this release have been uploaded with provenance metadata.
Attestation for verity_redteam_core-0.1.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 Nov 17, 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.