Skip to main content
Glama

Meok Fria Generator MCP

MEOK AI Labs EU AI Act License PyPI

EU AI Act Article 27 FRIA generator β€” EDPB DPIA crosswalk, EU Charter mapping, HMAC-signed compli...

EU AI Act Article 27 FRIA generator β€” EDPB DPIA crosswalk, EU Charter mapping, HMAC-signed compliance attestations. By MEOK AI Labs.


πŸš€ Quick Start

# Install via pip
pip install meok_fria_generator_mcp

# Or install via Smithery
npx -y @smithery/cli@latest install meok-fria-generator-mcp --client claude

Related MCP server: Encoder AI MCP

✨ Features

  • MCP protocol compliant

  • Easy installation

  • Well-documented API

  • Production-ready

  • Active maintenance

πŸ“– Documentation

πŸ›‘οΈ Compliance

This MCP server is built with EU AI Act compliance built-in:

  • βœ… Article 9 β€” Risk Management System

  • βœ… Article 13 β€” Transparency & Instructions for Use

  • βœ… Article 15 β€” Bias Detection & Testing

  • βœ… Article 26 β€” FRIA Support (where applicable)

  • βœ… Article 50 β€” AI Content Watermarking (where applicable)

Need help getting compliant? Book a free 15-min diagnostic β†’

🏒 Enterprise

Need custom development, SLA guarantees, or white-label deployment?

  • Pro: $99/mo β€” Full MCP suite + EU AI Act tracking

  • Enterprise: $499/mo β€” Custom dev + SLA + Dedicated support

View Pricing β†’ | Contact Sales β†’

🀝 Part of the MEOK Ecosystem

This server is part of the MEOK AI Labs ecosystem β€” 300+ MCP servers for sovereign AI governance.

Domain

Purpose

councilof.ai

EU AI Act compliance marketplace

safetyof.ai

AI safety & monitoring

meok.ai

Sovereign AI platform

cobolbridge.ai

Legacy modernization

πŸ“œ License

MIT Β© CSOAI-ORG


Available Tools

7 tools
generate_fria_templateA

Generate a FRIA template structure with all 7 mandatory Article 27 fields populated as guidance.

Args: deployer_name: Legal name of the deployer (e.g., "Acme Hiring Ltd"). ai_system_name: Name of the AI system being deployed. annex_iii_category: Annex III category (e.g., "employment-and-workforce"). expected_users: Estimated count of natural persons whose data will be processed. geographic_scope: List of country codes (e.g., ["DE", "FR", "IE"]).

Returns: Structured FRIA template ready for completion by the deployer's compliance team.

Inputs: deployer_name (required), ai_system_name (required), annex_iii_category (required), expected_users, +1 more. Returns: object

is_fria_requiredA

Determine if a FRIA is mandatory under EU AI Act Article 27 for this deployment.

Args: organisation_type: One of public-authority / private-operator / SaaS-vendor / individual. is_public_law_body: True if the organisation is a body governed by Member State or EU public law. provides_public_service: True if the organisation provides services in a public-service context (recruitment for public sector, education, healthcare, social services, etc.). annex_iii_categories: List of Annex III high-risk categories the system falls under. E.g., ["employment-and-workforce", "education-and-vocational-training", "credit-scoring"].

Returns: Decision + rationale + Article 27 reference.

Inputs: organisation_type (required), is_public_law_body, provides_public_service, annex_iii_categories. Returns: object

list_charter_articlesA

List EU Charter of Fundamental Rights articles relevant to AI deployer FRIA.

Inputs: no named parameters. Returns: object

list_mandatory_triggersA

List the conditions that make a FRIA mandatory under Article 27(1).

Inputs: no named parameters. Returns: object

map_to_edpb_dpiaA

Map FRIA fields to EDPB harmonised DPIA template (14 April 2026) sections to avoid double work.

Args: annex_iii_category: Annex III category for context.

Returns: Crosswalk showing which FRIA fields satisfy which DPIA sections.

Inputs: annex_iii_category (required). Returns: object

pricingC

Pricing for MEOK FRIA Generator.

Inputs: no named parameters. Returns: object

signed_fria_attestationB

Produce an HMAC-signed FRIA attestation via the public meok-attestation-api.

Args: deployer_name: Legal name of the deployer. ai_system_name: Name of the AI system. annex_iii_category: Annex III category. completed_sections: List of FRIA section IDs that have been completed (e.g., ["a_deployer_processes", "b_period_frequency_use"]). sign_off_role: Role of the signer.

Returns: Signed attestation with verification URL.

Inputs: deployer_name (required), ai_system_name (required), annex_iii_category (required), completed_sections (required), +1 mor… Returns: object

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: checking FRIA requirement, generating template, listing charter articles, listing triggers, mapping to DPIA, pricing, and signing attestation. There is no overlap or ambiguity.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (generate_fria_template, list_charter_articles, etc.), but 'pricing' and 'signed_fria_attestation' are nouns, deviating from the pattern. Overall, the naming is clear and predictable despite these minor inconsistencies.

    Tool Count5/5

    Seven tools is ideal for this specialized domain. Each tool provides a distinct function without unnecessary redundancy, and the count is neither too few nor too many for the scope of FRIA generation and associated compliance tasks.

    Completeness4/5

    The tool set covers the core FRIA workflow: determination, template generation, supporting information (charter articles, triggers), DPIA integration, pricing, and attestation. A minor gap is lack of tools for managing previously generated templates or attestations, but this aligns with the generator-focused design.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers