Fullmakt vs Aegis
A side-by-side look at the Fullmakt and Aegis MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
F
FullmaktSecurityCredential broker for AI agents: scoped, revocable API access with policy enforcement and audit.37FairAuth: not declaredVerdict: choose Fullmakt for security work; choose Aegis for security as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Aegis when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | F Fullmakt | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 37/100 · Fair | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 18 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Fullmakt | View Aegis |
Tools & capabilities
Fullmakt tools
No tool names declared yet. Check the project README from the listing page.
Aegis tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Fullmakt
No confirmed install command for Fullmakt yet — follow the setup steps linked from its listing page rather than a guessed package name.
Aegis
{
"mcpServers": {
"acacian-aegis": {
"command": "uvx",
"args": [
"agent-aegis"
]
}
}
}
Frequently asked questions
Fullmakt is categorized under Security and uses an install path we have not confirmed yet. Aegis belongs to Security and uses a local stdio subprocess. Pick Fullmakt for security work and Aegis for security.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Fullmakt has no confirmed install command yet — follow its own setup instructions.
Fullmakt has no declared pricing — check the project's own site. Aegis is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add fullmakt and acacian-aegis as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Fullmakt has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Aegis has 52/100 (Good) with 4 views, 0 installs and 18 GitHub stars.