list_overlapping_obligationsLABSCO SUMMARY
The gap between two regimes, not a summary of either.
Single-regime checklists are everywhere; what a dual-scope entity actually needs is the difference — where one control satisfies both, and where two clocks start ticking on the same incident. The reporting-clock comparison is the tool worth having open during an incident, not after it.
What it is
A Python server that maps DORA against NIS2 for organisations in scope for both. The repository puts the overlap at 65% of obligations, which is the whole reason the server exists: most of the work is shared, and the parts that aren't are where people get caught.
What you get
Three tools, named in the repository's own examples: list_overlapping_obligations for what both regimes ask of you, compare_reporting_clocks for the incident-notification deadlines that differ between them, and check_dual_compliance for the combined position.
Requirements
pip install dora_nis2_crosswalk_mcp, or point your client at uvx with the argument dora-nis2-crosswalk-mcp (package version 1.1.5, stdio transport). MIT-licensed.
Setup effort
One command — pip install dora_nis2_crosswalk_mcp
USE CASES
01
Not doing the same control twice
List the obligations both regimes share before planning the work.
02
Knowing which deadline hits first after an incident
Compare the two notification clocks side by side.
03
Stating a combined compliance position
Check both regimes at once rather than reconciling two reports.
3 tools
Listed in project docs. Your client may show a different list.
compare_reporting_clockscheck_dual_complianceBEFORE YOU INSTALL
What to know first
Tools you get
3 tools named in the project's documentation.
Requires
uvx on PATH
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
pip install dora_nis2_crosswalk_mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"dora-nis2-crosswalk-mcp": {
"command": "uvx",
"args": [
"dora-nis2-crosswalk-mcp"
]
}
}
}
