Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@polish-data-protection-mcp search decisions about employee data processing"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
▶ 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.
Claude Code (one line):
claude mcp add ansvar --transport http https://gateway.ansvar.eu/mcpClaude 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.
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).
Polish data protection data for AI compliance tools.
Query Polish data protection data -- regulations, decisions, and requirements from UODO (Personal Data Protection Office) -- directly from Claude, Cursor, or any MCP-compatible client.
Built by Ansvar Systems -- Stockholm, Sweden
Related MCP server: io.github.mister-franklin/gdpr-decisions
Tool | Description |
| Full-text search across UODO decisions (sanctions, administrative decisions, and orders). Returns matching decisions ... |
| Get a specific UODO decision by reference number (e.g., |
| Search UODO guidance documents: guidelines, opinions, recommendations, and FAQs. Covers GDPR implementation, employee... |
| Get a specific UODO guidance document by its database ID. |
| List all covered data protection topics with Polish and English names. Use topic IDs to filter decisions and guidelines. |
| Return metadata about this MCP server: version, data source, coverage, and tool list. |
All tools return structured data with source references and timestamps.
All content is sourced from official Polish regulatory publications:
UODO (Personal Data Protection Office) -- Official regulatory authority
Database updates are periodic and may lag official publications
Freshness checks run via GitHub Actions workflows
Last-updated timestamps in tool responses indicate data age
See sources.yml for full provenance metadata.
This project uses multiple layers of automated security scanning:
Scanner | What It Does | Schedule |
CodeQL | Static analysis for security vulnerabilities | Weekly + PRs |
Semgrep | SAST scanning (OWASP top 10, secrets, TypeScript) | Every push |
Gitleaks | Secret detection across git history | Every push |
Trivy | CVE scanning on filesystem and npm dependencies | Daily |
Docker Security | Container image scanning + SBOM generation | Daily |
Socket.dev | Supply chain attack detection | PRs |
Dependabot | Automated dependency updates | Weekly |
See SECURITY.md for the full policy and vulnerability reporting.
THIS TOOL IS NOT REGULATORY OR LEGAL ADVICE
Regulatory data is sourced from official publications by UODO (Personal Data Protection Office). However:
This is a research tool, not a substitute for professional regulatory counsel
Verify all references against primary sources before making compliance decisions
Coverage may be incomplete -- do not rely solely on this for regulatory research
Before using professionally, read: DISCLAIMER.md | PRIVACY.md
Queries go through the Claude API. For privileged or confidential matters, use on-premise deployment. See PRIVACY.md for details.
git clone https://github.com/Ansvar-Systems/polish-data-protection-mcp
cd polish-data-protection-mcp
npm install
npm run build
npm testnpm run dev # Start MCP server
npx @anthropic/mcp-inspector node dist/index.js # Test with MCP Inspectornpm run build:db # Rebuild SQLite database from seed data
npm run check-updates # Check for new regulatory dataFull fleet at ansvar.eu/gateway.
Contributions welcome! See CONTRIBUTING.md for guidelines.
Apache License 2.0. See LICENSE for details.
Regulatory data sourced from official government publications. See sources.yml for per-source licensing details.
We build AI-powered compliance and legal research tools for the European market. Our MCP fleet provides structured, verified regulatory data to AI assistants -- so compliance professionals can work with accurate sources instead of guessing.
ansvar.eu -- Stockholm, Sweden
Return metadata about this MCP server: version, data source, coverage, and tool list.
Inputs: no named parameters.
Get a specific UODO decision by reference number (e.g., 'ZSPR.421.1.2019', 'DKN.5112.1.2019').
Inputs: reference (required).
Get a specific UODO guidance document by its database ID.
Inputs: id (required).
List all covered data protection topics with Polish and English names. Use topic IDs to filter decisions and guidelines.
Inputs: no named parameters.
Full-text search across UODO decisions (sanctions, administrative decisions, and orders). Returns matching decisions with reference, entity name, fine amount, and GDPR articles cited.
Inputs: query (required), type, limit, topic.
Search UODO guidance documents: guidelines, opinions, recommendations, and FAQs. Covers GDPR implementation, employee monitoring, cookies, DPIA methodology, and more.
Inputs: query (required), type, limit, topic.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 6 tools
Each tool has a clearly distinct purpose: search decisions, get a specific decision, search guidelines, get a specific guideline, list topics, and server metadata. There is no overlap or ambiguity among them.
Most tools follow a consistent verb_noun pattern (search_decisions, get_decision, search_guidelines, get_guideline, list_topics). The 'about' tool is a minor deviation but not disruptive.
With 6 tools, the server is well-scoped for its purpose: covering search and retrieval of decisions and guidelines, plus topic filtering and metadata. Each tool earns its place.
The tool surface fully covers the intended domain: search and retrieve both decisions and guidelines, with topic support for filtering. Since this is a read-only public data source, no CRUD operations are needed.
Polish and EU law: statutes, rulings, UODO/UOKiK/KNF, EU regulations, citation checks. Free tier.
Polish statutes (Dziennik Ustaw, ELI) and court rulings (SAOS) for AI agents. Runs on Apify.
Semantic search over Polish law and case law, citing the exact in-force article.
Privacy law your AI assistant can cite: the exact clause and its version. GDPR and UAE PDPL today.
