Cordon vs AiSOC
A side-by-side look at the Cordon and AiSOC MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Cordon for security work as a local process; choose AiSOC 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 Cordon when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
Choose AiSOC 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 | ||
|---|---|---|
| Category | Security | Security |
| Quality signal | 41/100 · Fair | 59/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 | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 3,143 |
| Directory activity | 2 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Cordon | View AiSOC |
Tools & capabilities
Cordon tools
No tool names declared yet. Check the project README from the listing page.
AiSOC 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.
Cordon
{
"mcpServers": {
"cordon": {
"command": "npx",
"args": [
"-y",
"@getcordon/cli"
]
}
}
}
AiSOC
{
"mcpServers": {
"aisoc": {
"command": "uvx",
"args": [
"aisoc-sandbox"
]
}
}
}
Frequently asked questions
Cordon is categorized under Security and uses a local stdio subprocess. AiSOC belongs to Security and uses a local stdio subprocess. Pick Cordon for security work and AiSOC 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.
Cordon has no declared pricing — check the project's own site. AiSOC 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 cordon and aisoc as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Cordon has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 2 GitHub stars. AiSOC has 59/100 (Good) with 1 views, 0 installs and 3,143 GitHub stars.