Aegis vs MCP Regulated AI Compliance
A side-by-side look at the Aegis and MCP Regulated AI Compliance MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Aegis for security work as a local process; choose MCP Regulated AI Compliance 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.
Choose MCP Regulated AI Compliance when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You have the keys it needs:
MCP_STATEFUL, PORT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 53/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | MCP_STATEFULPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Aegis | View MCP Regulated AI Compliance |
Tools & capabilities
Aegis tools
No tool names declared yet. Check the project README from the listing page.
MCP Regulated AI Compliance 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": {
"getaegis-aegis": {
"command": "npx",
"args": [
"-y",
"@getaegis/cli"
]
}
}
}
MCP Regulated AI Compliance
{
"mcpServers": {
"uchit-mcp-regulated-ai-compliance": {
"command": "npx",
"args": [
"-y",
"@hellouchit/mcp-regulated-ai-compliance"
],
"env": {
"MCP_STATEFUL": "YOUR_MCP_STATEFUL_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Frequently asked questions
Aegis is categorized under Security and uses a local stdio subprocess. MCP Regulated AI Compliance belongs to Security and uses a local stdio subprocess. Pick Aegis for security work and MCP Regulated AI Compliance 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.
Aegis has no declared pricing — check the project's own site. MCP Regulated AI Compliance 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 getaegis-aegis and uchit-mcp-regulated-ai-compliance 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 53/100 (Good) with 3 views, 0 installs and 14 GitHub stars. MCP Regulated AI Compliance has 53/100 (Good) with 3 views, 0 installs and 1 GitHub stars.