Skip to main content
Glama
disclos-eu-ai-act
by GatisOzols

disclos-eu-ai-act

An MCP server that lets AI assistants (Claude Desktop, Claude Code, Cursor, Windsurf, and any MCP-compatible client) classify an AI system under the EU AI Act — Regulation (EU) 2024/1689.

Ask your assistant a plain-English question and it returns a structured scope finding: the risk tier, the obligations, and the deadlines.

Built and maintained by Disclos — fixed-price EU AI Act audits for SaaS companies.


What it does

Four tools:

Tool

What it returns

classify_ai_system

A full scope finding — tier, obligations, deadline, and the exact EUR-Lex article — from a description of the product.

eu_ai_act_timeline

The enforcement timeline (Feb 2025 → Aug 2028) and what takes effect on each date.

explain_tier

A detailed explanation of one risk tier and its duties.

framework_crosswalk

Maps an EU AI Act tier to the equivalent controls in ISO/IEC 42001, NIST AI RMF, and GDPR.

It tests every tier the Act defines: prohibited (Art 5), high-risk (Annex III), GPAI provider (Art 53), transparency (Art 50), minimal, and out of scope — flags the common mistake of over-classifying as high-risk, and links every finding to the official EUR-Lex text.

Related MCP server: Legalithm

TL;DR — 60-second install (Claude Desktop)

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

{
  "mcpServers": {
    "disclos-eu-ai-act": {
      "command": "npx",
      "args": ["-y", "github:GatisOzols/disclos-eu-ai-act"]
    }
  }
}

Restart Claude Desktop, then ask:

"We run a B2B SaaS with an AI chatbot and some EU customers. Are we in scope under the EU AI Act, and at what tier?"

Claude calls classify_ai_system and returns a finding with the tier, obligations, and the relevant deadline.

Run from source

git clone https://github.com/GatisOzols/disclos-eu-ai-act
cd disclos-eu-ai-act
npm install
npm start            # starts the server on stdio

Then point any MCP client at node /path/to/src/index.js.

How it works

A small, deterministic classifier maps six yes/no facts about your product to the Act's tiers. No network calls, no data collection, no tracking — everything runs locally on stdio.

Accuracy & limits

  • The logic follows the public text of Articles 5, 6, 50, 53 and Annex III.

  • It's a screening aid, accurate for most straightforward SaaS products.

  • Edge cases (multi-modal systems, mixed provider/deployer roles, biometric inference) need a human review.

  • This is general information, not legal advice.

License

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

Available Tools

4 tools
classify_ai_systemA

Classify an AI system or product under the EU AI Act (Regulation (EU) 2024/1689) and return its risk tier, obligations and deadlines. Map the user's description to the boolean flags below. When unsure, ask the user or choose the more cautious answer. Returns a structured 'scope finding'.

Inputs: eu_exposure (required), has_ai_feature (required), annex_iii_high_risk (required), prohibited_practice (required), +3 more.

eu_ai_act_timelineA

Return the EU AI Act enforcement timeline — the key dates and what takes effect on each.

Inputs: no named parameters.

explain_tierA

Explain a single EU AI Act risk tier in detail: what it means, the obligations, and the deadline.

Inputs: tier (required).

framework_crosswalkA

Map an EU AI Act risk tier to the equivalent controls in adjacent governance frameworks — ISO/IEC 42001, NIST AI RMF, and GDPR. Use when the user asks how the EU AI Act lines up with ISO 42001, NIST, GDPR, or their existing compliance program.

Inputs: tier (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 4 tools

    Disambiguation4/5

    The tools are mostly distinct: classify_ai_system maps user input to a risk tier, explain_tier describes a known tier, while timeline and crosswalk serve clear reference purposes. There is slight overlap between classify_ai_system and explain_tier (both return obligations and deadlines), but their primary functions differ enough to avoid confusion.

    Naming Consistency3/5

    All names use snake_case, but the pattern is mixed: classify_ai_system and explain_tier are verb_noun, while eu_ai_act_timeline and framework_crosswalk are noun phrases. The inconsistency in starting part (verb vs. noun) makes the set slightly less predictable.

    Tool Count5/5

    Four tools is well-scoped for an information-focused EU AI Act server. Each tool covers a specific high-level user need without redundancy, and the count is neither too thin nor excessive.

    Completeness4/5

    The set covers classification, timeline, tier explanations, and cross-framework mapping, which addresses common compliance questions. Minor gaps exist (e.g., no tool for searching specific legal provisions or compliance checklists), but the core workflows are covered and agents can work around these gaps.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables EU AI Act compliance assessment by classifying AI systems, listing obligations, computing deadlines, and scanning repos for required documentation, all running locally.
      4
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Provides an AI agent with regulatory compliance tools for the French/European market based on the AI Act and GDPR, including system classification, obligation listing, deadline schedules, legal reference lookup, and GDPR crosschecks.
      -