Moltline RegClock
Incident-reporting deadlines from the legal text — EU CRA, NIS2, DORA, GDPR, UK GDPR, HIPAA and SEC 8-K — with citations, business-day and bank-holiday rules, a statutory classifier and calendar export.
CONNECT • Endpoint: https://mcp.moltlinestudio.com/regclock (MCP Streamable HTTP) • Claude Code: claude mcp add --transport http moltline-regclock https://mcp.moltlinestudio.com/regclock • Cursor, Codex CLI and any other Streamable HTTP client take the same URL unchanged • Free tools need no account and no API key; every tool description says FREE. or PREMIUM (...) before you call it • Machine-readable server card: https://mcp.moltlinestudio.com/regclock/.well-known/mcp/server-card.json
OVERVIEW An incident-reporting deadline engine that computes from the legal text rather than from a summary: EU Cyber Resilience Act (Art. 14), NIS2 (Art. 23), DORA (Art. 19 with RTS 2025/301), GDPR and UK GDPR (Art. 33/34), US HIPAA breach notification (45 CFR 164.400-414) and SEC Form 8-K Item 1.05. Every deadline carries its citation, its anchor (awareness, classification, discovery, materiality determination), the business-day and bank-holiday adjustments applied, and whether the anchor was actual, estimated or derived. Rule book verified against the official texts on 6 September 2026. Not legal advice.
KEY CAPABILITIES • list_regimes + explain_rule — every regime, obligation, time limit and required content, cited • classify_event — apply a regime's statutory criteria to yes/no facts and name the event type • compute_deadlines — all deadlines of one regime from the moment of awareness, with holiday calendars for the country you name • deadline_status + holiday_calendar — open, due soon, overdue or submitted as of any instant; the public-holiday set the engine used • License: compute_deadlines_multi (one merged timeline across regimes), validate_report (draft checked against the statutory content list), timeline_export (iCalendar + CSV)
USE CASES • A CISO's agent computes the 24 h / 72 h / final-report clocks the moment an incident is classified • A DPO checks whether a draft breach notification covers every GDPR Art. 33(3) element before it is sent • A compliance team exports a merged NIS2 + DORA + GDPR timeline into the shared calendar
WHO THIS IS FOR Security, privacy and compliance teams — and the agents working for them — who need cited, reproducible deadline arithmetic instead of a guess.
WHY MOLTLINE • Every rule tested against worked examples before release • One All-Access licence ($19/month, settled in cryptocurrency through NOWPayments) unlocks the premium tools on every Moltline server - send it in the X-Moltline-License header • Support: first response <24h, confirmed defects fixed <30 days
Independently audited — MCPize Verified A (94/100) on this endpoint (https://mcp.moltlinestudio.com/regclock) · Live check result