ClauseKeeper Compliance Scanner

What ClauseKeeper Compliance Scanner MCP server does

ClauseKeeper Compliance Scanner MCP server makes ClauseKeeper’s compliance scanner available to AI agents through the Model Context Protocol. It is designed to review website privacy-policy content rather than provide legal advice or replace a lawyer’s review.

The scanner evaluates supplied policy text or retrieves a policy from a URL, then reports a score from 0 to 100 and a checklist of clauses that may be missing or stale. Its rule coverage includes GDPR, CCPA/CPRA, cookie requirements, data retention, AI disclosure, COPPA, and other rules maintained by the underlying ClauseKeeper project.

How it works

The MCP package runs locally and uses ClauseKeeper’s rule-based clause engine. It does not require an LLM for the core scan, and the provided setup requires no API keys. An MCP-compatible host starts the server as a local process and sends tool calls over the standard MCP connection.

The available operations are:

• scan_policy_text reviews policy text provided directly by the agent or user.
• scan_policy_url scans a policy identified by a URL.
• list_clause_rules returns the clause rules available to the scanner.

Results are intended to help an agent identify areas for follow-up, such as a missing disclosure or language that may no longer match the configured rules. The output is a compliance-oriented checklist, not a legal determination.

Setup and configuration

Add the server to an MCP host configuration with the clausekeeper-mcp command:

{
  "mcpServers": {
    "clausekeeper": {
      "command": "clausekeeper-mcp"
    }
  }
}

The README specifically shows this configuration for Claude Desktop and Cursor. ClauseKeeper Compliance Scanner MCP server is also described as usable with any MCP host that can launch a standard local command. No service registration, paid credential, or external API key is required for the scanner.

The repository’s broader ClauseKeeper application can be self-hosted, but the MCP usage described here centers on the clausekeeper-mcp executable.

Tools and capabilities

The server provides three focused tools rather than a general document-management interface. Use scan_policy_text when the policy is already available in the conversation or another agent workflow. Use scan_policy_url when the agent should scan a policy published on a website. Use list_clause_rules to inspect the rules before deciding how to interpret or present scan results.

The underlying project is open source and licensed under AGPL-3.0. Its scanner is intended for website legal documents and supports rule-based checks without an LLM dependency.

Limitations and notes

ClauseKeeper Compliance Scanner MCP server reports rule-based findings and should not be treated as legal advice. The project describes the scanner as a starting point and recommends consulting a lawyer for edge cases.

Results depend on the rules available in the installed version. The material also does not document authentication, rate limits, supported URL restrictions, or a mechanism for editing policies through MCP.