Vault Knowledge vs Kastell — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Vault Knowledge vs Kastell
In-depth architectural comparison of the Vault Knowledge and Kastell 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
Vault Knowledge
Security · Local stdio
Quality: 57/100 (Good) | Auth: No auth required
Kastell
Security · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
Verdict Summary: Choose Vault Knowledge if you need specialized Security tools running via a local process. Choose Kastell 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 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.
Semantically search the vault's concept, connection, and Q&A articles for a natural-language query. Returns ranked {slug, title, similarity_score, excerpt, last_modified}. Read-only.
find_contradictions
Traverse the typed reasoning graph for active 'contradicts' edges — the sharpest of six relation types. scope='all' or 'recent_30d'. Returns {from_slug, to_slug, confidence, surfaced_at, source_run_id}. Read-only.
get_article
Fetch one article by slug with frontmatter, body, and resolved inbound/outbound wikilinks. Reads only files under the configured knowledge allowlist. Read-only.
Kastell Tools (6)
Server security audits with remediation
SSH hardening and fail2ban setup
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).
Vault Knowledge is categorized under Security and uses a local stdio subprocess. In contrast, Kastell belongs to Security using local stdio subprocess. Select Vault Knowledge when you need capabilities focused on security and Kastell when you require tools for security.