Aegis MCP Server

Aegis MCP server exists for a simple reason — assistants are far more useful when they can act on Aegis directly instead of describing what you should do. Six-gate governance for AI agents: PROCEED/PAUSE/HALT decisions with hash-chained audit trails.

What you get

Give your agent a decision gate it can call before it acts — and an audit record compliance can actually read (NIST AI RMF, EU AI Act Annex IV).

• Six gates — Risk, Profit, Novelty, Complexity, Quality, Utility — calibrated thresholds, KL-divergence drift detection
• Audit-ready — hash-chained decision log; NIST AI RMF and EU AI Act Annex IV artifact generation
• Five integration surfaces — MCP (this repo), Python SDK, REST API, CLI, GitHub Action

What the assistant can call

Once Aegis is connected, these are the calls the assistant has available:

• aegis_evaluate_proposal — Full six-gate evaluation of a proposal; returns PROCEED/PAUSE/HALT/ESCALATE with per-gate scores and rationale
• aegis_quick_risk_check — Fast risk screen for a proposed change
• aegis_check_thresholds — Current gate threshold configuration
• aegis_get_scoring_guide — Domain-specific guidance for deriving gate parameters (e.g. cicd)
• aegis_record_proposal — Record a proposal for later verification
• aegis_list_proposals — List recorded proposals
• aegis_verify_proposals — Verify recorded proposals against outcomes
• aegis_list_decisions — List past governance decisions
• aegis_get_decision — Fetch a specific decision with full audit detail
• aegis_crypto_status — Hash-chain audit integrity status

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Configuration and credentials

You will need 2 environment variables: AEGIS_API_KEY, YOUR_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Aegis's toolset — aegis_evaluate_proposal, aegis_quick_risk_check, aegis_check_thresholds and 7 more — is a fair guide to whether it matches your workflow. It is maintained by com.undercurrentholdings; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Aegis's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 10 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Aegis.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the aegis mcp server does with a few real requests.