In-depth architectural comparison of the Kastell and Arai MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Kastell
Security · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Arai
Security · Local stdio
Quality: 49/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Kastell if you need specialized Security tools running via a local process. Choose Arai if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Kastell when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: KASTELL_API_KEY, KASTELL_PROVIDER_TOKEN, KASTELL_SSH_KEY_PATH, KASTELL_CONFIG_PATH.
Primary tools included: 413 security checks in 29 categories, Automated safe fixes and 19-step production hardening, Compliance mapping to CIS, PCI-DSS, HIPAA.
Server security auditing and hardening toolkit. 413 security checks across 29 categories (SSH, Firewall, Docker, TLS, HTTP Headers), CIS/PCI-DSS/HIPAA compliance mapping, 19-step production hardening, fleet management, and forensic evidence collection. Supports Hetzner, DigitalOcean, Vultr, and Linode. 13 MCP tools.
Policy enforcement for AI coding agents derived from existing instruction files (CLAUDE.md, .cursorrules, .windsurfrules, .github/copilot-instructions.md) — no separate YAML to maintain. Rules with prohibitive predicates (never, forbids, mustnot) emit permissionDecision: deny to block tool calls in Claude Code; advisory rules inject context. PostToolUse is correlated with PreToolUse to produce per-rule obeyed/ignored compliance verdicts in a local JSONL audit log. MCP tools — araiaddguard (register rules mid-session), arailistguards, arairecentdecisions — work in any MCP client (Claude Desktop, Cursor, Windsurf, Cline). No network on the hook hot path; opt-out anonymous telemetry.
Tools & Capabilities Breakdown
Kastell Tools (6)
413 security checks in 29 categories
Automated safe fixes and 19-step production hardening
Compliance mapping to CIS, PCI-DSS, HIPAA
Fleet management with multi-server support
Built-in MCP server with 17 AI tools
Support for Hetzner, DigitalOcean, Vultr, Linode
Arai Tools (6)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Kastell is categorized under Security and uses a local stdio subprocess. In contrast, Arai belongs to Security using local stdio subprocess. Select Kastell when you need capabilities focused on security and Arai when you require tools for security.