Skip to main content
Glama

LexGrid DORA & NIS2 ICT Resilience

Server Details

DORA third-party ICT contract compliance auditor (Art. 28/30), NIS2 entity criticality classifier, and 4h/24h/72h statutory incident reporting triage.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.4/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a distinct regulatory decision point: vendor contract audit, incident materiality triage, entity classification, and TLPT scoping. Descriptions explicitly cross-reference one another with 'do NOT use for X, use Y instead' guidance, eliminating misselection risk.

Naming Consistency5/5

All names follow a consistent snake_case noun-phrase pattern of regime/topic + subject (dora_third_party_risk, nis2_criticality_classifier, tlpt_threat_led_pentest_scope, incident_severity_triage). Verb-less but uniformly so, making the pattern predictable.

Tool Count5/5

Four tools map cleanly onto four distinct DORA/NIS2 assessment pillars, with no redundancy or filler. The count is well-scoped for a focused regulatory decision-support server.

Completeness3/5

The surface covers third-party risk, incident reporting, entity classification, and TLPT, but omits major DORA areas such as the ICT risk management framework (Art 5-16), register of information submissions, and information-sharing arrangements. Core decision points are present, yet meaningful gaps remain for full DORA/NIS2 lifecycle coverage.

Publisher details

Operator
NovaPixel · Publisher source
Operator website
Not provided
Vendor relationship
Not provided
Documentation
Not provided
Privacy policy
Not provided
Trust center
Not provided
Restrictions
Not provided

Available Tools

4 tools
dora_third_party_riskDORA ICT Third-Party Contract AuditorA
Read-onlyIdempotent
Inspect

[Deterministic regulatory contract audit. Pure calculation, read-only, side-effect free]. Audits ICT third-party service provider contracts under DORA Articles 28-30: mandatory exit strategies, regulator inspection rights, EEA data processing location guarantees, subcontractor change notification windows, and 24h incident reporting clauses. Usage: Use this tool to audit ICT vendor agreements for financial institutions. For entity NIS2 classification, use 'nis2_criticality_classifier'. For cyber incident triage, use 'incident_severity_triage'. Returns: JSON object with { isCompliant: boolean, compliantClausesCount: number, missingClauses: string[], riskLevel: 'LOW' | 'MEDIUM' | 'CRITICAL', recommendations: string[] }.

Inputs: providerName (required), contractClauses (required), serviceCategory (required), isCriticalFunction (required).

incident_severity_triageMajor ICT Incident Severity TriageA
Read-onlyIdempotent
Inspect

[Deterministic cyber incident triage. Pure calculation, read-only, side-effect free]. Evaluates operational and security incidents against regulatory materiality thresholds under DORA (JC 2023 83) and NIS2 Article 23: client impact count, downtime duration, economic loss, data compromise, and cross-border Member State impact, triggering statutory 4-hour initial and 24-hour formal notification deadlines. Usage: Use this tool immediately upon discovering an ICT disruption to assess whether mandatory regulatory reporting to CSIRT/National Competent Authorities is required. Do NOT use for penetration test scoping (use 'tlpt_threat_led_pentest_scope'). Returns: JSON object with { isMajorIncident: boolean, notificationRequired: boolean, initialNotificationDeadlineHours: number, formalNotificationDeadlineHours: number, applicableRegimes: string[], triggeredCriteria: string[] }.

Inputs: affectedService (required), durationMinutes (required), incidentSummary (required), isCrossBorderEuImpact (required), +5 more.

nis2_criticality_classifierNIS2 Entity Criticality & Scope ClassifierA
Read-onlyIdempotent
Inspect

[Deterministic entity classification. Pure calculation, read-only, side-effect free]. Classifies corporate entities into 'Essential Entity' vs 'Important Entity' under Directive (EU) 2022/2555 (NIS2) based on sector, headcount FTE, and financial turnover/balance sheet thresholds, computing supervisory regime and statutory fine exposure (up to 10M€ or 2% of global turnover). Usage: Use this tool to determine corporate NIS2 scope and governance duties. For penetration testing scope under DORA, use 'tlpt_threat_led_pentest_scope'. Returns: JSON object with { entityCategory: 'ESSENTIAL' | 'IMPORTANT' | 'OUT_OF_SCOPE', supervisoryRegime: string, maxStatutoryFineEur: number, statutoryObligations: string[] }.

Inputs: sector (required), companyName (required), annualTurnoverEur (required), totalEmployeesFte (required), +2 more.

tlpt_threat_led_pentest_scopeDORA Advanced TLPT / TIBER-EU Scope AssessorA
Read-onlyIdempotent
Inspect

[Deterministic regulatory assessment. Pure calculation, read-only, side-effect free, no external state modified]. Assesses Threat-Led Penetration Testing (TLPT) mandatory obligations and scoping under DORA Articles 26-27 and Joint RTS JC 2024 15 (TIBER-EU framework). Evaluates financial sector type, balance sheet assets (≥30B€ threshold), systemically important institution (G-SII/O-SII) designation, 3-year recurring testing cadence, and required independent external tester qualifications. Usage: Use this tool specifically to determine whether a financial entity is legally mandated to conduct live red-team / TLPT penetration testing under DORA. Do NOT use for general ICT incident classification (use 'incident_severity_triage' instead) or for vendor contract audits (use 'dora_third_party_risk' instead). Returns: JSON object with { isObliged: boolean, rationale: string, recommendedFrequency: string, requiredTesterType: 'EXTERNAL_ACCREDITED' | 'INTERNAL_PERMITTED', legalBasis: string, nextTestDueBy: string | null }.

Inputs: testerType, financialSector, lastTlptTestDate, testerUtilizzati, +9 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources