# Moltline RegClock (remote · mcp.moltlinestudio.com)

Incident-reporting deadlines from the law: CRA, NIS2, DORA, GDPR, HIPAA, SEC 8-K. 6 of 9 tools free.

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- remote · `mcp.moltlinestudio.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-moltlinestudio-regclock/regclock.md), [page](https://verifymcp.io/servers/com-moltlinestudio-regclock/regclock)

## Channel facts

- Endpoint: `https://mcp.moltlinestudio.com/regclock`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-21.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 3054 tokens (~339/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Moltline RegClock MCP server?

Moltline RegClock is a hosted endpoint at https://mcp.moltlinestudio.com/regclock, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-moltlinestudio-regclock 'https://mcp.moltlinestudio.com/regclock'
```

### Cursor

```json
{
  "mcpServers": {
    "com-moltlinestudio-regclock": {
      "url": "https://mcp.moltlinestudio.com/regclock"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-moltlinestudio-regclock": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/regclock"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-moltlinestudio-regclock]
url = "https://mcp.moltlinestudio.com/regclock"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-moltlinestudio-regclock": {
      "type": "remote",
      "url": "https://mcp.moltlinestudio.com/regclock",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-moltlinestudio-regclock --url 'https://mcp.moltlinestudio.com/regclock' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-moltlinestudio-regclock:
    url: "https://mcp.moltlinestudio.com/regclock"
```

### Netclaw

```json
{
  "McpServers": {
    "com-moltlinestudio-regclock": {
      "Transport": "http",
      "Url": "https://mcp.moltlinestudio.com/regclock"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-moltlinestudio-regclock -t streamable-http -u 'https://mcp.moltlinestudio.com/regclock'
```

### Other

```json
{
  "mcpServers": {
    "com-moltlinestudio-regclock": {
      "type": "http",
      "url": "https://mcp.moltlinestudio.com/regclock"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-08 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 72, +9)

- [security improvement] Authorization: unverified → partial
- [security improvement] HSTS header: unverified → pass
- [functional improvement] Stability: unverified → 0.03

## MCP tools (9)

### `list_regimes` (~169 tokens)

List Regimes

List the reporting regimes this server can compute, with citations. FREE.

Typical input {} returns {"regimes": [{"id": "eu_nis2", "name": ...,
"instrument": ..., "applies_from": ..., "event_types": [...]}, ...],
"verified_on": "2026-09-06"}. Use when choosing the regime id and
event_type for compute_deadlines or classify_event. Not for legal advice:
it reports what the instruments say and when the entry was last checked. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

### `explain_rule` (~305 tokens)

Explain Rule

Quote the time limit, citation and required content for an obligation. FREE.

Typical input {"regime": "eu_cra", "event_type": "severe_incident",
"obligation": "final_report"} returns {"citation": "Art. 14(4)(c)",
"rule": "within one month after ...", "required_content": [...]}. Leave
obligation empty to get every obligation of the event type; leave
event_type empty on single-event regimes. Use when a caller needs the
rule's own words next to a computed date. Not for computing dates: use
compute_deadlines. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown obligation '<value>' for <value>/<value>; one of <value>"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `event_type` (string): event type within the regime (see list_regimes); optional when the regime has one.
- `obligation` (string): obligation id (for example early_warning); empty for all.
- `regime` (string, required): regime id from list_regimes (eu_cra, eu_nis2, eu_dora, eu_gdpr, uk_gdpr, us_hipaa, us_sec_8k).

### `classify_event` (~262 tokens)

Classify Event

Apply a regime's statutory criteria to yes/no facts and name the event type. FREE.

Typical input {"regime": "eu_dora", "facts": {"critical_services_affected":
true, "duration_or_downtime": true, "geographic_spread": true}} returns
{"reportable": true, "event_type": "major_ict_incident", "reasoning":
[...], "criteria": {...}}. Unanswered questions are listed under "missing"
so the caller can go and find out. Use when deciding whether an incident
triggers a regime at all. Not for judging severity in the abstract: it
only applies the written criteria to the facts given. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "facts must be an object of question id -> answer"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `facts` (object, required): answers keyed by the question ids returned for the regime (booleans; integers for counts).
- `regime` (string, required): regime id from list_regimes.

### `compute_deadlines` (~587 tokens)

Compute Deadlines

Compute every reporting deadline of one regime from the moment of awareness. FREE.

Typical input {"regime": "eu_nis2", "event_type": "significant_incident",
"awareness_at": "2026-09-14T09:30:00+02:00"} returns {"deadlines":
[{"obligation": "early_warning", "due_at": "2026-09-15T09:30+02:00",
"citation": "Art. 23(4)(a)", ...}, ...]}. Later clocks that run from an
earlier submission are estimated from that report's due time until you
pass the actual time in submitted. DORA needs classification_at and a
country for the bank-holiday rule; the SEC needs
materiality_determined_at; HIPAA takes discovery_date and
flags.individuals_affected. Use when an incident has just been
identified and the agent needs the instants. Not for several regimes at
once: use compute_deadlines_multi. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "flags must be an object"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `awareness_at` (string, required): when the entity became aware, ISO 8601 with a UTC offset.
- `classification_at` (string): DORA - when the incident was classified as major.
- `country` (string): ISO 3166-1 alpha-2 code for the public-holiday calendar (DORA weekend rule; SEC uses US).
- `discovery_date` (string): HIPAA - the date the breach is treated as discovered (defaults to awareness date).
- `entity_class` (string): e.g. trust_service_provider (NIS2), credit_institution / central_counterparty / trading_venue_operator / nis2_essential_or_important (DORA), business_associate (HIPAA).
- `event_type` (string): event type within the regime; optional when the regime has one.
- `flags` (object): condition answers: high_risk, processor, ongoing, handled_at, individuals_affected, max_residents_of_one_state, business_associate.
- `materiality_determined_at` (string): SEC - when the incident was determined to be material.
- `measure_available_at` (string): CRA - when a corrective or mitigating measure became available.
- `regime` (string, required): regime id from list_regimes.
- `subdiv` (string): optional subdivision code for the holiday calendar (e.g. BY for Bavaria).
- `submitted` (object): actual submission times of earlier reports, e.g. {"initial_notification": "..."}.

### `deadline_status` (~273 tokens)

Deadline Status

Mark each computed deadline open, due soon, overdue or submitted as of now. FREE.

Typical input {"deadlines": <rows from compute_deadlines>, "now":
"2026-09-15T08:00:00+02:00"} returns {"items": [{"obligation":
"early_warning", "status": "due_soon", "hours_remaining": 1.5, ...}],
"overdue": 0, "next_due": {...}}. Use when polling an incident timeline
or deciding what to escalate next. Not for computing the deadlines
themselves. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "deadlines must be a non-empty list of rows from compute_deadlines"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `deadlines` (array, required): rows from compute_deadlines / compute_deadlines_multi (each with obligation and due_at).
- `now` (string, required): the current instant, ISO 8601 with a UTC offset.
- `submitted` (object): actual submission times keyed by obligation id (or "regime/obligation").

### `holiday_calendar` (~248 tokens)

Holiday Calendar

List the public holidays the engine uses for a country and year. FREE.

Typical input {"country": "IE", "year": 2026} returns {"holidays":
[{"date": "2026-01-01", "name": "New Year's Day"}, ...]}. Use when
checking why a business-day or bank-holiday adjustment landed where it
did, or to see whether a country/subdivision is supported. Not a legal
register of bank holidays: it is the `holidays` package's public-holiday
calendar, which is what compute_deadlines uses. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "country is required"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `country` (string, required): ISO 3166-1 alpha-2 code (DE, FR, IE, US, ...).
- `subdiv` (string): optional subdivision code (state, province, region).
- `year` (integer, required): calendar year.

### `compute_deadlines_multi` (~469 tokens)

Compute Deadlines Multi

One merged timeline across several regimes for the same incident. PREMIUM (license).

Typical input {"regimes": [{"regime": "eu_nis2"}, {"regime": "eu_gdpr"},
{"regime": "eu_dora", "entity_class": "credit_institution"}],
"awareness_at": "2026-09-14T09:30:00+02:00", "country": "DE"} returns
{"timeline": [rows sorted by due_at, each tagged with regime], "first_due":
{...}, "per_regime": {...}}. Each entry may carry its own event_type and
entity_class; the anchors and flags are shared. Use when one incident
triggers several regimes and the agent needs a single ordered list. Not
for one regime: compute_deadlines is free. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "regimes must be a non-empty list of <value>"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `awareness_at` (string, required): when the entity became aware, ISO 8601 with a UTC offset.
- `classification_at` (string): DORA classification instant.
- `country` (string): ISO 3166-1 alpha-2 code for the public-holiday calendar.
- `discovery_date` (string): HIPAA discovery date (defaults to the awareness date).
- `entity_class` (string): default entity class for entries that do not set their own.
- `flags` (object): condition answers shared by all regimes (see compute_deadlines).
- `materiality_determined_at` (string): SEC materiality determination instant.
- `measure_available_at` (string): CRA corrective-measure instant.
- `regimes` (array, required): list of {"regime": id, "event_type"?: ..., "entity_class"?: ...} (1-10 entries).
- `subdiv` (string): optional subdivision code for the holiday calendar.
- `submitted` (object): actual submission times keyed by "regime/obligation" or obligation id.

### `validate_report` (~373 tokens)

Validate Report

Check a draft report against the statutory content list and its deadline. PREMIUM (license).

Typical input {"regime": "eu_gdpr", "obligation":
"supervisory_authority_notification", "report": {"nature": "...",
"contact": "...", "consequences": "...", "measures": "..."}} returns
{"checklist": [{"item": "...", "found": true, "evidence": [...]}, ...],
"missing": [...], "coverage": 0.75, "timing": {...}}. The content check is
a keyword heuristic over the report text, reported as such; the timing
check compares submitted_at with due_at and, for GDPR, flags a late
notification that gives no reasons for the delay. Use before a report is
sent. Not a legal review, and it cannot judge quality, only presence. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown obligation '<value>' for <value>/<value>; one of <value>"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `due_at` (string): the computed due instant (from compute_deadlines), optional.
- `event_type` (string): event type within the regime; optional when the regime has one.
- `obligation` (string, required): obligation id (for example incident_notification).
- `regime` (string, required): regime id from list_regimes.
- `report` (object, required): the draft, as an object of section name -> text (any keys).
- `submitted_at` (string): when the report was or will be submitted, optional.

### `timeline_export` (~294 tokens)

Timeline Export

Export computed deadlines as an iCalendar file and CSV rows. PREMIUM (license).

Typical input {"deadlines": <rows from compute_deadlines or the
timeline from compute_deadlines_multi>, "incident_ref": "INC-2026-041"}
returns {"ics": "BEGIN:VCALENDAR...", "csv": "regime,obligation,...",
"events": 4}. Each dated deadline becomes a VEVENT with the citation in
the description and an alarm alarm_hours_before it; rows without a fixed
time limit are listed in the CSV only. Use when the timeline needs to
land in a calendar or a ticket. Not for computing deadlines. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "deadlines must be a non-empty list of rows from compute_deadlines"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `alarm_hours_before` (number): hours before each due instant to fire a VALARM (0 disables).
- `calendar_name` (string): X-WR-CALNAME for the calendar file.
- `deadlines` (array, required): rows from compute_deadlines / compute_deadlines_multi.
- `incident_ref` (string): your incident reference, prefixed to every event summary.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-moltlinestudio-regclock/regclock#diagnostics

## Score history

- 2026-09-21: 79
- 2026-09-20: 79
- 2026-09-19: 78
- 2026-09-18: 78
- 2026-09-17: 77
- 2026-09-16: 77
- 2026-09-15: 76
- 2026-09-14: 76
- 2026-09-13: 75
- 2026-09-12: 75
- 2026-09-11: 74
- 2026-09-10: 74
- 2026-09-09: 73
- 2026-09-08: 73
- 2026-09-07: 72
- 2026-09-06: 63

## Common questions

### What is the Moltline RegClock MCP server?

Moltline RegClock is an MCP server listed in the public MCP registry as com.moltlinestudio/regclock. Incident-reporting deadlines from the law: CRA, NIS2, DORA, GDPR, HIPAA, SEC 8-K. 6 of 9 tools free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/regclock).

### Is the Moltline RegClock MCP server safe to use?

Moltline RegClock scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Moltline RegClock MCP server expose?

Moltline RegClock exposes 9 tools: list_regimes, explain_rule, classify_event, compute_deadlines, deadline_status, and 4 more. Their descriptions and schemas cost roughly 2,980 tokens of context every time the server is loaded.

### Does the Moltline RegClock MCP server require authentication?

No. We connected to Moltline RegClock without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Moltline RegClock MCP server still maintained?

Moltline RegClock is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.moltlinestudio.com/regclock
- Repository: https://github.com/GarphenGate/moltline-mcp
- Website: https://moltlinestudio.com/servers.html#regclock
- Changelog RSS feed: https://verifymcp.io/servers/com-moltlinestudio-regclock/regclock.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-moltlinestudio-regclock/regclock.json
- HTML version of this page: https://verifymcp.io/servers/com-moltlinestudio-regclock/regclock