Skip to main content
Glama

meok-fria-generator-mcp MCP 服务器 MCP 注册表 PyPI

meok-fria-generator-mcp MCP 服务器

meok-fria-generator-mcp

PyPI 许可证: MIT MCP

欧盟《人工智能法案》第 27 条基本权利影响评估 (FRIA) 生成器。包含 EDPB DPIA 交叉参考、欧盟基本权利宪章映射以及 HMAC 签名的合规性证明。

由 MEOK AI Labs 开发 · MIT 许可 · 可作为 MCP 服务器 在 Claude Code、Cursor、Cline、Windsurf 等工具中运行。


存在意义

欧盟《人工智能法案》条例 (EU) 2024/1689 第 27 条规定,提供公共服务的公法机构和私营运营商必须在部署高风险 AI 系统之前完成基本权利影响评估 (FRIA)。

欧盟人工智能办公室的官方 FRIA 模板尚未发布(截至 2026 年 4 月)。现有的免费工具(ALIGNER、AIActStack、kla.digital)仅为模板生成器——它们均不支持 MCP 调用,也不提供已签名的证明。

该 MCP 为合规团队提供了一个结构化、可调用且已签名的 FRIA 工作流,并对照 EDPB 统一的 DPIA 模板(2026 年 4 月 14 日)进行了映射,从而使同一套证据包能够同时满足《人工智能法案》和 GDPR 审计的要求。

Related MCP server: Encoder AI MCP

工具

工具

用途

is_fria_required

判断特定部署是否根据第 27(1) 条强制要求进行 FRIA

generate_fria_template

生成包含所有 7 个强制性第 27 条字段的结构化 FRIA 模板

map_to_edpb_dpia

交叉参考 FRIA 字段与 EDPB DPIA 部分以共享证据

signed_fria_attestation

通过 meok-attestation-api 对已完成的 FRIA 进行 HMAC 签名

list_charter_articles

与 AI 部署者 FRIA 相关的《欧盟基本权利宪章》条款

list_mandatory_triggers

触发第 27(1) 条 FRIA 义务的条件

pricing

定价层级(免费 / 79 英镑专业版 / 1,499 英镑企业版 / 5,000 英镑起定制版)

安装

pip install meok-fria-generator-mcp

然后在你的 Claude Code / Cursor MCP 配置中:

{
  "mcpServers": {
    "meok-fria-generator": {
      "command": "python",
      "args": ["-m", "meok_fria_generator"]
    }
  }
}

使用示例

“如果我们是一家在欧盟市场部署简历筛选 AI 的英国公共部门招聘服务提供商,是否强制要求进行 FRIA?附件 III 类别:就业与劳动力。”

Claude 调用 is_fria_required(...) 并返回结构化的决策:是,强制要求,因为 (a) 提供公共服务 且 (b) 属于附件 III 高风险类别。返回理由、监管依据以及截止日期(首次部署前)。

“为 Acme Public Services Ltd 的简历筛选 AI 生成 FRIA 模板。预计每年 50,000 名候选人,在德国、法国、爱尔兰部署。”

Claude 返回一个结构化模板,包含所有 7 个第 27 条字段、《欧盟基本权利宪章》条款引用、EDPB DPIA 交叉参考以及审查触发时间表。

第 27 条强制触发条件

在以下情况下,FRIA 是强制性的:

  1. 部署者是公法机构(成员国或欧盟机构)

  2. 部署者是提供公共服务的私营运营商(公共部门招聘、教育、医疗保健等)

  3. 部署的是高风险附件 III 系统

  4. 始终强制的类别(无论组织类型如何):

    • 信用评分(附件 III §5(b))

    • 人寿/健康保险定价(附件 III §5(c))

合规立场

  • 欧盟《人工智能法案》条例 (EU) 2024/1689 第 27 条(FRIA — 公共部门 + 附件 III 部署者强制要求)

  • 《欧盟基本权利宪章》(交叉引用以进行风险识别)

  • EDPB 统一 DPIA 模板(2026 年 4 月 14 日 — 用于 GDPR 第 35 条重叠部分)

  • 第 14 条(纳入 FRIA (e) 部分的人工监督要求)

定价

  • 免费 — 全套工具,公共证明 API

  • 79 英镑/月 专业版 — 你自己的 HMAC 签名密钥 + 自定义验证域名 + FRIA 版本控制

  • 1,499 英镑/月 企业版 — 多部署 FRIA 管理 + SLA + 经销商白标

  • 5,000 英镑起 定制版 — 自托管证明 + GRC 集成 + 现场研讨会

购买:https://meok.ai/pricing · 联系:nicholas@csoai.org

许可证

MIT。© 2026 Nicholas Templeman / CSOAI LTD (英国公司注册处 16939677)。

另请参阅

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