ClauseKeeper Compliance Scanner vs TCU (Licitante Inidôneo)

In-depth architectural comparison of the ClauseKeeper Compliance Scanner and TCU (Licitante Inidôneo) 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).
• Primary tools included: Scan policy text, Scan policy URLs, Return a 0–100 compliance score.

Explore ClauseKeeper Compliance Scanner Details

Choose TCU (Licitante Inidôneo) when:

• You need dedicated capabilities in the Legal domain.
• You prefer remote streaming HTTP/SSE transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).
• Primary tools included: CPF and CNPJ certificate lookups, Single read-only consultation tool, MCP over HTTP endpoint.

Feature & Specification Comparison

Specification	ClauseKeeper Compliance Scanner Legal	TCU (Licitante Inidôneo) Legal
Summary	Scan website legal docs for missing or stale compliance clauses. Rule-based, no LLM.	Issues the disreputable-bidder clearance at the Federal Audit Court (TCU) for a person or company fr
Category & Scope	Legal	Legal

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": {
    "tcu-licitante-inid-neo": {
      "url": "https://api.mcp.ai/p_tcu_inidoneo"
    }
  }
}

Related MCP Server Comparisons