MEOK DORA Tlpt Planner 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 |
|---|---|
| scope_tlptA | Generate a DORA Article 26 TLPT scope document for a financial entity. Args: entity_name: Legal name of the financial entity (e.g., "Acme Bank N.V."). entity_type: One of credit-institution / investment-firm / insurance / pension-fund / payment-institution / e-money-institution / market-infrastructure / CCP. sector: ISIC sector code (default: credit-institution). critical_functions: List of critical/important functions to be scoped (per Art. 26(2)). E.g., ["retail-payments", "trading-platform", "customer-onboarding"]. last_tlpt_date: ISO date of last TLPT (YYYY-MM-DD) — DORA mandates 3-year cycle. annual_budget_estimate_eur: Estimated TLPT engagement budget (drives RT-provider tier). Returns: Structured scope document with phase plan, deliverables, RACI, and budget breakdown. |
| threat_intel_briefA | Generate a Targeted Threat Intelligence (TTI) brief template per ECB TIBER-EU v2.0. This is a SCAFFOLD. Real TTI must be authored by an accredited threat-intel provider with current intelligence feeds. Use this template to brief them. Args: entity_name: Legal name of the financial entity. entity_sector: One of retail-banking, wholesale-banking, insurance, asset-management, market-infrastructure, payments, e-money. geographic_footprint: List of country codes where entity operates (e.g., ["DE", "NL", "IE"]). critical_functions: List of critical functions for which threats must be modelled. Returns: TTI template with sections aligned to TIBER-EU + ECB standards. |
| remediation_milestonesA | Generate a 90/180/365-day remediation milestone plan based on TLPT findings. Args: findings_count: Total number of findings from the red-team report. severity_distribution: Dict with keys 'critical', 'high', 'medium', 'low' and counts. Returns: Milestone plan with required closure timelines per severity. |
| signed_tlpt_attestationA | Produce an HMAC-signed TLPT attestation via the public meok-attestation-api. Args: entity_name: Legal name of the financial entity. scope_summary: 1-3 sentence summary of test scope. test_phase: One of preparation / testing / closure. findings_summary: Dict with findings_count, severity_distribution, and summary text. signing_role: Role of the signer (default white-team-lead). Returns: Signed attestation with verification URL. |
| list_phasesA | List the 3 TIBER-EU TLPT phases with deliverables. |
| pricingC | Pricing for MEOK DORA TLPT Planner. |
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 6 tools
Each tool targets a distinct purpose: listing phases, pricing, remediation milestones, scope document generation, signed attestation, and threat intel brief. No overlap in functionality, making selection unambiguous.
Names use snake_case but mix verb_noun (list_phases, signed_tlpt_attestation) with plain nouns (pricing, remediation_milestones, scope_tlpt, threat_intel_brief). While readable, the pattern is inconsistent.
With 6 tools, the server covers the key planning activities for DORA TLPT without being bloated or sparse. Each tool contributes meaningfully to the planner's purpose.
The set covers phases, pricing, remediation, scope, attestation, and threat intel scaffolding. A minor gap is the lack of a tool to input findings automatically, but the remediation_milestones tool accepts that data, so the core workflow is intact.