Sealkeep vs Kastell
A side-by-side look at the Sealkeep and Kastell MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Sealkeep for security work as a local process; choose Kastell 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 Sealkeep when
- You need dedicated capabilities in the Security domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
Choose Kastell 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.
Tools & capabilities
Sealkeep tools
No tool names declared yet. Check the project README from the listing page.
Kastell 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.
Sealkeep
{
"mcpServers": {
"sealkeep": {
"command": "npx",
"args": [
"-y",
"@munhq/sealkeep"
]
}
}
}
Kastell
{
"mcpServers": {
"kastelldev-kastell": {
"command": "npx",
"args": [
"-y",
"kastell"
]
}
}
}
Frequently asked questions
Sealkeep is categorized under Security and uses a local stdio subprocess. Kastell belongs to Security and uses a local stdio subprocess. Pick Sealkeep for security work and Kastell 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.
Sealkeep is listed as free. Auth: no auth required. Kastell 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 sealkeep and kastelldev-kastell as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Sealkeep has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 1 GitHub stars. Kastell has 61/100 (Good) with 4 views, 0 installs and 60 GitHub stars.
