Kastell vs Vault Knowledge

In-depth architectural comparison of the Kastell and Vault Knowledge 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.

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).
• Primary tools included: Server security audits with remediation, SSH hardening and fail2ban setup, UFW firewall management.

Explore Kastell Details

Choose Vault Knowledge 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: VAULT_DB, VAULT_ROOT.
• Primary tools included: search_concepts, find_contradictions, get_article.

Explore Vault Knowledge Details

Feature & Specification Comparison

Specification	Kastell kastelldev Security	Vault Knowledge Security
Summary	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.	Read-only MCP over a vault's typed knowledge graph: concept search, contradictions, article fetch.
Category & Scope	Security

Tools & Capabilities Breakdown

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).

{
  "mcpServers": {
    "kastelldev-kastell": {
      "command": "npx",
      "args": [
        "-y",
        "kastell"
      ]
    }
  }
}

{
  "mcpServers": {
    "vault-knowledge": {
      "command": "npx",
      "args": [
        "-y",
        "@swins/vault-knowledge-mcp"
      ],
      "env": {
        "VAULT_DB": "YOUR_VAULT_DB_HERE",
        "VAULT_ROOT": "YOUR_VAULT_ROOT_HERE"
      }
    }
  }
}

Related MCP Server Comparisons