Aegis vs Fullmakt
A side-by-side look at the Aegis and Fullmakt 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 Aegis for security work as a local process; choose Fullmakt for security. 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 | 52/100 · Good | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Local subprocess (stdio) | — |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 18 | — |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Aegis | View Fullmakt |
Tools & capabilities
Aegis tools
No tool names declared yet. Check the project README from the listing page.
Fullmakt 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.
Aegis
{
"mcpServers": {
"acacian-aegis": {
"command": "uvx",
"args": [
"agent-aegis"
]
}
}
}
Fullmakt
No confirmed install command for Fullmakt yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Aegis is categorized under Security and uses a local stdio subprocess. Fullmakt belongs to Security and uses an install path we have not confirmed yet. Pick Aegis for security work and Fullmakt 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.
Aegis is listed as free. Auth: no auth required. Fullmakt has no declared pricing — check the project's own site. 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 acacian-aegis and fullmakt as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aegis has a quality signal of 52/100 (Good) with 4 views, 0 installs and 18 GitHub stars. Fullmakt has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.