MEOK Fria Generator MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| 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. |
| 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. |
| 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. |
| 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. |
| list_charter_articlesA | List EU Charter of Fundamental Rights articles relevant to AI deployer FRIA. |
| list_mandatory_triggersA | List the conditions that make a FRIA mandatory under Article 27(1). |
| pricingC | Pricing for MEOK FRIA Generator. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
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.
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.
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.
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.