AppGenie Compliance MCP vs Aegis
A side-by-side look at the AppGenie Compliance MCP and Aegis MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
AppGenie Compliance MCPSecurity · Remote HTTP/SSECited, standards-aware compliance overlay for AI assistants (ISO, NIST, FedRAMP, IRAP), over MCP.37FairAuth: not declaredVerdict: choose AppGenie Compliance MCP for security work over a hosted endpoint; 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?
AChoose AppGenie Compliance MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a remote HTTP/SSE transport.
Choose Aegis when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A AppGenie Compliance MCP | |
|---|---|---|
| Category | Security | Security |
| Quality signal | 37/100 · Fair | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 14 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View AppGenie Compliance MCP | View Aegis |
Tools & capabilities
AppGenie Compliance MCP 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.
AppGenie Compliance MCP
{
"mcpServers": {
"appgenie-compliance-mcp": {
"command": "npx",
"args": [
"-y",
"appgenie-compliance-mcp"
]
}
}
}
Aegis
{
"mcpServers": {
"getaegis-aegis": {
"command": "npx",
"args": [
"-y",
"@getaegis/cli"
]
}
}
}
Frequently asked questions
AppGenie Compliance MCP is categorized under Security and uses a remote HTTP/SSE transport. Aegis belongs to Security and uses a local stdio subprocess. Pick AppGenie Compliance MCP 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.
AppGenie Compliance MCP has no declared pricing — check the project's own site. Aegis 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 appgenie-compliance-mcp and getaegis-aegis as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, AppGenie Compliance MCP has a quality signal of 37/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Aegis has 55/100 (Good) with 4 views, 0 installs and 14 GitHub stars.