Husk vs Leakferret

In-depth architectural comparison of the Husk and Leakferret 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 Husk 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).

Explore Husk Details

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

Explore Leakferret Details

Feature & Specification Comparison

Specification	Husk Security	Leakferret Security
Summary	Local-first defensive scanner for vulnerable dependencies, leaked secrets, and risky agent configs	Context-aware secret scanner: lets an AI agent scan, verify, and rewrite secrets before committing.
Category & Scope	Security	Security
Quality signal

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": {
    "husk": {
      "command": "npx",
      "args": [
        "-y",
        "husk"
      ]
    }
  }
}

{
  "mcpServers": {
    "leakferret": {
      "command": "npx",
      "args": [
        "-y",
        "@leakferret/mcp"
      ]
    }
  }
}

Related MCP Server Comparisons