Local MCP capabilities provider for Expo
ClevSec EU compliance tools is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Deterministic, sourced EU compliance checks: NIS2, DORA, GDPR, Cyber Resilience Act and AI Act.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http clevsec-eu-compliance-tools-mcp https://mcp.clevsec.one/mcp
# 2 — ask your agent for something these tools do
# reporting_deadlines, nis2_scope_check, nis2_gap_assessment and 25 more
ClevSec EU compliance tools costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http clevsec-eu-compliance-tools-mcp https://mcp.clevsec.one/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
28 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| regimes | array | no | Limit to these regimes; omit for all |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| sector | string | no | The Annex I or II sector of the entity's activity; omit if none applies |
| staff_headcount | number | yes | Staff in annual work units, including partner and linked enterprises |
| annual_turnover_eur | number | no | — |
| balance_sheet_total_eur | number | no | — |
| provider_type | string | no | Special provider types covered regardless of size (Art. 2(2)(a), 2(4)) |
| public_administration | string | no | — |
| national_security_or_law_enforcement | boolean | no | Public administration working in national security, public security, defence or law enforcement (Art. 2(7)) |
| designated_by_member_state | boolean | no | Identified by the member state under Art. 2(2)(b)-(e) |
| critical_entity_under_cer | boolean | no | Identified as a critical entity under Directive (EU) 2022/2557 |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | no | Question id to answer, e.g. {"g1": "yes", "r2": "partial"}. Omit to get the questions. Unanswered questions count as gaps. |
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,
| Parameter | Type | Required | Notes |
|---|---|---|---|
| affects_critical_or_important_functions | boolean | no | ICT services or systems supporting critical or important functions are affected (Art. 6(a)) |
| affects_authorised_or_supervised_services | boolean | no | Financial services requiring authorisation or registration, or supervised, are affected (Art. 6(b)) |
| successful_malicious_unauthorised_access | boolean | no | A successful, malicious and unauthorised access to network and information systems occurred that may result in data losses (Arts. 6(c), 9(5)(b)) |
| affected_clients_percent | number | no | Affected clients as % of all clients using the affected service |
| affected_clients_count | integer | no | — |
| affected_counterparts_percent | number | no | Affected financial counterparts as % of those active in the affected service |
| affected_transactions_number_percent | number | no | Affected transactions as % of the daily average number for the service |
| affected_transactions_value_percent | number | no | Affected transaction amount as % of the daily average value for the service |
| relevant_clients_or_counterparts_affected | boolean | no | Clients or counterparts identified as relevant under Art. 1(3) are affected |
| reputational_impact | boolean | no | Media coverage, repetitive complaints, likely failure to meet regulatory requirements, or likely loss of clients with material impact (Art. 2) |
| duration_hours | number | no | — |
| critical_service_downtime_hours | number | no | Downtime of ICT services supporting critical or important functions |
| member_states_with_impact | integer | no | — |
| data_impact_adverse | boolean | no | Impact on availability, authenticity, integrity or confidentiality of data that harms business objectives or regulatory compliance (Art. 9(5)(a)) |
| costs_and_losses_eur | number | no | Direct and indirect costs and losses per Art. 7, without financial recoveries |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| microenterprise | boolean | no | The financial entity is a microenterprise (DORA Art. 3(60)) |
| simplified_framework | boolean | no | The entity is listed in DORA Art. 16(1) and uses the simplified framework |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | no | Question id to answer, e.g. {"p1_1": "yes", "p2_3": "partial"}. Unanswered questions count as gaps. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| role | string | no | Controller decides why and how data are processed; a processor acts on its behalf |
| risk | string | yes | 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 consequen |
| hours_since_aware | number | no | Hours since the controller had a reasonable degree of certainty that a breach occurred |
| data_unintelligible | boolean | no | The affected data were unintelligible to unauthorised people, e.g. state-of-the-art encryption with the key not compromised |
| subsequent_measures_remove_high_risk | boolean | no | Measures taken since then ensure the high risk is no longer likely to materialise |
| individual_contact_disproportionate | boolean | no | Contacting each person would involve disproportionate effort, e.g. no contact details |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| annual_turnover_eur | number | yes | Total worldwide annual turnover of the undertaking in the preceding financial year, in EUR |
| infringement_tier | string | yes | 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 |
| seriousness | string | no | Seriousness per EDPB Guidelines 04/2022 para. 60; omit to have it suggested from the facts below |
| people_affected | integer | no | — |
| data_categories | array | no | basic contact data, financial, other personal (e.g. location), special categories (Art. 9), children's data, criminal data (Art. 10) |
| duration | string | no | short: under a month; medium: 1 to 12 months; long: over a year |
| fault | string | no | low: measures in place but one failed; clear: a known risk not addressed; intent: intentional or against advice |
| damage | string | no | — |
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, accountability, international transfers), each with its article. Call with the ids done (and optional items not applicable) to get the co
| Parameter | Type | Required | Notes |
|---|---|---|---|
| done | array | no | Ids of the items already in place |
| not_applicable | array | no | Ids of optional items that do not apply (only items marked optional) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| t1 | string | 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 | 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 convictio |
| t3 | string | no | Will you systematically monitor a publicly accessible area on a large scale (for example CCTV in shops, stations or streets)? |
| t4 | string | no | Is this type of processing on your supervisory authority's published list of operations that require a DPIA? |
| c1 | string | no | Does the processing evaluate or score people (profiling or predicting their performance, finances, health, preferences, reliability, behaviour or location)? |
| c2 | string | no | Does it involve automated decisions with legal or similarly significant effects (for example access to credit, a job or a service)? |
| c3 | string | no | Does it involve systematic monitoring of people (for example online tracking, employee monitoring or CCTV)? |
| c4 | string | no | Does it involve sensitive or highly personal data (special category or criminal data, financial data, location data or private communications)? |
| c5 | string | 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 | no | Does it combine or match datasets from different sources in ways people would not expect? |
| c7 | string | no | Does it concern vulnerable people (children, employees, patients, the elderly, or others in an unequal relationship with you)? |
| c8 | string | no | Does it use innovative technology or a new way of using existing technology (for example AI, biometrics or IoT)? |
| c9 | string | 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)? |
| x1 | string | no | Will personal data be transferred outside the EU/EEA (including remote access from outside the EEA)? |
| proj_data | array | no | Categories of personal data |
| proj_subjects | array | no | Categories of data subjects |
| proj_legal | string | no | Legal basis for processing |
| nec1 | string | no | Is the processing necessary to achieve the stated purpose, or could the purpose be achieved with less data? |
| nec2 | string | no | Is the amount of data collected proportionate to the purpose? |
| nec3 | string | no | Is the retention period limited to what is necessary? |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| source | string | no | data_subject: collected from the person (forms, accounts, cookies); other_source: from third parties, public sources or data brokers |
| has_dpo | boolean | no | A data protection officer is appointed |
| relies_on_legitimate_interests | boolean | no | — |
| relies_on_consent | boolean | no | — |
| transfers_outside_eea | boolean | no | — |
| automated_decisions | boolean | no | Solely automated decisions with legal or similarly significant effects, including profiling (Art. 22) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flows | array | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | no | Item id to answer, e.g. {"c1": "yes", "c3": "partial"}. Unanswered items count as gaps. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | yes | actively_exploited_vulnerability: reliable evidence that a malicious actor exploited it; severe_incident: an incident affecting the product's security |
| is_manufacturer | boolean | no | 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 | no | 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 prod |
| affects_data_or_functions_protection | boolean | no | 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 |
| malicious_code | boolean | no | Severe incident test, Art. 14(5)(b): it led or can lead to malicious code in the product or in users' systems |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | no | Control question id to status, e.g. {"o1": "implemented", "t3": "planned"}. Unanswered controls count as gaps. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendorType | string | no | Type of service |
| dataAccess | array | no | What data will this vendor access? |
| criticality | string | no | How critical is this vendor to your operations? |
| regimes | array | no | Which of these apply to your organization? (optional) |
| sec1 | string | no | Does the vendor hold relevant security certifications (ISO 27001, SOC 2, etc.)? |
| sec2 | string | no | Does the vendor have a documented information security policy? |
| sec3 | string | no | Does the vendor encrypt data at rest and in transit? |
| sec4 | string | no | Does the vendor enforce multi-factor authentication? |
| sec5 | string | no | Does the vendor conduct regular penetration testing? |
| sec6 | string | no | Does the vendor have a vulnerability management program? |
| sec7 | string | no | Does the vendor perform background checks on employees with data access? |
| inc1 | string | no | Does the vendor have a documented incident response plan? |
| inc2 | string | no | Will the vendor notify you of security incidents within 24-48 hours? |
| inc3 | string | no | Has the vendor experienced any data breaches in the last 3 years? |
| inc4 | string | no | Does the vendor conduct incident response exercises/tabletop tests? |
| com1 | string | no | Is the vendor compliant with GDPR (if processing EU personal data)? |
| com2 | string | no | Will the vendor sign a Data Processing Agreement? |
| com3 | string | no | Does the vendor provide right-to-audit or access to audit reports? |
| com4 | string | no | Does the vendor's contract include security requirements and SLAs? |
| com5 | string | no | Does the vendor have adequate insurance coverage (cyber liability)? |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | no | Question id to maturity level 1-5, e.g. {"gv1": 2, "id1": 3}. Unanswered questions count as level 1. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | no | Question id to answer, e.g. {"q1": "yes", "q4": "partial"}. Unanswered questions score zero. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | yes | Question id to answer, e.g. {"g1": "yes", "r2": "partial"}. Omit to get the questions. Unanswered questions count as gaps. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | yes | Question id to answer, e.g. {"p1_1": "yes", "p2_3": "partial"}. Unanswered questions count as gaps. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| done | array | no | Ids of the items already in place |
| not_applicable | array | no | Ids of optional items that do not apply (only items marked optional) |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| t1 | string | 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 | 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 convictio |
| t3 | string | no | Will you systematically monitor a publicly accessible area on a large scale (for example CCTV in shops, stations or streets)? |
| t4 | string | no | Is this type of processing on your supervisory authority's published list of operations that require a DPIA? |
| c1 | string | no | Does the processing evaluate or score people (profiling or predicting their performance, finances, health, preferences, reliability, behaviour or location)? |
| c2 | string | no | Does it involve automated decisions with legal or similarly significant effects (for example access to credit, a job or a service)? |
| c3 | string | no | Does it involve systematic monitoring of people (for example online tracking, employee monitoring or CCTV)? |
| c4 | string | no | Does it involve sensitive or highly personal data (special category or criminal data, financial data, location data or private communications)? |
| c5 | string | 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 | no | Does it combine or match datasets from different sources in ways people would not expect? |
| c7 | string | no | Does it concern vulnerable people (children, employees, patients, the elderly, or others in an unequal relationship with you)? |
| c8 | string | no | Does it use innovative technology or a new way of using existing technology (for example AI, biometrics or IoT)? |
| c9 | string | 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)? |
| x1 | string | no | Will personal data be transferred outside the EU/EEA (including remote access from outside the EEA)? |
| proj_data | array | no | Categories of personal data |
| proj_subjects | array | no | Categories of data subjects |
| proj_legal | string | no | Legal basis for processing |
| nec1 | string | no | Is the processing necessary to achieve the stated purpose, or could the purpose be achieved with less data? |
| nec2 | string | no | Is the amount of data collected proportionate to the purpose? |
| nec3 | string | no | Is the retention period limited to what is necessary? |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| flows | array | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | yes | Item id to answer, e.g. {"c1": "yes", "c3": "partial"}. Unanswered items count as gaps. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | yes | Control question id to status, e.g. {"o1": "implemented", "t3": "planned"}. Unanswered controls count as gaps. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| vendorType | string | no | Type of service |
| dataAccess | array | no | What data will this vendor access? |
| criticality | string | no | How critical is this vendor to your operations? |
| regimes | array | no | Which of these apply to your organization? (optional) |
| sec1 | string | no | Does the vendor hold relevant security certifications (ISO 27001, SOC 2, etc.)? |
| sec2 | string | no | Does the vendor have a documented information security policy? |
| sec3 | string | no | Does the vendor encrypt data at rest and in transit? |
| sec4 | string | no | Does the vendor enforce multi-factor authentication? |
| sec5 | string | no | Does the vendor conduct regular penetration testing? |
| sec6 | string | no | Does the vendor have a vulnerability management program? |
| sec7 | string | no | Does the vendor perform background checks on employees with data access? |
| inc1 | string | no | Does the vendor have a documented incident response plan? |
| inc2 | string | no | Will the vendor notify you of security incidents within 24-48 hours? |
| inc3 | string | no | Has the vendor experienced any data breaches in the last 3 years? |
| inc4 | string | no | Does the vendor conduct incident response exercises/tabletop tests? |
| com1 | string | no | Is the vendor compliant with GDPR (if processing EU personal data)? |
| com2 | string | no | Will the vendor sign a Data Processing Agreement? |
| com3 | string | no | Does the vendor provide right-to-audit or access to audit reports? |
| com4 | string | no | Does the vendor's contract include security requirements and SLAs? |
| com5 | string | no | Does the vendor have adequate insurance coverage (cyber liability)? |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | yes | Question id to maturity level 1-5, e.g. {"gv1": 2, "id1": 3}. Unanswered questions count as level 1. |
| target_level | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | yes | Question id to answer, e.g. {"q1": "yes", "q4": "partial"}. Unanswered questions score zero. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install ClevSec EU compliance tools or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| reporting_deadlines | no tags | |
| nis2_scope_check | no tags | |
| nis2_gap_assessment | no tags | |
| dora_classify_incident | no tags | |
| dora_checklist | no tags | |
| dora_gap_assessment | no tags | |
| gdpr_breach_decision | no tags | |
| gdpr_fine_estimate | no tags | |
| gdpr_checklist_assessment | no tags | |
| gdpr_dpia_screening | no tags | |
| privacy_notice_requirements | no tags | |
| data_flow_record_check | no tags | |
| cookie_consent_check | no tags | |
| cra_reporting_check | no tags | |
| iso27001_gap_assessment | no tags | |
| vendor_risk_assessment | no tags | |
| maturity_assessment | no tags | |
| cyber_risk_score | no tags | |
| nis2_remediation_plan | no tags | |
| dora_remediation_plan | no tags | |
| gdpr_remediation_plan | no tags | |
| gdpr_dpia_report | no tags | |
| data_flow_review | no tags | |
| cookie_consent_fix_plan | no tags | |
| iso27001_remediation_plan | no tags | |
| vendor_due_diligence_plan | no tags | |
| maturity_improvement_plan | no tags | |
| cyber_risk_action_plan | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.5.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish ClevSec EU compliance tools can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.