TCU (Licitante Inidôneo) vs OpenWorkProof

In-depth architectural comparison of the TCU (Licitante Inidôneo) and OpenWorkProof 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 TCU (Licitante Inidôneo) 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 TCU (Licitante Inidôneo) Details

Choose OpenWorkProof 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 OpenWorkProof Details

Feature & Specification Comparison

Specification	TCU (Licitante Inidôneo) Legal	OpenWorkProof Legal
Summary	Issues the disreputable-bidder clearance at the Federal Audit Court (TCU) for a person or company fr	Verifiable execution for AI agents: Ed25519-signed work contracts and audit trails.
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": {
    "tcu-licitante-inid-neo": {
      "command": "npx",
      "args": [
        "-y",
        "tcu-licitante-inid-neo"
      ]
    }
  }
}

{
  "mcpServers": {
    "openworkproof": {
      "command": "uvx",
      "args": [
        "openworkproof"
      ]
    }
  }
}

Related MCP Server Comparisons