meok-fria-generator-mcp
EU AI Act Article 27 Fundamental Rights Impact Assessment (FRIA) generator. EDPB DPIA crosswalk, EU Charter of Fundamental Rights mapping, HMAC-signed compliance attestations.
By MEOK AI Labs · MIT licensed · runs as an MCP server inside Claude Code, Cursor, Cline, Windsurf, etc.
Why this exists
EU AI Act Reg (EU) 2024/1689 Article 27 mandates that public-law bodies and private operators providing public services complete a Fundamental Rights Impact Assessment before deploying a high-risk AI system.
The official EU AI Office FRIA template is not yet published (April 2026). Existing free tools (ALIGNER, AIActStack, kla.digital) are template generators — none are MCP-callable, none ship signed attestations.
This MCP gives compliance teams a structured, callable, signed-FRIA workflow today, mapped against the EDPB harmonised DPIA template (14 April 2026) so the same evidence pack satisfies both AI Act and GDPR auditors.
Tools
| Tool | Use |
|---|---|
is_fria_required |
Decide if FRIA is mandatory under Article 27(1) for a given deployment |
generate_fria_template |
Produce a structured FRIA template with all 7 mandatory Article 27 fields |
map_to_edpb_dpia |
Crosswalk FRIA fields ↔ EDPB DPIA sections to share evidence |
signed_fria_attestation |
HMAC-sign your completed FRIA via meok-attestation-api |
list_charter_articles |
EU Charter of Fundamental Rights articles relevant to AI deployer FRIA |
list_mandatory_triggers |
Conditions that trigger Article 27(1) FRIA obligation |
pricing |
Pricing tiers (free / £79 Pro / £1,499 Enterprise / from £5K bespoke) |
Install
pip install meok-fria-generator-mcp
Then in your Claude Code / Cursor MCP config:
{
"mcpServers": {
"meok-fria-generator": {
"command": "python",
"args": ["-m", "meok_fria_generator"]
}
}
}
Example use
"Is a FRIA mandatory if we're a UK public-sector recruitment provider deploying a CV-screening AI in EU markets? Annex III categories: employment-and-workforce."
Claude calls is_fria_required(...) and returns a structured decision: YES, mandatory because (a) provides-public-service AND (b) Annex III high-risk category. Returns the rationale, the regulatory basis, and the deadline (before first deployment).
"Generate a FRIA template for Acme Public Services Ltd's CV-screening AI. Expected 50,000 candidates/year, deployed in DE, FR, IE."
Claude returns a structured template with all 7 Article 27 fields, EU Charter article references, EDPB DPIA crosswalk, and review-trigger schedule.
Article 27 mandatory triggers
FRIA is mandatory when:
- The deployer is a body governed by public law (Member State or EU institution)
- The deployer is a private operator providing public services (recruitment for public sector, education, healthcare, etc.)
- The deployment is a high-risk Annex III system
- Always-mandatory categories (regardless of organisation type):
- Credit scoring (Annex III §5(b))
- Life/health insurance pricing (Annex III §5(c))
Compliance posture
- EU AI Act Reg (EU) 2024/1689 Article 27 (FRIA — mandatory for public-sector + Annex III deployers)
- EU Charter of Fundamental Rights (cross-referenced for risk identification)
- EDPB Harmonised DPIA Template (14 April 2026 — for GDPR Article 35 overlap)
- Article 14 (human oversight requirements feeding into FRIA section (e))
Pricing
- Free — full toolset, public attestation API
- £79/mo Pro — your own HMAC signing key + custom verify domain + FRIA versioning
- £1,499/mo Enterprise — multi-deployment FRIA management + SLA + reseller white-label
- from £5,000 bespoke — self-hosted attestation + GRC integrations + on-site workshop
Buy: https://meok.ai/pricing · Contact: nicholas@csoai.org
License
MIT. © 2026 Nicholas Templeman / CSOAI LTD (UK Companies House 16939677).
See also
- meok-eu-ai-act-compliance-mcp — broader EU AI Act compliance toolkit
- meok-dpia-edpb-template-mcp — EDPB harmonised DPIA template
- meok-attestation-api — public verifiable attestation infrastructure
Metadata
Release files for meok-fria-generator-mcp 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| meok_fria_generator_mcp-1.0.3.tar.gz | 12.3 kB | Without provenance | Details for meok_fria_generator_mcp-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| meok_fria_generator_mcp-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for meok_fria_generator_mcp-1.0.3-py3-none-any.whl |
Total release size: 23.4 kB
Release files / meok_fria_generator_mcp-1.0.3.tar.gz
| Download URL | meok_fria_generator_mcp-1.0.3.tar.gz |
|---|---|
| Size | 12.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c7654f6c3774ecaf7f55c8c9fd11dfd9ffd1ca8c424bd3991f2f42ef3e98ce63
|
|
BLAKE2b-256 checksum How to use checksums |
04df2dc021497382c8d0b280bdbe3fb58e1821edfb82cd08f74c63b6621b4c7c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / meok_fria_generator_mcp-1.0.3-py3-none-any.whl
| Download URL | meok_fria_generator_mcp-1.0.3-py3-none-any.whl |
|---|---|
| Size | 11.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9cf8e10536cb8462095f486c90f0375a5e0f899b60ff1061526800a701c221f1
|
|
BLAKE2b-256 checksum How to use checksums |
64e861769b14cec674143afcf18265a5c3e9b8640e2067cea0c922a4c0f52529
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for meok-fria-generator-mcp 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.