
Aegis
io.github.getaegis由 GitHub 账号 getaegis 发布v1.0.5更新于 Oct 24, 2026
Credential isolation for AI agents. Inject secrets at the network boundary.
概览
本地优先的凭据隔离代理,让 AI 助手通过 Aegis 调用外部 API,由它在网络边界注入已保存的密钥。
- 可以做什么
- 向已配置的服务发起带认证的 API 调用,由 Aegis 注入保存的凭据,助手本身看不到密钥(aegis_proxy_request)。列出可用服务名称,绝不返回密钥内容(aegis_list_services)。查询 Aegis 的运行状态与健康状况(aegis_health)。请求与 HTTP 网关走同一套流程:域名白名单、代理身份认证、请求体检查、限流和审计日志。
- 适用场景
- 当助手需要调用 Slack、GitHub、Stripe 等服务,但你不希望把原始 API 密钥写进 MCP 配置或让模型看到,并希望对出站请求做域名限制和审计时使用。
- 运行要求
- 以 npm 包 @getaegis/cli 在本地通过 stdio 运行,需要 Node.js 20 或更高版本。需先执行 aegis init 初始化,并提供密钥 AEGIS_MASTER_KEY 和 AEGIS_SALT;凭据须先加入 vault。可选配置包括 AEGIS_DATA_DIR、AEGIS_POLICIES_DIR、AEGIS_POLICY_MODE、AEGIS_PORT、AEGIS_REQUIRE_AGENT_AUTH、AEGIS_VAULT、AEGIS_METRICS 及日志选项。需要访问目标 API 的网络。
安装
在 SourceWeft 中
- 打开 控制台中的 Aegis,将其添加到工作区。
- 为需要使用其工具的对话启用该服务。
Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。
其他 MCP 客户端
参照 仓库 中的启动说明。
README
Aegis
[CI] [npm version] [Docker] [License]
Stop putting API keys where AI agents can read them.
Aegis is a local-first credential isolation proxy for AI agents. It sits between your agent and the APIs it calls — injecting secrets at the network boundary so the agent never sees, stores, or transmits real credentials.
How It Works
[How Aegis works — agent sends request through Gate, credentials injected at the network boundary]
Why?
AI agents (Claude, GPT, Cursor, custom bots) increasingly call real APIs — Slack, GitHub, Stripe, databases. The current pattern is dangerous:
- Agents see raw API keys — one prompt injection exfiltrates them
- No domain guard — a compromised agent can send your Slack token to
evil.com - No audit trail — you can't see what an agent did with your credentials
- No access control — every agent can use every credential
Aegis solves all four. Your agent makes HTTP calls through a local proxy. Aegis handles authentication, enforces domain restrictions, and logs everything.
Quick Start
Production Setup (with agent auth)
MCP Integration
Aegis is a first-class MCP server. Any MCP-compatible AI agent can use it natively — no HTTP calls needed.
Before (plaintext key in config):
After (Aegis — no key visible):
Generate the config for your AI host:
The MCP server exposes three tools:
The MCP server replicates the full Gate security pipeline: domain guard, agent auth, body inspection, rate limiting, audit logging.
Setup Guides
Features
Example Integrations
Step-by-step guides with config files and policies included:
- Slack Bot — Protect your Slack bot token with domain-restricted proxy access
- GitHub Integration — Secure GitHub PAT with per-agent grants and read-only policies
- Stripe Backend — Isolate Stripe API keys with body inspection and rate limiting
- OpenClaw Skill — Aegis skill for OpenClaw personal AI assistant
Security
- Published STRIDE threat model — 28 threats analysed, 0 critical/high unmitigated findings
- Full security architecture documentation (trust boundaries, crypto pipeline, data flow)
- AES-256-GCM + ChaCha20-Poly1305 encryption at rest
- Domain guard enforced on every request — no bypass
- Agent tokens stored as SHA-256 hashes — cannot be recovered, only regenerated
- Request body inspection for credential pattern detection
- Open source (Apache 2.0) — read the code
How Aegis Compares
See full comparison for detailed breakdowns against each approach.
Documentation
Install
Requires Node.js ≥ 20 — check with node -v
Development
See CONTRIBUTING.md for code style, PR process, and architecture overview.
License
来源:README.md,提交 f1321b3
工具
0版本历史
1- v1.0.5最新Sep 16, 2026
评分
已满足适用检查项的 50%
该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。
- 近 30 天内可连通25 分
请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。
- 已声明认证方式10 分
请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。
- 已列出工具15 分
请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。
- 描述必需15 分
- 图标10 分
- 文档15 分
- 许可证10 分