A side-by-side look at the Unprofane 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 Unprofane for security work over a hosted endpoint; 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?
U
Choose Unprofane when
You need dedicated capabilities in the Security domain.
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.
Unprofane is categorized under Security and uses a remote HTTP/SSE transport. Kastell belongs to Security and uses a local stdio subprocess. Pick Unprofane 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.
Unprofane has no declared pricing — check the project's own site. 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 unprofane and kastelldev-kastell as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Unprofane has a quality signal of 39/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Kastell has 61/100 (Good) with 5 views, 0 installs and 60 GitHub stars.