Tick

Next cron run times in any IANA timezone, with DST gap and fold warnings.

Sollte ich dies verwenden

Qualität und Sicherheit

A
Qualität der Beschreibung
100%
Vollständigkeit des Schemas
100%
Qualität der Benennung
80%
Risiko der Vergiftung
100%
Übereinstimmung der Berechtigungen
100%
Einhaltung des Protokolls
100%

Basierend auf einer automatisierten Analyse der Tool-Definitionen und der Einhaltung des Protokolls.

Kontextkosten

~658Tokens (Tool-Definitionen)
~1.6 KBTypische Antwortgröße
Mittlere Auswirkung auf die Aufmerksamkeit (0.51% von 128k Kontext)

Dies ist die ungefähre Anzahl der Tokens, die jedes Mal verbraucht werden, wenn die Tools des Servers in den Kontext eines Modells geladen werden. Höhere Werte verringern die Aufmerksamkeit, die für andere Aufgaben verfügbar ist.

Installieren

Installation mit einem Klick

Fügen Sie dies Ihrer Datei `claude_desktop_config.json` hinzu:

{
  "mcpServers": {
    "tick": {
      "url": "https://tick.clawhard.com/mcp"
    }
  }
}

Remote-Endpunkte

https://tick.clawhard.com/mcpstreamable-http

Was es kann

Tool-Inventar

Tools (2)

🟢 Nur lesen🟡 Schreiben🔴 Löschen⚪ Unbekannt
🟢tick_next_runs(expression, timezone, count, from)

Use when you or the user just wrote a cron expression (GitHub Actions, Vercel cron, Cloudflare Cron Triggers, systemd, an agent schedule) and need its next fire times. Pass the expression and an IANA timezone (default UTC). Returns the next N runs as local wall times and UTC ISO, a plain-English field breakdown, and DST gap/fold warnings (spring-forward skips, fall-back double fires). Example: {"expression":"0 9 * * 1-5","timezone":"America/New_York","count":5}. Uses the tz database, so DST rules match the region and year. Not for converting a meeting time across cities (use Meridian) or for email DNS (use Stamp).

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "expression": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "description": "Cron expression: 5 fields (minute hour day-of-month month day-of-week) or 6 with seconds first. Also accepts @hourly, @daily, @weekly, @monthly, @yearly."
    },
    "timezone": {
      "type": "string",
      "maxLength": 80,
      "description": "IANA timezone for local wall times, e.g. America/New_York. Default UTC."
    },
    "count": {
      "type": "integer",
      "minimum": 1,
      "maximum": 20,
      "description": "How many next runs to return (1–20). Default 5."
    },
    "from": {
      "type": "string",
      "maxLength": 40,
      "description": "Optional ISO datetime to start from (default now), e.g. 2026-03-07T12:00:00Z."
    }
  },
  "required": [
    "expression"
  ]
}
🟢tick_matches(expression, timezone, at)

Use when you need a yes/no on whether a cron expression would fire at a specific instant in a timezone — for example before shipping a schedule that crosses a DST transition, or to verify a single expected fire. Example: {"expression":"0 9 * * 1-5","timezone":"America/New_York","at":"2026-11-06T14:00:00Z"}. Returns fires true/false, the local wall time of that instant, and DST notes if the local time is in a gap or fold.

Eingabe-Schema

{
  "type": "object",
  "properties": {
    "expression": {
      "type": "string",
      "minLength": 1,
      "maxLength": 120,
      "description": "Cron expression (5 or 6 fields, or a nickname like @hourly)."
    },
    "timezone": {
      "type": "string",
      "maxLength": 80,
      "description": "IANA timezone. Default UTC."
    },
    "at": {
      "type": "string",
      "minLength": 1,
      "maxLength": 40,
      "description": "ISO datetime to test, e.g. 2026-11-06T14:00:00Z."
    }
  },
  "required": [
    "expression",
    "at"
  ]
}

Community

Diesen Server bewerten

Nachweis

Aktuelle Beobachtungen

verifiziertVersion nicht aufgezeichnet2 Tools