com.moltlinestudio/timeops

Est-ce que com.moltlinestudio/timeops est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.moltlinestudio/timeops » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• business_days≈ 508 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • add_days · integer · optionnel
    Business days to add; negative subtracts. Range -5000 to 5000. Ignored when end_date is provided.
  • end_date · string · optionnel
    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 · optionnel
    Optional list of ISO YYYY-MM-DD dates to treat as non-working days, e.g. ["2026-12-25"].
  • start_date · string · requis
    Anchor date in ISO format YYYY-MM-DD, e.g. "2026-03-02".

  Exemple d'appel

  {"name": "business_days", "arguments": {"start_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• deadline_planner≈ 509 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • tasks · array · requis
    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.
  • due_date · string · requis
    The deadline, ISO YYYY-MM-DD.
  • holidays · array · optionnel
    Optional list of ISO YYYY-MM-DD dates treated as non-working days.
  • buffer_days · integer · optionnel
    Business days of safety margin kept free before due_date, clamped to 0-365. Default 1.

  Exemple d'appel

  {"name": "deadline_planner", "arguments": {"tasks": [], "due_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• meeting_overlap≈ 442 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

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

  Exemple d'appel

  {"name": "meeting_overlap", "arguments": {"offsets_utc": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• recurrence_expand≈ 438 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

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

  Exemple d'appel

  {"name": "recurrence_expand", "arguments": {"start_date": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• sla_due≈ 516 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

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

  Exemple d'appel

  {"name": "sla_due", "arguments": {"opened_at": "texte", "sla_hours": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.moltlinestudio.com/timeops