Czech Law MCP

▶ Try this MCP instantly via Ansvar Gateway

50 free queries/day · no card required · OAuth signup at ansvar.eu/gateway

One endpoint, one OAuth signup, access from any MCP-compatible client.

Connect

Claude Code (one line):

claude mcp add ansvar --transport http https://gateway.ansvar.eu/mcp

Claude Desktop / Cursor — add to claude_desktop_config.json (or mcp.json):

{
  "mcpServers": {
    "ansvar": {
      "type": "url",
      "url": "https://gateway.ansvar.eu/mcp"
    }
  }
}

Claude.ai — Settings → Connectors → Add custom connector → paste https://gateway.ansvar.eu/mcp

First request opens an OAuth flow at ansvar.eu/gateway. After signup, your client is bound to your account; tier (free / premium / team / company) determines fan-out, quota, and which downstream MCPs are reachable.

Self-host this MCP

You can also clone this repo and build the corpus yourself. The schema, fetcher, and tool implementations all live here. What is not in the repo is the pre-built database — TDM and standards-licensing constraints on the upstream sources mean we host the corpus on Ansvar infrastructure rather than redistribute it as a public artifact.

Build your own: run this repo's ingestion script (entry-point varies per repo — typically scripts/ingest.sh, npm run ingest, or make ingest; check the repo root).

MCP server for Czech Law — 45,899 statutes from www.e-sbirka.cz.

What this is

This server indexes the legal materials listed under Sources below and exposes them via the Model Context Protocol. Part of the Ansvar MCP fleet — source-available servers published for self-hosting.

It makes no outbound network calls except to the upstream sources during ingestion — no analytics, no phone-home.

Coverage

• Corpus: Czech Law — 45,899 statutes, 461,231 provisions
• Jurisdiction code: CZ
• Corpus snapshot: 2026-02-22

The corpus is rebuilt from the upstream sources by the included ingestion script; re-run periodically to refresh.

See Sources below for source URLs, terms, and reuse conditions.

Why this exists

LLMs answering compliance, security, or legal questions from training data alone will fabricate citations — confidently producing article numbers, statute names, and source URLs that do not exist, or that do not say what the model claims. This MCP exists so an agent can call a tool that returns the real text, the real identifier, and the real source URL straight from the indexed materials — and ground an answer rather than recall it.

One MCP, one corpus. The point is composition.

The Ansvar Gateway (ansvar.eu) joins this MCP with the rest of the Ansvar fleet behind a single authenticated endpoint — 300+ servers covering legal jurisdictions, EU regulations, security frameworks, sector regulators, privacy-pattern catalogues, and risk-scoring tools. That lets an agent run cross-domain workflows that no single MCP can serve alone:

• Threat model and TARA. Threat enumeration → known component vulnerabilities → severity scoring → applicable AI, cybersecurity, and automotive obligations → privacy threats. Every finding traceable to its source.
• Gap analysis. Target framework requirements → current-state evidence → unmet obligations → remediation guidance and authority opinions. Every gap traceable to the specific requirement that flagged it.
• Data Protection Impact Assessment. Privacy regulation articles → national DPA guidance → privacy-pattern catalogue → applicable case

... View full README on GitHub