Aegis vs Checker MCP
A side-by-side look at the Aegis and Checker MCP 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 Checker MCP 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 Checker MCP when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
OKSIGENIA_LANG. - You want tools like
check_domain, list_checks, explain_check.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 53/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | OKSIGENIA_LANG |
| Verified owner | Community listing | Community listing |
| GitHub stars | 14 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Aegis | View Checker MCP |
Tools & capabilities
Aegis tools
No tool names declared yet. Check the project README from the listing page.
Checker MCP tools 3
check_domainRun the Oksigenia Checker against a domain and return a scored security report from real live checks (SSL/TLS, email authentication, DNS & infrastructure, web security). Accepts a bare domain or a URL. Optionally restrict to specific categories.list_checksList every check the Oksigenia Checker performs, grouped by category, with the reason each one matters. Useful to know what check ids exist.explain_checkGiven a check id (see list_checks), explain what it verifies, why it matters, and how to remediate a failure.
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"
]
}
}
}
Checker MCP
{
"mcpServers": {
"oksigeniasl-checker-mcp": {
"command": "npx",
"args": [
"-y",
"@oksigenia/checker-mcp"
],
"env": {
"OKSIGENIA_LANG": "YOUR_OKSIGENIA_LANG_HERE"
}
}
}
}
Frequently asked questions
Aegis is categorized under Security and uses a local stdio subprocess. Checker MCP belongs to Security and uses a local stdio subprocess. Pick Aegis for security work and Checker MCP 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. Checker MCP 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 getaegis-aegis and oksigeniasl-checker-mcp 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 2 views, 0 installs and 14 GitHub stars. Checker MCP has 57/100 (Good) with 2 views, 0 installs and 0 GitHub stars.