Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.moltlinestudio/timeops

REMOTE · MCP.MOLTLINESTUDIO.COM · SCANNED AUG 17

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

Available components

remote · mcp.moltlinestudio.com 70
70 Trust /100
Trust breakdown (6 categories)

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. How we score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability59
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · mcp.moltlinestudio.com

# add to Claude Code
claude mcp add --transport http com-moltlinestudio-timeops https://mcp.moltlinestudio.com/timeops
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add com-moltlinestudio-timeops --url https://mcp.moltlinestudio.com/timeops --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-moltlinestudio-timeops:
    url: "https://mcp.moltlinestudio.com/timeops"
// mcp.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 we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 17 Aug 26 70

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 17 Aug 2026 · Probed https://mcp.moltlinestudio.com/timeops

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.moltlinestudio.com CN=YE1,O=Let's Encrypt,C=US 16 Aug 2026 14 Nov 2026 ECDSA 256 ECDSA-SHA384 6c3ed2184cc1622eb0659f596575816a5c8
SANs: mcp.moltlinestudio.com
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd
DNSSEC secure

Validation of mcp.moltlinestudio.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
moltlinestudio.com. present 2371 13 Verified
mcp.moltlinestudio.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000
x-content-type-options nosniff
Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.moltlinestudio.com/timeops Verified 200
http (plaintext) http://mcp.moltlinestudio.com/timeops HTTPS enforced 308 https://mcp.moltlinestudio.com/timeops
MCP tools · 5 exposed · ~1,522 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
business_days ~321

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.

NameTypeReqDescription
add_daysinteger–Business days to add; negative subtracts. Range -5000 to 5000. Ignored when end_date is provided.
end_datestring–Optional end date, ISO YYYY-MM-DD. When set, the tool counts business days between start_date and end_date instead of adding.
holidaysarray–Optional list of ISO YYYY-MM-DD dates to treat as non-working days, e.g. ["2026-12-25"].
start_datestringyesAnchor date in ISO format YYYY-MM-DD, e.g. "2026-03-02".

Structured output declared, but exposes no named fields.

No examples provided.

deadline_planner ~312

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.

NameTypeReqDescription
buffer_daysinteger–Business days of safety margin kept free before due_date, clamped to 0-365. Default 1.
due_datestringyesThe deadline, ISO YYYY-MM-DD.
holidaysarray–Optional list of ISO YYYY-MM-DD dates treated as non-working days.
tasksarrayyesOrdered list of task objects, each {"name": str, "days": int} where days is the business-day duration (1-365); the first 30 tasks are scheduled.

Structured output declared, but exposes no named fields.

No examples provided.

meeting_overlap ~276

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.

NameTypeReqDescription
offsets_utcarrayyesOne UTC offset per participant, each between -14 and +14; fractional offsets allowed, e.g. [-8, 1, 5.5].
work_endstring–Working day end, 24h HH:MM; must be later than work_start. Default "17:00".
work_startstring–Working day start, 24h HH:MM local in every zone. Default "09:00".

Structured output declared, but exposes no named fields.

No examples provided.

recurrence_expand ~270

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.

NameTypeReqDescription
countinteger–How many dates to generate; values outside 1-60 are clamped into that range. Default 10.
every_daysinteger–Interval in days between occurrences; use this OR weekly_on, not both.
start_datestringyesFirst date of the series, ISO YYYY-MM-DD.
weekly_onarray–Weekday names to recur on, e.g. ["mon", "thu"]; full names like "monday" also work.

Structured output declared, but exposes no named fields.

No examples provided.

sla_due ~343

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.

NameTypeReqDescription
business_hours_onlyboolean–If true, only time inside day_start-day_end on business days counts toward the SLA.
day_endstring–Business day end, 24h HH:MM; must be later than day_start. Default "17:00".
day_startstring–Business day start, 24h HH:MM. Default "09:00".
holidaysarray–Optional list of ISO YYYY-MM-DD dates that never count as working days.
opened_atstringyesWhen the SLA clock started, ISO datetime YYYY-MM-DDTHH:MM.
sla_hoursnumberyesSLA length in hours; greater than 0, at most 24000; fractions allowed, e.g. 7.5.

Structured output declared, but exposes no named fields.

No examples provided.