Skip to main content
Glama
disclos-article-50

disclos-article-50

by GatisOzols

disclos-article-50

An MCP server that generates the exact EU AI Act Article 50 transparency disclosure you have to show users, in all 24 EU languages, with copy-paste code.

Article 50 is the part of the Act that hits almost every SaaS shipping an AI feature into the EU, and it takes effect on 2 August 2026. This tool hands you the right disclosure text and tells you where to put it, from inside Claude or Cursor.

Built and maintained by Disclos. The companion classifier is disclos-eu-ai-act.


What it does

Two tools:

Tool

What it returns

article_50_disclosure

The visible label for your use case in the language you pick, where and when to show it, and a copy-paste snippet (HTML for chatbots, a machine-readable marker for generated content).

which_article_50_rules_apply

From a few yes/no facts about your product, which Article 50 sub-rules apply, and the use cases to generate.

It covers all four Article 50 duties: AI interaction (50(1)), synthetic content (50(2)), emotion recognition and biometric categorisation (50(3)), and deepfakes (50(4)). Languages: all 24 official EU languages (English, German, French, Spanish, Italian and Dutch are the maintained translations; the other 18 are first-pass and should be reviewed before you rely on them).

Related MCP server: EU AI Act Compliance MCP Server

TL;DR — install (Claude Desktop)

Add this to your Claude Desktop config (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "disclos-article-50": {
      "command": "npx",
      "args": ["-y", "github:GatisOzols/disclos-article-50"]
    }
  }
}

Restart Claude Desktop, then ask:

"I run an AI chatbot with German and French users. Give me the Article 50 disclosure I need to show them."

Claude calls article_50_disclosure and returns the label, the rules, and the HTML to paste in.

Run from source

git clone https://github.com/GatisOzols/disclos-article-50
cd disclos-article-50
npm install
npm start

Where the text comes from

All 24 EU languages are included here. The six core ones (English, German, French, Spanish, Italian, Dutch) are the maintained Disclos translations, also published in the open-source eu-ai-act-checklist. The canonical generator lives at https://www.disclos.eu/tools/article-50-disclosure-generator.

Accuracy & limits

  • The text follows the public structure of Article 50. It is a drafting aid for the common cases, accurate for most straightforward SaaS products.

  • Sensitive cases (biometric categorisation, deepfakes of real people) can cross into prohibited or high-risk territory and need a human review.

  • English, German, French, Spanish, Italian and Dutch are the maintained translations. The other 18 EU languages are first-pass and should be checked by a native speaker before you rely on them.

  • This is general information, not legal advice.

License

MIT © 2026 Gatis Ozols / Disclos. Original work, free to use, copy, modify and share.

Available Tools

2 tools
article_50_disclosureA

Generate the exact EU AI Act Article 50 transparency disclosure you must show users, for a given use case and language. Returns the visible label, where and when to show it, and a copy-paste implementation snippet. Covers chatbots (50(1)), AI-generated content (50(2)), emotion recognition and biometric categorisation (50(3)), and deepfakes (50(4)).

Inputs: use_case (required), language, company, model.

which_article_50_rules_applyA

Work out which Article 50 transparency duties apply to a product, from a few yes/no facts. Returns the relevant sub-rules and the use_case keys to feed into article_50_disclosure.

Inputs: interacts_with_users (required), generates_or_alters_content (required), deepfakes_real_subjects (required), emotion_or_biometric (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.1/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have completely distinct purposes: one identifies applicable rules, the other generates the disclosure. There is no overlap or ambiguity.

    Naming Consistency5/5

    Both tool names follow a clear, descriptive pattern using snake_case with specific nouns and verbs, making them predictable and understandable.

    Tool Count4/5

    Two tools is minimal but appropriate for the narrow domain of Article 50 compliance. It covers the essential workflow without unnecessary bloat.

    Completeness5/5

    The tool set covers the full process: first determine which rules apply, then generate the appropriate disclosure. No obvious gaps for this specific purpose.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers