Moltline TimeOps
REMOTE · MCP.MOLTLINESTUDIO.COM
Business days, meeting overlap and recurrence expansion, deterministic. 3 of 5 tools free.
Available components
Last scanned (22 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 16 Oct 2026.
Category Productivity and Notes
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 → Why this is hard to score →
Endpoint Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability60
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1756 tokens (~351/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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 20 Aug 26 0
- Server version: 3.4.7 → 1.1.0 functional
- 18 Aug 26 0
- Tool “business_days” rewrote its description, which is the text the model reads security
- Tool “deadline_planner” rewrote its description, which is the text the model reads security
- Tool “meeting_overlap” rewrote its description, which is the text the model reads security
- Tool “recurrence_expand” rewrote its description, which is the text the model reads security
- Tool “sla_due” rewrote its description, which is the text the model reads security
- Schema quality: 314 → 351 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Schema quality: good → excellent functional
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 16 Oct 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=moltlinestudio.com | CN=WE1,O=Google Trust Services,C=US | 14 Oct 2026 | 12 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 5fcf21014c71aedb0ee8aa375beac0b4 |
| SANs: moltlinestudio.com, *.moltlinestudio.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
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=15576000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.moltlinestudio.com https://mcp.moltlinestudio.com; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
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 | 301 | https://mcp.moltlinestudio.com/timeops |
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
business_days Business Days ~363
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": ...}. Use when the span must exclude weekends and named holidays. Not for plain calendar-day differences, which are a direct subtraction, and not for scheduling backward from a fixed deadline (deadline_planner). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Anchor 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 Deadline Planner ~351
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": "..."}. Use when the end date is fixed and steps must be placed backward from it. Not for forward counting from a start date (business_days) and not for response-time targets (sla_due). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| buffer_days | integer | – | Business days of safety margin kept free before due_date, clamped to 0-365. Default 1. |
| due_date | string | yes | The deadline, ISO YYYY-MM-DD. |
| holidays | array | – | Optional list of ISO YYYY-MM-DD dates treated as non-working days. |
| tasks | array | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
meeting_overlap Meeting Overlap ~313
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": "..."}. Use when people in different zones need one shared slot. Not for converting a single known time between zones, and not for expanding a recurring series (recurrence_expand). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| offsets_utc | array | yes | 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". |
Structured output declared, but exposes no named fields.
No examples provided.
recurrence_expand Recurrence Expand ~308
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"]}. Use when a recurrence rule has to become concrete dates. Not for counting working days in a span (business_days) and not for finding a slot across zones (meeting_overlap). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
sla_due Sla Due ~371
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". Use when a response or resolution clock has started and one due moment is needed. Not for multi-step project schedules (deadline_planner). 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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | When the SLA clock started, ISO datetime YYYY-MM-DDTHH:MM. |
| sla_hours | number | yes | SLA 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.
How do I install the Moltline TimeOps MCP server?
Moltline TimeOps is a hosted endpoint at https://mcp.moltlinestudio.com/timeops, 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.
remote · mcp.moltlinestudio.com
claude mcp add --transport http com-moltlinestudio-timeops 'https://mcp.moltlinestudio.com/timeops'
What is the Moltline TimeOps MCP server?
Moltline TimeOps is an MCP server listed in the public MCP registry as com.moltlinestudio/timeops. Business days, meeting overlap and recurrence expansion, deterministic. 3 of 5 tools free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/timeops).
Is the Moltline TimeOps MCP server safe to use?
Moltline TimeOps scores 86 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 TimeOps MCP server expose?
Moltline TimeOps exposes 5 tools: business_days, meeting_overlap, recurrence_expand, deadline_planner, sla_due. Their descriptions and schemas cost roughly 1,706 tokens of context every time the server is loaded.
Does the Moltline TimeOps MCP server require authentication?
No. We connected to Moltline TimeOps without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Moltline TimeOps MCP server still maintained?
Moltline TimeOps is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.