one.clevsec/eu-compliance

Est-ce que one.clevsec/eu-compliance est sûr ?

Au dernier audit MCP Hub, le serveur MCP « one.clevsec/eu-compliance » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 28 outils

• cookie_consent_check≈ 205 tokens

  Use when someone asks whether their cookie banner or cookie consent is compliant in the EU (ePrivacy Art. 5(3) and GDPR consent rules). Call without answers to get the checklist items by area, critical ones marked. Call with yes, partial or no per item to get a score, a compliance label and the open items.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · optionnel
    Item id to answer, e.g. {"c1": "yes", "c3": "partial"}. Unanswered items count as gaps.

  Exemple d'appel

  {"name": "cookie_consent_check", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cookie_consent_fix_plan≈ 192 tokens

  Use after cookie_consent_check when the user wants to fix their cookie consent. Returns every open item with the fix, its legal source (ePrivacy, GDPR, CJEU Planet49, EDPB) and a 30/60/90-day roadmap. Requires ClevSec Pro.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · requis
    Item id to answer, e.g. {"c1": "yes", "c3": "partial"}. Unanswered items count as gaps.

  Exemple d'appel

  {"name": "cookie_consent_fix_plan", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cra_reporting_check≈ 484 tokens

  Use when a manufacturer of hardware or software sold in the EU learns of an actively exploited vulnerability or a security incident in its product. Applies Art. 14 of the Cyber Resilience Act (Regulation (EU) 2024/2847), in force since 11 September 2026: whether a report is due, the 24-hour, 72-hour and final report deadlines, where to report, and informing users.

  Paramètres, retour & exemple (5)

  Paramètres

  • event · string · requis · actively_exploited_vulnerability | severe_incident
    actively_exploited_vulnerability: reliable evidence that a malicious actor exploited it; severe_incident: an incident affecting the product's security
  • malicious_code · boolean · optionnel
    Severe incident test, Art. 14(5)(b): it led or can lead to malicious code in the product or in users' systems
  • is_manufacturer · boolean · optionnel
    Develops or manufactures the product, or has it designed or made, and markets it under its own name or trademark
  • product_with_digital_elements · boolean · optionnel
    Software or hardware product (and its remote data processing) made available in the EU whose intended or foreseeable use includes a data connection to a device or network (Arts. 2(1), 3(1)); some products under sector laws, such as medical devices and vehicles, are excluded (Art. 2(2)-(4))
  • affects_data_or_functions_protection · boolean · optionnel
    Severe incident test, Art. 14(5)(a): it harms or can harm the product's ability to protect the availability, authenticity, integrity or confidentiality of sensitive or important data or functions

  Exemple d'appel

  {"name": "cra_reporting_check", "arguments": {"event": "actively_exploited_vulnerability"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cyber_risk_action_plan≈ 206 tokens

  Use after cyber_risk_score when the user wants to reduce their risk. Returns every gap with a recommended action, a priority, NIST CSF 2.0 and NIS2 references and a 30/60/90-day roadmap (MFA, encryption, patching, incident response and backups first). Requires ClevSec Pro.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · requis
    Question id to answer, e.g. {"q1": "yes", "q4": "partial"}. Unanswered questions score zero.

  Exemple d'appel

  {"name": "cyber_risk_action_plan", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• cyber_risk_score≈ 212 tokens

  Use for a quick view of a small organisation's cyber risk ('how secure are we?', 'what is our cyber risk score?'). Call without answers to get 15 weighted questions on access, data, systems, people, incident response and backups. Call with yes, partial or no per question to get a 0-100 score, a risk level and a score per category.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · optionnel
    Question id to answer, e.g. {"q1": "yes", "q4": "partial"}. Unanswered questions score zero.

  Exemple d'appel

  {"name": "cyber_risk_score", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• data_flow_record_check≈ 539 tokens

  Use when someone maps personal data flows or builds GDPR records of processing activities (ROPA, Art. 30). Give the flows (name, purpose, data categories, recipients, legal basis, retention, transfers); returns, per flow, what an Art. 30 record still lacks, plus the allowed values for categories, legal bases and safeguards.

  Paramètres, retour & exemple (1)

  Paramètres

  • flows · array · requis

  Exemple d'appel

  {"name": "data_flow_record_check", "arguments": {"flows": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• data_flow_review≈ 543 tokens

  Use after data_flow_record_check for a compliance review of each personal data flow: legal basis, special category and children's data, consent and legitimate interest records, retention, international transfer tools and transfer impact assessments, and DPIA need, with an action, GDPR article and 30/60/90-day roadmap. Requires ClevSec Pro.

  Paramètres, retour & exemple (1)

  Paramètres

  • flows · array · requis

  Exemple d'appel

  {"name": "data_flow_review", "arguments": {"flows": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dora_checklist≈ 223 tokens

  Use for 'what does DORA require?', DORA compliance checklists or gap reviews. Returns the core DORA (Regulation (EU) 2022/2554) requirements for financial entities, grouped by section with the article for each, leaving out those that DORA itself disapplies for microenterprises or for entities under the simplified ICT risk management framework of Art. 16.

  Paramètres, retour & exemple (2)

  Paramètres

  • microenterprise · boolean · optionnel
    The financial entity is a microenterprise (DORA Art. 3(60))
  • simplified_framework · boolean · optionnel
    The entity is listed in DORA Art. 16(1) and uses the simplified framework

  Exemple d'appel

  {"name": "dora_checklist", "arguments": {"microenterprise": true, "simplified_framework": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dora_classify_incident≈ 776 tokens

  Use when a bank, insurer, investment firm, payment or crypto-asset firm or other financial entity has an IT outage, cyber attack or data incident and asks whether it must be reported under DORA. Classifies the ICT-related incident as major or not under DORA, applying the criteria and materiality thresholds of Commission Delegated Regulation (EU) 2024/1772 (Arts. 6, 8 and 9). Returns the decision, which criteria are met, and the reporting time limits if major. Leave out what you do not know.

  Paramètres, retour & exemple (15)

  Paramètres

  • duration_hours · number · optionnel
  • data_impact_adverse · boolean · optionnel
    Impact on availability, authenticity, integrity or confidentiality of data that harms business objectives or regulatory compliance (Art. 9(5)(a))
  • reputational_impact · boolean · optionnel
    Media coverage, repetitive complaints, likely failure to meet regulatory requirements, or likely loss of clients with material impact (Art. 2)
  • costs_and_losses_eur · number · optionnel
    Direct and indirect costs and losses per Art. 7, without financial recoveries
  • affected_clients_count · integer · optionnel
  • affected_clients_percent · number · optionnel
    Affected clients as % of all clients using the affected service
  • member_states_with_impact · integer · optionnel
  • affected_counterparts_percent · number · optionnel
    Affected financial counterparts as % of those active in the affected service
  • critical_service_downtime_hours · number · optionnel
    Downtime of ICT services supporting critical or important functions
  • affected_transactions_value_percent · number · optionnel
    Affected transaction amount as % of the daily average value for the service
  • affected_transactions_number_percent · number · optionnel
    Affected transactions as % of the daily average number for the service
  • affects_critical_or_important_functions · boolean · optionnel
    ICT services or systems supporting critical or important functions are affected (Art. 6(a))
  • successful_malicious_unauthorised_access · boolean · optionnel
    A successful, malicious and unauthorised access to network and information systems occurred that may result in data losses (Arts. 6(c), 9(5)(b))
  • affects_authorised_or_supervised_services · boolean · optionnel
    Financial services requiring authorisation or registration, or supervised, are affected (Art. 6(b))
  • relevant_clients_or_counterparts_affected · boolean · optionnel
    Clients or counterparts identified as relevant under Art. 1(3) are affected

  Exemple d'appel

  {"name": "dora_classify_incident", "arguments": {"duration_hours": 1, "data_impact_adverse": true, "reputational_impact": true, "costs_and_losses_eur": 1, "affected_clients_count": 1, "affected_clients_percent": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dora_gap_assessment≈ 229 tokens

  Use to assess how ready a financial entity is for DORA, or to find its gaps. Call without answers to get the 39 questions in five pillars (ICT risk management, incident management, resilience testing, ICT third-party risk, information sharing), each with its DORA article. Call with answers (yes, partial, no per question id) to get a score per pillar, an overall readiness level and the gaps.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · optionnel
    Question id to answer, e.g. {"p1_1": "yes", "p2_3": "partial"}. Unanswered questions count as gaps.

  Exemple d'appel

  {"name": "dora_gap_assessment", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• dora_remediation_plan≈ 208 tokens

  Use after dora_gap_assessment when the user wants a plan to close their DORA gaps. Turns the same answers into every gap with a recommended action, a priority, the DORA article and a 30/60/90-day roadmap (ICT risk management and incident management first). Requires ClevSec Pro.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · requis
    Question id to answer, e.g. {"p1_1": "yes", "p2_3": "partial"}. Unanswered questions count as gaps.

  Exemple d'appel

  {"name": "dora_remediation_plan", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gdpr_breach_decision≈ 463 tokens

  Use when a personal data breach has happened (data lost, stolen, sent to the wrong person, encrypted by ransomware, accessed without authorisation) to decide whether the GDPR requires notifying the supervisory authority within 72 hours (Art. 33) and the people affected (Art. 34), applying the exceptions. Needs the risk level of the breach: unlikely, risk or high.

  Paramètres, retour & exemple (6)

  Paramètres

  • risk · string · requis · unlikely | risk | high
    Likely risk to people's rights and freedoms (EDPB Guidelines 9/2022): consider the type of breach, the sensitivity and volume of the data, how easily people can be identified, how severe the consequences are, and vulnerable people such as children
  • role · string · optionnel · controller | processor
    Controller decides why and how data are processed; a processor acts on its behalf
  • hours_since_aware · number · optionnel
    Hours since the controller had a reasonable degree of certainty that a breach occurred
  • data_unintelligible · boolean · optionnel
    The affected data were unintelligible to unauthorised people, e.g. state-of-the-art encryption with the key not compromised
  • individual_contact_disproportionate · boolean · optionnel
    Contacting each person would involve disproportionate effort, e.g. no contact details
  • subsequent_measures_remove_high_risk · boolean · optionnel
    Measures taken since then ensure the high risk is no longer likely to materialise

  Exemple d'appel

  {"name": "gdpr_breach_decision", "arguments": {"risk": "unlikely"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gdpr_checklist_assessment≈ 243 tokens

  Use to check how far an organisation is with GDPR compliance, or to list what GDPR requires in practice. Call without input to get the 48 checklist items in 8 areas (lawfulness, transparency and rights, minimisation and retention, security, breaches, processors and transfers, accountability), each with its article. Call with the ids done (and optional items not applicable) to get the completion score and the open items.

  Paramètres, retour & exemple (2)

  Paramètres

  • done · array · optionnel
    Ids of the items already in place
  • not_applicable · array · optionnel
    Ids of optional items that do not apply (only items marked optional)

  Exemple d'appel

  {"name": "gdpr_checklist_assessment", "arguments": {"done": [], "not_applicable": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gdpr_dpia_report≈ 2184 tokens

  Use after gdpr_dpia_screening when the user needs the DPIA worked out: a risk register linking each high or medium risk to its measures with coverage and indicative residual risk, and every gap (legal basis, special category data, necessity, missing measures, transfers, prior consultation under Art. 36) with an action, priority, article and a 30/60/90-day roadmap. Requires ClevSec Pro.

  Paramètres, retour & exemple (46)

  Paramètres

  • c1 · string · optionnel · yes | no
    Does the processing evaluate or score people (profiling or predicting their performance, finances, health, preferences, reliability, behaviour or location)?
  • c2 · string · optionnel · yes | no
    Does it involve automated decisions with legal or similarly significant effects (for example access to credit, a job or a service)?
  • c3 · string · optionnel · yes | no
    Does it involve systematic monitoring of people (for example online tracking, employee monitoring or CCTV)?
  • c4 · string · optionnel · yes | no
    Does it involve sensitive or highly personal data (special category or criminal data, financial data, location data or private communications)?
  • c5 · string · optionnel · yes | no
    Is the processing large-scale (many people, a large volume or range of data, a long duration or a wide geographic area)?
  • c6 · string · optionnel · yes | no
    Does it combine or match datasets from different sources in ways people would not expect?
  • c7 · string · optionnel · yes | no
    Does it concern vulnerable people (children, employees, patients, the elderly, or others in an unequal relationship with you)?
  • c8 · string · optionnel · yes | no
    Does it use innovative technology or a new way of using existing technology (for example AI, biometrics or IoT)?
  • c9 · string · optionnel · yes | no
    Could the processing itself prevent people from exercising a right or using a service or contract (for example credit screening that decides whether to offer a loan)?
  • m1 · string · optionnel · yes | partial | no
    Encryption of personal data at rest and in transit
  • m2 · string · optionnel · yes | partial | no
    Pseudonymization or anonymization where possible
  • m3 · string · optionnel · yes | partial | no
    Access controls limiting who can view/modify the data
  • m4 · string · optionnel · yes | partial | no
    Regular security testing (vulnerability scans, penetration tests)
  • m5 · string · optionnel · yes | partial | no
    Staff training on data protection for those handling the data
  • m6 · string · optionnel · yes | partial | no
    Data minimization — collecting only what is strictly necessary
  • m7 · string · optionnel · yes | partial | no
    Automated deletion at end of retention period
  • m8 · string · optionnel · yes | partial | no
    Incident response plan covering this processing activity
  • m9 · string · optionnel · yes | partial | no
    Regular audits or reviews of the processing activity
  • r1 · string · optionnel · high | medium | low
    Risk of unauthorized access to personal data (data breach)
  • r2 · string · optionnel · high | medium | low
    Risk of data being used for purposes beyond what was communicated
  • r3 · string · optionnel · high | medium | low
    Risk of inaccurate data leading to wrong decisions about individuals
  • r4 · string · optionnel · high | medium | low
    Risk of excessive data collection beyond what is needed
  • r5 · string · optionnel · high | medium | low
    Risk of insufficient transparency — individuals unaware of processing
  • r6 · string · optionnel · high | medium | low
    Risk of discrimination or unfair treatment based on the processing
  • r7 · string · optionnel · high | medium | low
    Risk of financial loss or economic disadvantage to individuals
  • r8 · string · optionnel · high | medium | low
    Risk of reputational damage or social disadvantage to individuals
  • r9 · string · optionnel · high | medium | low
    Risk of physical harm or safety concerns
  • t1 · string · optionnel · yes | no
    Will you systematically and extensively evaluate people by automated means (including profiling), and base decisions on it that have legal or similarly significant effects on them?
  • t2 · string · optionnel · yes | no
    Will you process special category data (health, biometric, genetic, racial or ethnic origin, political opinions, religion, trade union membership, sex life or sexual orientation) or criminal conviction data on a large scale?
  • t3 · string · optionnel · yes | no
    Will you systematically monitor a publicly accessible area on a large scale (for example CCTV in shops, stations or streets)?
  • t4 · string · optionnel · yes | no
    Is this type of processing on your supervisory authority's published list of operations that require a DPIA?
  • x1 · string · optionnel · yes | no
    Will personal data be transferred outside the EU/EEA (including remote access from outside the EEA)?
  • m10 · string · optionnel · yes | partial | no
    Data Processing Agreements with all third-party processors
  • m11 · string · optionnel · yes | partial | no
    Privacy by design principles applied in system architecture
  • m12 · string · optionnel · yes | partial | no
    Mechanism for data subjects to exercise their rights easily
  • r10 · string · optionnel · high | medium | low
    Risk of loss of confidentiality (e.g. medical or legal privilege)
  • nec1 · string · optionnel · yes | partial | no
    Is the processing necessary to achieve the stated purpose, or could the purpose be achieved with less data?
  • nec2 · string · optionnel · yes | partial | no
    Is the amount of data collected proportionate to the purpose?
  • nec3 · string · optionnel · yes | partial | no
    Is the retention period limited to what is necessary?
  • nec4 · string · optionnel · yes | partial | no
    Are data subjects adequately informed about the processing (transparency)?
  • nec5 · string · optionnel · yes | partial | no
    Can data subjects exercise their rights (access, rectification, erasure, portability)?
  • nec6 · string · optionnel · yes | partial | no
    If relying on consent, is it freely given, specific, informed, and withdrawable?
  • nec7 · string · optionnel · yes | partial | no
    If relying on legitimate interest, has a balancing test been conducted?
  • proj_data · array · optionnel
    Categories of personal data
  • proj_legal · string · optionnel · Consent (Art. 6(1)(a)) | Contract (Art. 6(1)(b)) | Legal obligation (Art. 6(1)(c)) | Vital interests (Art. 6(1)(d)) | Public interest (Art. 6(1)(e)) | Legitimate interest (Art. 6(1)(f)) | Not yet determined
    Legal basis for processing
  • proj_subjects · array · optionnel
    Categories of data subjects

  Exemple d'appel

  {"name": "gdpr_dpia_report", "arguments": {"c1": "yes", "c2": "yes", "c3": "yes", "c4": "yes", "c5": "yes", "c6": "yes"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gdpr_dpia_screening≈ 2185 tokens

  Use when someone plans new processing of personal data (a new system, AI use, monitoring, profiling) and asks whether a data protection impact assessment is required or how risky it is. Applies GDPR Art. 35(3), national lists and the nine WP248 rev.01 criteria, scores necessity and mitigation, and gives an indicative residual risk. Call without input to get the questions; every input is optional.

  Paramètres, retour & exemple (46)

  Paramètres

  • c1 · string · optionnel · yes | no
    Does the processing evaluate or score people (profiling or predicting their performance, finances, health, preferences, reliability, behaviour or location)?
  • c2 · string · optionnel · yes | no
    Does it involve automated decisions with legal or similarly significant effects (for example access to credit, a job or a service)?
  • c3 · string · optionnel · yes | no
    Does it involve systematic monitoring of people (for example online tracking, employee monitoring or CCTV)?
  • c4 · string · optionnel · yes | no
    Does it involve sensitive or highly personal data (special category or criminal data, financial data, location data or private communications)?
  • c5 · string · optionnel · yes | no
    Is the processing large-scale (many people, a large volume or range of data, a long duration or a wide geographic area)?
  • c6 · string · optionnel · yes | no
    Does it combine or match datasets from different sources in ways people would not expect?
  • c7 · string · optionnel · yes | no
    Does it concern vulnerable people (children, employees, patients, the elderly, or others in an unequal relationship with you)?
  • c8 · string · optionnel · yes | no
    Does it use innovative technology or a new way of using existing technology (for example AI, biometrics or IoT)?
  • c9 · string · optionnel · yes | no
    Could the processing itself prevent people from exercising a right or using a service or contract (for example credit screening that decides whether to offer a loan)?
  • m1 · string · optionnel · yes | partial | no
    Encryption of personal data at rest and in transit
  • m2 · string · optionnel · yes | partial | no
    Pseudonymization or anonymization where possible
  • m3 · string · optionnel · yes | partial | no
    Access controls limiting who can view/modify the data
  • m4 · string · optionnel · yes | partial | no
    Regular security testing (vulnerability scans, penetration tests)
  • m5 · string · optionnel · yes | partial | no
    Staff training on data protection for those handling the data
  • m6 · string · optionnel · yes | partial | no
    Data minimization — collecting only what is strictly necessary
  • m7 · string · optionnel · yes | partial | no
    Automated deletion at end of retention period
  • m8 · string · optionnel · yes | partial | no
    Incident response plan covering this processing activity
  • m9 · string · optionnel · yes | partial | no
    Regular audits or reviews of the processing activity
  • r1 · string · optionnel · high | medium | low
    Risk of unauthorized access to personal data (data breach)
  • r2 · string · optionnel · high | medium | low
    Risk of data being used for purposes beyond what was communicated
  • r3 · string · optionnel · high | medium | low
    Risk of inaccurate data leading to wrong decisions about individuals
  • r4 · string · optionnel · high | medium | low
    Risk of excessive data collection beyond what is needed
  • r5 · string · optionnel · high | medium | low
    Risk of insufficient transparency — individuals unaware of processing
  • r6 · string · optionnel · high | medium | low
    Risk of discrimination or unfair treatment based on the processing
  • r7 · string · optionnel · high | medium | low
    Risk of financial loss or economic disadvantage to individuals
  • r8 · string · optionnel · high | medium | low
    Risk of reputational damage or social disadvantage to individuals
  • r9 · string · optionnel · high | medium | low
    Risk of physical harm or safety concerns
  • t1 · string · optionnel · yes | no
    Will you systematically and extensively evaluate people by automated means (including profiling), and base decisions on it that have legal or similarly significant effects on them?
  • t2 · string · optionnel · yes | no
    Will you process special category data (health, biometric, genetic, racial or ethnic origin, political opinions, religion, trade union membership, sex life or sexual orientation) or criminal conviction data on a large scale?
  • t3 · string · optionnel · yes | no
    Will you systematically monitor a publicly accessible area on a large scale (for example CCTV in shops, stations or streets)?
  • t4 · string · optionnel · yes | no
    Is this type of processing on your supervisory authority's published list of operations that require a DPIA?
  • x1 · string · optionnel · yes | no
    Will personal data be transferred outside the EU/EEA (including remote access from outside the EEA)?
  • m10 · string · optionnel · yes | partial | no
    Data Processing Agreements with all third-party processors
  • m11 · string · optionnel · yes | partial | no
    Privacy by design principles applied in system architecture
  • m12 · string · optionnel · yes | partial | no
    Mechanism for data subjects to exercise their rights easily
  • r10 · string · optionnel · high | medium | low
    Risk of loss of confidentiality (e.g. medical or legal privilege)
  • nec1 · string · optionnel · yes | partial | no
    Is the processing necessary to achieve the stated purpose, or could the purpose be achieved with less data?
  • nec2 · string · optionnel · yes | partial | no
    Is the amount of data collected proportionate to the purpose?
  • nec3 · string · optionnel · yes | partial | no
    Is the retention period limited to what is necessary?
  • nec4 · string · optionnel · yes | partial | no
    Are data subjects adequately informed about the processing (transparency)?
  • nec5 · string · optionnel · yes | partial | no
    Can data subjects exercise their rights (access, rectification, erasure, portability)?
  • nec6 · string · optionnel · yes | partial | no
    If relying on consent, is it freely given, specific, informed, and withdrawable?
  • nec7 · string · optionnel · yes | partial | no
    If relying on legitimate interest, has a balancing test been conducted?
  • proj_data · array · optionnel
    Categories of personal data
  • proj_legal · string · optionnel · Consent (Art. 6(1)(a)) | Contract (Art. 6(1)(b)) | Legal obligation (Art. 6(1)(c)) | Vital interests (Art. 6(1)(d)) | Public interest (Art. 6(1)(e)) | Legitimate interest (Art. 6(1)(f)) | Not yet determined
    Legal basis for processing
  • proj_subjects · array · optionnel
    Categories of data subjects

  Exemple d'appel

  {"name": "gdpr_dpia_screening", "arguments": {"c1": "yes", "c2": "yes", "c3": "yes", "c4": "yes", "c5": "yes", "c6": "yes"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gdpr_fine_estimate≈ 531 tokens

  Use for 'how big could a GDPR fine be?' or 'how are GDPR fines calculated?'. Applies step 2 of the EDPB Guidelines 04/2022 method: the Art. 83(4) or 83(5) legal maximum, the starting amount band for the seriousness of the infringement, and the turnover adjustment. Give the seriousness, or the facts to let ClevSec suggest it. Returns a starting range in EUR, not a prediction of a real fine.

  Paramètres, retour & exemple (8)

  Paramètres

  • fault · string · optionnel · low | clear | intent
    low: measures in place but one failed; clear: a known risk not addressed; intent: intentional or against advice
  • damage · string · optionnel · limited | significant | severe
  • duration · string · optionnel · short | medium | long
    short: under a month; medium: 1 to 12 months; long: over a year
  • seriousness · string · optionnel · low | medium | high
    Seriousness per EDPB Guidelines 04/2022 para. 60; omit to have it suggested from the facts below
  • data_categories · array · optionnel
    basic contact data, financial, other personal (e.g. location), special categories (Art. 9), children's data, criminal data (Art. 10)
  • people_affected · integer · optionnel
  • infringement_tier · string · requis · 83(4) | 83(5)
    83(4): controller/processor obligations such as security (Art. 32) and breach notification (Arts. 33-34). 83(5): principles, legal basis, data subject rights, transfers
  • annual_turnover_eur · number · requis
    Total worldwide annual turnover of the undertaking in the preceding financial year, in EUR

  Exemple d'appel

  {"name": "gdpr_fine_estimate", "arguments": {"infringement_tier": "83(4)", "annual_turnover_eur": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• gdpr_remediation_plan≈ 215 tokens

  Use after gdpr_checklist_assessment when the user wants a plan to close their GDPR gaps. Turns the same input into every open item with a recommended action, a priority, the GDPR article and a 30/60/90-day roadmap (lawfulness, records, breach handling and processor contracts first). Requires ClevSec Pro.

  Paramètres, retour & exemple (2)

  Paramètres

  • done · array · optionnel
    Ids of the items already in place
  • not_applicable · array · optionnel
    Ids of optional items that do not apply (only items marked optional)

  Exemple d'appel

  {"name": "gdpr_remediation_plan", "arguments": {"done": [], "not_applicable": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• iso27001_gap_assessment≈ 241 tokens

  Use to check how close an organisation is to ISO/IEC 27001:2022 certification, or to list the Annex A controls in practice. Call without answers to get 41 control checks in four themes (organizational, people, physical, technological) with their Annex A references. Call with a status per control (implemented, partial, planned, not_impl) to get a score per theme, a readiness level and the gaps.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · optionnel
    Control question id to status, e.g. {"o1": "implemented", "t3": "planned"}. Unanswered controls count as gaps.

  Exemple d'appel

  {"name": "iso27001_gap_assessment", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• iso27001_remediation_plan≈ 219 tokens

  Use after iso27001_gap_assessment when the user wants a plan towards ISO/IEC 27001 certification. Turns the same statuses into every gap with a recommended action, a priority, the Annex A control and a 30/60/90-day roadmap (organizational controls first). Requires ClevSec Pro.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · requis
    Control question id to status, e.g. {"o1": "implemented", "t3": "planned"}. Unanswered controls count as gaps.

  Exemple d'appel

  {"name": "iso27001_remediation_plan", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• maturity_assessment≈ 204 tokens

  Use to measure an organisation's cybersecurity maturity or to benchmark it against NIST CSF 2.0. Call without answers to get 39 capabilities in the six CSF functions and the 1-5 levels. Call with a level per capability to get the average per function and an overall maturity level.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · optionnel
    Question id to maturity level 1-5, e.g. {"gv1": 2, "id1": 3}. Unanswered questions count as level 1.

  Exemple d'appel

  {"name": "maturity_assessment", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• maturity_improvement_plan≈ 222 tokens

  Use after maturity_assessment when the user wants to raise their maturity. Lists every capability below the target level (3 or 4) with the next action, NIST CSF 2.0 subcategory, NIS2 article and a 30/60/90-day roadmap (govern and identify first). Requires ClevSec Pro.

  Paramètres, retour & exemple (2)

  Paramètres

  • answers · object · requis
    Question id to maturity level 1-5, e.g. {"gv1": 2, "id1": 3}. Unanswered questions count as level 1.
  • target_level · integer · optionnel · 3 | 4

  Exemple d'appel

  {"name": "maturity_improvement_plan", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• nis2_gap_assessment≈ 246 tokens

  Use to assess how ready an organisation is for NIS2 cybersecurity requirements, or to find its gaps. Call without answers to get the 53 questions in nine domains (governance, risk, incidents, continuity, supply chain, network security, vulnerabilities, training, cryptography), each mapped to NIS2 Arts. 20, 21 or 23. Call with answers (yes, partial, no per question id) to get a score per domain, an overall readiness level and the gaps.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · optionnel
    Question id to answer, e.g. {"g1": "yes", "r2": "partial"}. Omit to get the questions. Unanswered questions count as gaps.

  Exemple d'appel

  {"name": "nis2_gap_assessment", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• nis2_remediation_plan≈ 212 tokens

  Use after nis2_gap_assessment when the user wants a plan to close their NIS2 gaps. Turns the same answers into every gap with a recommended action, a priority, the NIS2 article and a 30/60/90-day roadmap (governance, risk and incident gaps first). Requires ClevSec Pro.

  Paramètres, retour & exemple (1)

  Paramètres

  • answers · object · requis
    Question id to answer, e.g. {"g1": "yes", "r2": "partial"}. Omit to get the questions. Unanswered questions count as gaps.

  Exemple d'appel

  {"name": "nis2_remediation_plan", "arguments": {"answers": {}}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• nis2_scope_check≈ 618 tokens

  Use for questions like 'does NIS2 apply to my company?', 'are we an essential or important entity?' or 'is a company of this size and sector in scope?'. Indicates whether the NIS2 Directive applies to an organisation and in which category (essential or important), from its sector, size and type, applying Arts. 2 and 3 of Directive (EU) 2022/2555 and the size rule of Recommendation 2003/361/EC. An indication only: national law and the member state's list decide.

  Paramètres, retour & exemple (9)

  Paramètres

  • sector · string · optionnel · Energy | Transport | Banking | Financial market infrastructures | Health | Drinking water | Waste water | Digital infrastructure
    The Annex I or II sector of the entity's activity; omit if none applies
  • provider_type · string · optionnel · none | public_electronic_communications | qualified_trust_service | non_qualified_trust_service | tld_registry | dns_service | domain_name_registration
    Special provider types covered regardless of size (Art. 2(2)(a), 2(4))
  • staff_headcount · number · requis
    Staff in annual work units, including partner and linked enterprises
  • annual_turnover_eur · number · optionnel
  • public_administration · string · optionnel · none | central_government | regional | local
  • balance_sheet_total_eur · number · optionnel
  • critical_entity_under_cer · boolean · optionnel
    Identified as a critical entity under Directive (EU) 2022/2557
  • designated_by_member_state · boolean · optionnel
    Identified by the member state under Art. 2(2)(b)-(e)
  • national_security_or_law_enforcement · boolean · optionnel
    Public administration working in national security, public security, defence or law enforcement (Art. 2(7))

  Exemple d'appel

  {"name": "nis2_scope_check", "arguments": {"staff_headcount": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• privacy_notice_requirements≈ 311 tokens

  Use when writing or checking a privacy policy or privacy notice. Lists every item the GDPR requires with its article, for data collected from the person (Art. 13) or obtained from other sources (Art. 14), when the notice must be given, and the exceptions. Tell it which situations apply to drop items you do not need.

  Paramètres, retour & exemple (6)

  Paramètres

  • source · string · optionnel · data_subject | other_source
    data_subject: collected from the person (forms, accounts, cookies); other_source: from third parties, public sources or data brokers
  • has_dpo · boolean · optionnel
    A data protection officer is appointed
  • relies_on_consent · boolean · optionnel
  • automated_decisions · boolean · optionnel
    Solely automated decisions with legal or similarly significant effects, including profiling (Art. 22)
  • transfers_outside_eea · boolean · optionnel
  • relies_on_legitimate_interests · boolean · optionnel

  Exemple d'appel

  {"name": "privacy_notice_requirements", "arguments": {"source": "data_subject", "has_dpo": true, "relies_on_consent": true, "automated_decisions": true, "transfers_outside_eea": true, "relies_on_legitimate_interests": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• reporting_deadlines≈ 232 tokens

  Use for any question about incident or breach reporting deadlines in the EU (for example 'how long do we have to report a breach / a cyber incident?'). Lists who must report what, to whom and by when under GDPR (personal data breaches), NIS2 (significant incidents), DORA (major ICT-related incidents at financial entities) and the Cyber Resilience Act (actively exploited vulnerabilities and severe incidents), with the article for each deadline and when the clock starts.

  Paramètres, retour & exemple (1)

  Paramètres

  • regimes · array · optionnel
    Limit to these regimes; omit for all

  Exemple d'appel

  {"name": "reporting_deadlines", "arguments": {"regimes": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• vendor_due_diligence_plan≈ 1351 tokens

  Use after vendor_risk_assessment when the user needs to act on a vendor's gaps. Returns every gap with an action, the evidence to request from the vendor, ISO 27001 / GDPR / NIS2 / DORA references and a roadmap (before signing first), plus the contract clauses to include (GDPR Art. 28, NIS2 Art. 21, DORA Art. 30 when they apply). Requires ClevSec Pro.

  Paramètres, retour & exemple (29)

  Paramètres

  • bcp1 · string · optionnel · yes | partial | no | unknown
    Does the vendor have a business continuity / disaster recovery plan?
  • bcp2 · string · optionnel · yes | partial | no | unknown
    Does the vendor offer a defined SLA with uptime guarantees?
  • bcp3 · string · optionnel · yes | partial | no | unknown
    Can data be exported/migrated if you terminate the relationship?
  • bcp4 · string · optionnel · yes | partial | no | unknown
    Does the vendor have geographic redundancy for critical services?
  • bcp5 · string · optionnel · yes | partial | no | unknown
    Is the vendor financially stable (no signs of distress)?
  • com1 · string · optionnel · yes | partial | no | unknown
    Is the vendor compliant with GDPR (if processing EU personal data)?
  • com2 · string · optionnel · yes | partial | no | unknown
    Will the vendor sign a Data Processing Agreement?
  • com3 · string · optionnel · yes | partial | no | unknown
    Does the vendor provide right-to-audit or access to audit reports?
  • com4 · string · optionnel · yes | partial | no | unknown
    Does the vendor's contract include security requirements and SLAs?
  • com5 · string · optionnel · yes | partial | no | unknown
    Does the vendor have adequate insurance coverage (cyber liability)?
  • inc1 · string · optionnel · yes | partial | no | unknown
    Does the vendor have a documented incident response plan?
  • inc2 · string · optionnel · yes | partial | no | unknown
    Will the vendor notify you of security incidents within 24-48 hours?
  • inc3 · string · optionnel · yes | partial | no | unknown
    Has the vendor experienced any data breaches in the last 3 years?
  • inc4 · string · optionnel · yes | partial | no | unknown
    Does the vendor conduct incident response exercises/tabletop tests?
  • sec1 · string · optionnel · yes | partial | no | unknown
    Does the vendor hold relevant security certifications (ISO 27001, SOC 2, etc.)?
  • sec2 · string · optionnel · yes | partial | no | unknown
    Does the vendor have a documented information security policy?
  • sec3 · string · optionnel · yes | partial | no | unknown
    Does the vendor encrypt data at rest and in transit?
  • sec4 · string · optionnel · yes | partial | no | unknown
    Does the vendor enforce multi-factor authentication?
  • sec5 · string · optionnel · yes | partial | no | unknown
    Does the vendor conduct regular penetration testing?
  • sec6 · string · optionnel · yes | partial | no | unknown
    Does the vendor have a vulnerability management program?
  • sec7 · string · optionnel · yes | partial | no | unknown
    Does the vendor perform background checks on employees with data access?
  • sup1 · string · optionnel · yes | partial | no | unknown
    Does the vendor disclose its key subprocessors/subcontractors?
  • sup2 · string · optionnel · yes | partial | no | unknown
    Will the vendor notify you before changing subprocessors?
  • sup3 · string · optionnel · yes | partial | no | unknown
    Does the vendor assess the security of its own suppliers?
  • sup4 · string · optionnel · yes | partial | no | unknown
    Are subprocessor contracts held to the same security standards?
  • regimes · array · optionnel
    Which of these apply to your organization? (optional)
  • dataAccess · array · optionnel
    What data will this vendor access?
  • vendorType · string · optionnel · SaaS / Cloud Service | Infrastructure (IaaS/PaaS) | Managed IT Services | Consulting / Professional Services | Software Vendor | Hardware Supplier | Outsourced Business Process | Other
    Type of service
  • criticality · string · optionnel · Critical — essential service, no easy replacement | Important — significant impact if disrupted | Standard — limited impact, easily replaceable
    How critical is this vendor to your operations?

  Exemple d'appel

  {"name": "vendor_due_diligence_plan", "arguments": {"bcp1": "yes", "bcp2": "yes", "bcp3": "yes", "bcp4": "yes", "bcp5": "yes", "com1": "yes"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• vendor_risk_assessment≈ 1350 tokens

  Use when an organisation evaluates a supplier, SaaS or ICT provider (vendor due diligence, third-party risk, supply chain security under NIS2 Art. 21(2)(d) or DORA). Call without input to get the questions. Call with the vendor profile (type, criticality, data access, regimes) and answers (yes, partial, no, unknown) to get a risk score, risk level, monitoring tier and the gaps.

  Paramètres, retour & exemple (29)

  Paramètres

  • bcp1 · string · optionnel · yes | partial | no | unknown
    Does the vendor have a business continuity / disaster recovery plan?
  • bcp2 · string · optionnel · yes | partial | no | unknown
    Does the vendor offer a defined SLA with uptime guarantees?
  • bcp3 · string · optionnel · yes | partial | no | unknown
    Can data be exported/migrated if you terminate the relationship?
  • bcp4 · string · optionnel · yes | partial | no | unknown
    Does the vendor have geographic redundancy for critical services?
  • bcp5 · string · optionnel · yes | partial | no | unknown
    Is the vendor financially stable (no signs of distress)?
  • com1 · string · optionnel · yes | partial | no | unknown
    Is the vendor compliant with GDPR (if processing EU personal data)?
  • com2 · string · optionnel · yes | partial | no | unknown
    Will the vendor sign a Data Processing Agreement?
  • com3 · string · optionnel · yes | partial | no | unknown
    Does the vendor provide right-to-audit or access to audit reports?
  • com4 · string · optionnel · yes | partial | no | unknown
    Does the vendor's contract include security requirements and SLAs?
  • com5 · string · optionnel · yes | partial | no | unknown
    Does the vendor have adequate insurance coverage (cyber liability)?
  • inc1 · string · optionnel · yes | partial | no | unknown
    Does the vendor have a documented incident response plan?
  • inc2 · string · optionnel · yes | partial | no | unknown
    Will the vendor notify you of security incidents within 24-48 hours?
  • inc3 · string · optionnel · yes | partial | no | unknown
    Has the vendor experienced any data breaches in the last 3 years?
  • inc4 · string · optionnel · yes | partial | no | unknown
    Does the vendor conduct incident response exercises/tabletop tests?
  • sec1 · string · optionnel · yes | partial | no | unknown
    Does the vendor hold relevant security certifications (ISO 27001, SOC 2, etc.)?
  • sec2 · string · optionnel · yes | partial | no | unknown
    Does the vendor have a documented information security policy?
  • sec3 · string · optionnel · yes | partial | no | unknown
    Does the vendor encrypt data at rest and in transit?
  • sec4 · string · optionnel · yes | partial | no | unknown
    Does the vendor enforce multi-factor authentication?
  • sec5 · string · optionnel · yes | partial | no | unknown
    Does the vendor conduct regular penetration testing?
  • sec6 · string · optionnel · yes | partial | no | unknown
    Does the vendor have a vulnerability management program?
  • sec7 · string · optionnel · yes | partial | no | unknown
    Does the vendor perform background checks on employees with data access?
  • sup1 · string · optionnel · yes | partial | no | unknown
    Does the vendor disclose its key subprocessors/subcontractors?
  • sup2 · string · optionnel · yes | partial | no | unknown
    Will the vendor notify you before changing subprocessors?
  • sup3 · string · optionnel · yes | partial | no | unknown
    Does the vendor assess the security of its own suppliers?
  • sup4 · string · optionnel · yes | partial | no | unknown
    Are subprocessor contracts held to the same security standards?
  • regimes · array · optionnel
    Which of these apply to your organization? (optional)
  • dataAccess · array · optionnel
    What data will this vendor access?
  • vendorType · string · optionnel · SaaS / Cloud Service | Infrastructure (IaaS/PaaS) | Managed IT Services | Consulting / Professional Services | Software Vendor | Hardware Supplier | Outsourced Business Process | Other
    Type of service
  • criticality · string · optionnel · Critical — essential service, no easy replacement | Important — significant impact if disrupted | Standard — limited impact, easily replaceable
    How critical is this vendor to your operations?

  Exemple d'appel

  {"name": "vendor_risk_assessment", "arguments": {"bcp1": "yes", "bcp2": "yes", "bcp3": "yes", "bcp4": "yes", "bcp5": "yes", "com1": "yes"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.clevsec.one/mcp