Aegis MCP (v0.1)
Aegis encodes a project's threat model in security-context.yaml and exposes deterministic security guidance through MCP tools for coding agents.
What Was Executed From the Build Plan
The repository now includes the v0.1 deliverables defined in aegis-build-plan.md:
- Schema design
- JSON Schema:
schemas/security-context.schema.json - Example:
examples/security-context.example.yaml - Template:
templates/security-context.template.yaml
- JSON Schema:
- MCP server
- Tooling surface in
src/aegis/server.py - Tools:
aegis_assess,aegis_validate,aegis_init - Resource:
aegis://summary
- Tooling surface in
- Deterministic assess semantics
- Matching/merge/conflict logic in
src/aegis/engine.py
- Matching/merge/conflict logic in
- Validation
- Schema + normative contract checks in
src/aegis/validation.py
- Schema + normative contract checks in
- Security context generation
aegis_initinsrc/aegis/init_tool.pywith Claude-assisted mode and deterministic fallback mode
- Agent integration templates
agent-templates/
- Reliability feasibility fixtures
scenarios/trigger-scenarios.jsonlscenarios/mock-aegis-assess.json
Install
Install from PyPI (recommended):
python -m pip install aegis-mcp
Optional for Claude-assisted aegis_init:
python -m pip install "aegis-mcp[init-llm]"
For local development from this repository:
python -m pip install -e .
Optional local development install with Claude-assisted mode:
python -m pip install -e ".[init-llm]"
Validate a Security Context
aegis-validate examples/security-context.example.yaml
Start the MCP Server
aegis-server --config examples/security-context.example.yaml
Equivalent command from the build plan:
{
"mcpServers": {
"aegis": {
"command": "python",
"args": ["-m", "aegis.server", "--config", "./security-context.yaml"]
}
}
}
Tool Contract
aegis_assess response always includes:
requirementsapproved_patternsanti_patternsmatchedwarningsconflictsno_match
See aegis-build-plan.md and docs/schema-reference.md for details.
Metadata
Release files for aegis-mcp 0.1.1
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 |
|---|---|---|---|---|
| aegis_mcp-0.1.1.tar.gz | 26.3 kB | With provenance | Details for aegis_mcp-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| aegis_mcp-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for aegis_mcp-0.1.1-py3-none-any.whl |
Total release size: 47.5 kB
Release files / aegis_mcp-0.1.1.tar.gz
| Download URL | aegis_mcp-0.1.1.tar.gz |
|---|---|
| Size | 26.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bad014480b3e54d92b46c2d97daed5888f4e678e5754ea7396c6883d86048797
|
|
BLAKE2b-256 checksum How to use checksums |
7b8871e2dd0d3c8d54759a55fa557c1b1e05e03467ebb8d9387f0d1956d4225b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 11, 2026.
Transparency logRelease files / aegis_mcp-0.1.1-py3-none-any.whl
| Download URL | aegis_mcp-0.1.1-py3-none-any.whl |
|---|---|
| Size | 21.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1ab94fbdfb84667c3a42c13d771ae4dc734f603dcdffb45b8fb1babe64aabc3d
|
|
BLAKE2b-256 checksum How to use checksums |
d493f69ab10c14b6a310c5e6ca5bd90b9518bde43438287a5453007d4d20cf86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Feb 11, 2026.
Transparency logSecurity for aegis-mcp 0.1.1
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 aegis_mcp-0.1.1.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 Feb 11, 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.