Aegis runs on your own machine — the client starts it, so there is no endpoint to ping. 51 installs a week from npm. Last commit 6 Aug 2026.
Credential isolation for AI agents. Inject secrets at the network boundary.
We read the source, 22 h ago · rules 3dff92dd89df
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
? path.join(config.dataDir, info.dbPath)
hint: `Update scopes with: aegis vault update --name ${credential.name} --scopes ${scopeList},${reqMethod === 'GET' ? 'read' : 'write'}`,
execFileSync(which, [command], { stdio: 'pipe' });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add aegis -- npx -y @getaegis/cli
{
"mcpServers": {
"aegis": {
"args": [
"-y",
"@getaegis/cli"
],
"command": "npx"
}
}
}
[mcp_servers.aegis]
command = "npx"
args = ["-y", "@getaegis/cli"]
{
"mcpServers": {
"aegis": {
"args": [
"-y",
"@getaegis/cli"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"aegis": {
"args": [
"-y",
"@getaegis/cli"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
AEGIS_MASTER_KEY (Master encryption key for the credential vault), AEGIS_SALT (Hex-encoded 32-byte salt for key derivation (generated by aegis init)), AEGIS_DATA_DIR (Directory for vault databases and registry (default: .aegis/)), AEGIS_PORT (Gate proxy port (default: 3100)), AEGIS_LOG_LEVEL (Log verbosity: debug, info, warn, error (default: info)), AEGIS_LOG_FORMAT (Log output format: json or pretty (default: json)), AEGIS_VAULT (Named vault to use (default: default)), AEGIS_REQUIRE_AGENT_AUTH (Require agent authentication on every request (true/false, default: false)), AEGIS_POLICY_MODE (Policy enforcement mode: enforce, dry-run, or off (default: enforce)), AEGIS_POLICIES_DIR (Directory containing YAML policy files), AEGIS_METRICS (Enable Prometheus metrics endpoint (true/false, default: true)).
The author declared them in the registry entry; get the values from the project itself.
Credential isolation for AI agents: placeholder secrets, policy checks, optional human approval.
Zero-knowledge MCP secrets vault for AI agents: secrets injected at runtime, never seen by the model
Encrypted secrets and credential management for agents
Security firewall for AI agents — scans MCP calls for injection, secrets, and risks.
Secure Firecracker microVM sandboxes for AI agents: network policy, PII & injection guardrails.
Credential custody for agents: use secrets blind (ssh/http/smtp/git/db), never in context.
Secure secrets proxy for AI agents — manages API keys so agents never see raw credentials.
Security for AI agents: MCP audits, secret redaction, skill vetting, network scans, agent checkout.
Answers built from our own checks of this server.