Side-by-Side Model Context Protocol Comparison

Kastell vs Depguard

In-depth architectural comparison of the Kastell and Depguard 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: 48/100 (Fair) | Auth: No auth required
Depguard
Security · Local stdio
Quality: 53/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Kastell if you need specialized Security tools running via a local process. Choose Depguard 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?

Kastell logo

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.
Depguard logo

Choose Depguard 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: Pre-install package guardian with allow/warn/block decisions, Static code analysis and vulnerability audit using npm and GitHub advisories, AI hallucination guard to detect typosquats and fake packages.

Feature & Specification Comparison

Specification
Kastell logo
Kastell
kastelldev
Security
Depguard logo
Depguard
mopanc
Security
SummaryServer 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.Pre-install guardian for npm packages with static code analysis, supply-chain attack detection, vulnerability audit (npm + GitHub Advisory Database), AI hallucination guard, and CycloneDX 1.6 SBOM generation with VEX. 28 MCP tools. Zero runtime dependencies — the SBOM serializer is implemented natively against the public CycloneDX schema.
Category & ScopeSecuritySecurity
Quality signal48/100 (Fair)53/100 (Fair)
Transport ProtocolLocal Subprocess (stdio)Local Subprocess (stdio)
Auth RequirementNo auth requiredNo auth required
Pricing ModelFree / Open SourceFree / Open Source
Required Env Vars
KASTELL_API_KEYKASTELL_PROVIDER_TOKENKASTELL_SSH_KEY_PATHKASTELL_CONFIG_PATH
None required
Compatible Clients
Claude DesktopCursorWindsurfClineVS Code
Claude DesktopCursorWindsurfClineVS Code
Install path signalnpx · lownpx · high
Engagement & Health 2 views 0 copies 0 upvotes 56 stars 1 views 0 copies 0 upvotes 15 stars
Verified / OfficialCommunity ListingCommunity Listing
Open full listingView Kastell ListingView Depguard Listing

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

Depguard Tools (6)

Pre-install package guardian with allow/warn/block decisions
Static code analysis and vulnerability audit using npm and GitHub advisories
AI hallucination guard to detect typosquats and fake packages
Remediation planner grouping vulnerabilities by dependency parents
CycloneDX 1.6 SBOM generation with VEX support
SARIF v2.1.0 output compatible with GitHub Code Scanning

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 Configuration
mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "kastelldev-kastell": {
      "command": "npx",
      "args": [
        "-y",
        "kastelldev-kastell"
      ],
      "env": {
        "KASTELL_API_KEY": "YOUR_KASTELL_API_KEY_HERE",
        "KASTELL_PROVIDER_TOKEN": "YOUR_KASTELL_PROVIDER_TOKEN_HERE",
        "KASTELL_SSH_KEY_PATH": "YOUR_KASTELL_SSH_KEY_PATH_HERE",
        "KASTELL_CONFIG_PATH": "YOUR_KASTELL_CONFIG_PATH_HERE"
      }
    }
  }
}
Depguard Configuration
mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mopanc-depguard": {
      "command": "npx",
      "args": [
        "-y",
        "npx"
      ]
    }
  }
}

Frequently Asked Questions

Kastell is categorized under Security and uses a local stdio subprocess. In contrast, Depguard belongs to Security using local stdio subprocess. Select Kastell when you need capabilities focused on security and Depguard when you require tools for security.

More alternatives to KastellMore alternatives to DepguardSecurity category hub

Related MCP Server Comparisons

Popular comparisons with Kastell

Popular comparisons with Depguard