meok-dora-tlpt-planner-mcp
DORA Article 26 Threat-Led Penetration Testing (TLPT) planner — TIBER-EU pathway scoping, white-team RACI, threat-intel briefing templates, and HMAC-signed compliance attestations.
By MEOK AI Labs · MIT licensed · runs as an MCP server inside Claude Code, Cursor, Cline, Windsurf, etc.
Why this exists
DORA Reg (EU) 2022/2554 Articles 26-27 require significant/systemic financial entities to conduct Threat-Led Penetration Testing (TLPT) every three years using accredited red-team providers and following the TIBER-EU framework.
Today, TLPT engagements cost €250-500K minimum (€30-80K threat-intel report + €100-500K red-team + €100-500K remediation reserve). Sub-significant institutions wanting to look ready for a regulator visit have no entry-level path.
This MCP gives you the scoping + planning layer for free, MIT-licensed, callable from any AI agent, with HMAC-signed attestations the regulator can verify cryptographically.
It does not replace an accredited red-team provider. It compresses the planning + RACI + remediation tracking phases that today eat 30-40% of TLPT consulting fees.
Tools
| Tool | Use |
|---|---|
scope_tlpt |
Generate a DORA Art. 26 scope document with phase plan, RACI, RT-provider requirements, budget tiering |
threat_intel_brief |
Produce a TIBER-EU v2.0-compliant TTI brief template to commission accredited threat-intel providers |
remediation_milestones |
90/180/365-day remediation plan with severity-mapped closure timelines (Art. 26(7)) |
signed_tlpt_attestation |
HMAC-sign your TLPT attestation via meok-attestation-api; produces verification URL |
list_phases |
List the 3 TIBER-EU phases (preparation/testing/closure) with deliverables |
pricing |
Pricing tiers (free / £79 Pro / £1,499 Enterprise / from £5K bespoke) |
Install
pip install meok-dora-tlpt-planner-mcp
Then add to your Claude Code / Cursor / Cline MCP config:
{
"mcpServers": {
"meok-dora-tlpt-planner": {
"command": "python",
"args": ["-m", "meok_dora_tlpt_planner"]
}
}
}
Example use
Inside Claude Code:
"Scope a DORA TLPT for Acme Bank N.V., a credit institution operating in DE, NL, IE. Critical functions: retail-payments, core-banking, customer-onboarding. Last TLPT was 2023-06-15. Annual budget estimate €750K."
Claude calls scope_tlpt(...), returns a structured scope doc with phase plan, RACI, RT-provider requirements, and budget tiering. You review, correct, sign with signed_tlpt_attestation(), hand to your white-team-lead.
"Generate the 90/180/365 remediation milestone plan for 47 findings: 3 critical, 11 high, 23 medium, 10 low."
Claude returns a structured milestone plan with severity-mapped closure timelines per DORA Art. 26(7).
Compliance posture
- DORA Reg (EU) 2022/2554 Art. 26-27 (TLPT)
- DORA RTS on TLPT (per Art. 26(11) — final RTS adopted 2024)
- TIBER-EU framework v2.0 (ECB, August 2023 update)
- MITRE ATT&CK Enterprise + ICS (for TTP mapping in TTI briefs)
- ICD-203 standard for attribution confidence statements
Pricing
- Free — full toolset, public attestation API (shared HMAC issuer)
- £79/mo Pro — your own HMAC signing key + custom verify domain
- £1,499/mo Enterprise — multi-BU separation for group-level coordination + SLA
- from £5,000 bespoke — self-hosted attestation API + GRC integrations + on-site training
Buy: https://meok.ai/pricing · Contact: nicholas@csoai.org
Reseller / consultancy partnership
If you're a Big 4 / boutique consultancy running TLPT engagements, MEOK has a 70/30 reseller split for the Pro tier. White-label it for your clients. Email nicholas@csoai.org with subject "TLPT reseller inquiry".
License
MIT. © 2026 Nicholas Templeman / CSOAI LTD (UK Companies House 16939677).
See also
- meok-dora-compliance-mcp — broader DORA compliance toolkit (Art. 28 register, Art. 18 incident reporting)
- meok-attestation-api — public verifiable attestation infrastructure
- Full MEOK fleet
Metadata
Release files for meok-dora-tlpt-planner-mcp 1.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| meok_dora_tlpt_planner_mcp-1.0.3.tar.gz | 12.7 kB | Without provenance | Details for meok_dora_tlpt_planner_mcp-1.0.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| meok_dora_tlpt_planner_mcp-1.0.3-py3-none-any.whl | Python 3 | none | any | Details for meok_dora_tlpt_planner_mcp-1.0.3-py3-none-any.whl |
Total release size: 24.0 kB
Release files / meok_dora_tlpt_planner_mcp-1.0.3.tar.gz
| Download URL | meok_dora_tlpt_planner_mcp-1.0.3.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ebcb542c32d74f716880cddf7e89fe18c547729630e0f938e434d00bcbb85419
|
|
BLAKE2b-256 checksum How to use checksums |
de11af430b172ce1dd0a5fa98b7c930fca5afcab2462c78c305d1ba4a5f844cf
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / meok_dora_tlpt_planner_mcp-1.0.3-py3-none-any.whl
| Download URL | meok_dora_tlpt_planner_mcp-1.0.3-py3-none-any.whl |
|---|---|
| Size | 11.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a63c5779aa107ea07934e18e715c24aadd519c154e5b3af3f3d4bd83ecf2003b
|
|
BLAKE2b-256 checksum How to use checksums |
ace345b4c1ee00fa20e27f2c3c29528ae5a81e8b1f1a92e1c9853f79d00eee60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for meok-dora-tlpt-planner-mcp 1.0.3
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.