ClauseKeeper Compliance Scanner vs Lexvibe

In-depth architectural comparison of the ClauseKeeper Compliance Scanner and Lexvibe 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 ClauseKeeper Compliance Scanner when:

• You need dedicated capabilities in the Legal domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore ClauseKeeper Compliance Scanner Details

Choose Lexvibe when:

• You need dedicated capabilities in the Legal domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Lexvibe Details

Feature & Specification Comparison

Specification	ClauseKeeper Compliance Scanner Legal	Lexvibe Legal
Summary	Scan website legal docs for missing or stale compliance clauses. Rule-based, no LLM.	One-step legal compliance for vibe-coded apps: privacy, terms, cookie banner and EU AI Act check.
Category & Scope	Legal	Legal
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": {
    "clausekeeper-compliance-scanner": {
      "command": "npx",
      "args": [
        "-y",
        "clausekeeper-compliance-scanner"
      ]
    }
  }
}

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

Related MCP Server Comparisons