Obsidian Regulatory MCP vs TCU (Licitante Inidôneo)

In-depth architectural comparison of the Obsidian Regulatory MCP 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 Obsidian Regulatory MCP 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: Semantic search across 850+ official regulatory sources, Jurisdiction, framework, and status filters, Enforcement and product recall lookup.

Explore Obsidian Regulatory MCP 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	Obsidian Regulatory MCP Legal	TCU (Licitante Inidôneo) Legal
Summary	Verified, tier-0 regulatory data for AI across 850+ official sources and 50+ jurisdictions.	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": {
    "obsidian-regulatory-mcp": {
      "url": "https://obsidianri.com/mcp"
    }
  }
}

{
  "mcpServers": {
    "tcu-licitante-inid-neo": {
      "url": "https://api.mcp.ai/p_tcu_inidoneo"
    }
  }
}

Related MCP Server Comparisons