# com.moltlinestudio/timeops (remote · mcp.moltlinestudio.com)

Hosted MCP server for business-day math, deadline planning, meeting overlap, and SLA calculations.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-17

## Components

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

## Channel facts

- Endpoint: `https://mcp.moltlinestudio.com/timeops`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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-08-17.

- **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**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1572 tokens (~314/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Other

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

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-08-17 (score 70)

First indexed and scored.

## MCP tools (5)

### `business_days` (~321 tokens)

Business Days

Do business-day math that skips weekends and your holiday list. FREE.

Either add N business days to start_date (set add_days), or count the
business days between start_date and end_date (set end_date). Typical
input {"start_date": "2026-03-02", "add_days": 10} returns
{"result_date": "2026-03-16", "result_weekday": "Monday", ...}; with
end_date set it returns {"business_days_between": N, "from": ..., "to": ...}. 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": "dates must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `add_days` (integer): Business days to add; negative subtracts. Range -5000 to 5000. Ignored when end_date is provided.
- `end_date` (string): Optional end date, ISO YYYY-MM-DD. When set, the tool counts business days between start_date and end_date instead of adding.
- `holidays` (array): Optional list of ISO YYYY-MM-DD dates to treat as non-working days, e.g. ["2026-12-25"].
- `start_date` (string, required): Anchor date in ISO format YYYY-MM-DD, e.g. "2026-03-02".

### `meeting_overlap` (~276 tokens)

Meeting Overlap

Find the shared meeting window across time zones inside working hours. FREE.

Give one UTC offset per participant and an optional working-hours window.
Typical input {"offsets_utc": [-8, 1, 5.5]} returns {"overlap_utc":
["HH:MM", "HH:MM"], "overlap_minutes": N, "local_windows": [...]}; when no
shared window exists it returns {"overlap": null, "verdict": "..."}. 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": "times must be HH:MM"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `offsets_utc` (array, required): One UTC offset per participant, each between -14 and +14; fractional offsets allowed, e.g. [-8, 1, 5.5].
- `work_end` (string): Working day end, 24h HH:MM; must be later than work_start. Default "17:00".
- `work_start` (string): Working day start, 24h HH:MM local in every zone. Default "09:00".

### `recurrence_expand` (~270 tokens)

Recurrence Expand

Expand a recurrence rule into a concrete list of ISO dates. FREE.

Set every_days for a fixed interval, or weekly_on for specific weekdays.
Typical input {"start_date": "2026-01-05", "every_days": 14, "count": 3}
returns {"dates": ["2026-01-05", "2026-01-19", "2026-02-02"]}. 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": "start_date must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `count` (integer): How many dates to generate; values outside 1-60 are clamped into that range. Default 10.
- `every_days` (integer): Interval in days between occurrences; use this OR weekly_on, not both.
- `start_date` (string, required): First date of the series, ISO YYYY-MM-DD.
- `weekly_on` (array): Weekday names to recur on, e.g. ["mon", "thu"]; full names like "monday" also work.

### `deadline_planner` (~312 tokens)

Deadline Planner

Plan a task schedule backward from a hard deadline in business days. PREMIUM (license).

Given ordered tasks with business-day durations, returns each task's
start/end dates, the latest safe start, and slack from today. Typical
input {"due_date": "2026-06-01", "tasks": [{"name": "Draft", "days": 3},
{"name": "Review", "days": 2}]} returns {"schedule": [...],
"latest_safe_start": "YYYY-MM-DD", "slack_business_days_from_today": N,
"verdict": "..."}. 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": "due_date must be YYYY-MM-DD"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `buffer_days` (integer): Business days of safety margin kept free before due_date, clamped to 0-365. Default 1.
- `due_date` (string, required): The deadline, ISO YYYY-MM-DD.
- `holidays` (array): Optional list of ISO YYYY-MM-DD dates treated as non-working days.
- `tasks` (array, required): Ordered list of task objects, each {"name": str, "days": int} where days is the business-day duration (1-365); the first 30 tasks are scheduled.

### `sla_due` (~343 tokens)

Sla Due

Compute when a ticket's SLA falls due, wall-clock or business-hours. PREMIUM (license).

Typical input {"opened_at": "2026-03-02T15:30", "sla_hours": 8,
"business_hours_only": true} returns {"due": "2026-03-03T15:30", "mode":
"business hours 09:00-17:00"}; with business_hours_only false the mode is
"wall-clock". 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": "opened_at must be ISO YYYY-MM-DDTHH:MM"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.

Input parameters:

- `business_hours_only` (boolean): If true, only time inside day_start-day_end on business days counts toward the SLA.
- `day_end` (string): Business day end, 24h HH:MM; must be later than day_start. Default "17:00".
- `day_start` (string): Business day start, 24h HH:MM. Default "09:00".
- `holidays` (array): Optional list of ISO YYYY-MM-DD dates that never count as working days.
- `opened_at` (string, required): When the SLA clock started, ISO datetime YYYY-MM-DDTHH:MM.
- `sla_hours` (number, required): SLA length in hours; greater than 0, at most 24000; fractions allowed, e.g. 7.5.

## Diagnostics

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

## Score history

- 2026-08-17: 70

## Links

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