# Rotawise Shift Scheduler (remote · shift-scheduler.zovo.one)

Weekly staff shift schedules

- Trust score: 73/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `shift-scheduler.zovo.one`: 73/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-shift-scheduler/shift-scheduler.md), [page](https://verifymcp.io/servers/theluckystrike-shift-scheduler/shift-scheduler)

## Channel facts

- Endpoint: `https://shift-scheduler.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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-10-23.

- **Endpoint Security**: 80/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 check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1568 tokens (~522/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Rotawise Shift Scheduler MCP server?

Rotawise Shift Scheduler is a hosted endpoint at https://shift-scheduler.zovo.one/mcp, 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.

### Claude

```bash
claude mcp add --transport http theluckystrike-shift-scheduler 'https://shift-scheduler.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-shift-scheduler": {
      "url": "https://shift-scheduler.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-shift-scheduler": {
      "type": "http",
      "url": "https://shift-scheduler.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-shift-scheduler]
url = "https://shift-scheduler.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-shift-scheduler": {
      "type": "remote",
      "url": "https://shift-scheduler.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-shift-scheduler --url 'https://shift-scheduler.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-shift-scheduler:
    url: "https://shift-scheduler.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-shift-scheduler": {
      "Transport": "http",
      "Url": "https://shift-scheduler.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-shift-scheduler -t streamable-http -u 'https://shift-scheduler.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-shift-scheduler": {
      "type": "http",
      "url": "https://shift-scheduler.zovo.one/mcp"
    }
  }
}
```

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-10-23 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 72)

First indexed and scored.

## MCP tools (2)

### `generate_shift_schedule` (~769 tokens)

Make a shift schedule

Use this when the user wants an employee schedule maker or work schedule maker: build a weekly staff or shift schedule for a restaurant, cafe, retail store, clinic front desk or similar from staff names, roles or skills, availability (days or times people cannot work), min/max hours, and the shifts to cover with headcount, e.g. "make a weekly schedule for 6 employees", "need 2 people on each shift, nobody over 40 hours", "make a rotating schedule so weekends are fair", "who should close on friday", "Sam cannot work Mondays". Accepts typed lists or an attached availability CSV/XLSX. A deterministic solver checks each hard rule (roles, availability, max hours, overtime cap, minimum rest between shifts, shifts per day, consecutive days), balances weekend and closing shifts, and when coverage is impossible returns each open shift with the binding reason. Returns hours per person, overtime flags, fairness ranges, and a printable PDF, Excel file and per-employee calendar (.ics) files. Overnight shifts and daylight-saving weeks are counted in real elapsed hours. Does not post schedules, message staff, track clock-ins or run payroll. Do not use for job searches or for checking a schedule the user already made (use check_schedule).

Input parameters:

- `allow_overtime` (boolean): false (default): nobody is scheduled past overtime_after_hours. true: overtime is allowed when needed for coverage, kept as low as possible, and flagged.
- `business_name` (string): Optional name printed on the PDF, e.g. "Blue Door Cafe".
- `max_consecutive_days` (integer): Most days in a row anyone may work in this week, default 6, e.g. 5.
- `max_shifts_per_day` (integer): Default shifts per person per day, default 1. Use 2 to allow split shifts (same-day shifts need no rest gap, only no overlap).
- `min_rest_hours` (number): Minimum hours off between two shifts of the same person (the "clopening" rule), default 10, e.g. 8 or 11. 0 only blocks overlaps.
- `overtime_after_hours` (number): Weekly hours after which time counts as overtime, default 40 (US federal FLSA workweek), e.g. 40. 0 turns overtime tracking off.
- `shifts` (array): Shifts to cover, e.g. [{"day":"Mon-Fri","start":"07:00","end":"15:00","role":"cook","headcount":2}]. Required unless the attached .xlsx has a Shifts sheet.
- `staff` (array): The team, one item per person (up to 80), e.g. [{"name":"Ana","roles":["cook"],"max_hours":40,"unavailable":["Sun"]}]. Can be combined with staff_file.
- `staff_file` (object): Optional staff availability spreadsheet the user attached (CSV or Excel .xlsx), e.g. availability.xlsx: a Name column plus Role, Max hours, Min hours, Unavailable, Preferred, and/or day columns (Mon.…
- `time_zone` (string): The business's time zone, IANA or US name, e.g. "America/Chicago", "Pacific". Default America/New_York. Used for daylight-saving weeks and calendar files.
- `week_start` (string): First day of the week to schedule, e.g. "2026-10-05". Default: next Monday. Dates pin calendar files and daylight-saving weeks to real hours.

Output parameters:

- `assumptions` (array)
- `coverage` (object)
- `downloads` (object)
- `fairness` (object)
- `notes` (array)
- `open_shifts` (array)
- `open_shifts_not_shown` (number)
- `rules` (object)
- `schedule` (array)
- `staff` (array)
- `week` (object)

### `check_schedule` (~676 tokens)

Check a shift schedule

Use this when the user already has a work schedule and wants it checked against scheduling rules: "check this schedule", "does anyone have a clopening", "is anyone over 40 hours", "fix this schedule, Sam cannot work Mondays". Takes the shifts with the people on them (typed, or an attached schedule CSV/XLSX grid or list) plus optional staff rules (roles, max hours, unavailable days) and reports each problem it finds: overlapping or double-booked shifts, less rest than the rule between shifts, too many shifts per day or days in a row, over max hours or overtime, wrong role, unavailable times, and shifts below headcount. Returns hours per person and a PDF, Excel and per-employee calendar files of the checked schedule. Does not change the schedule itself (generate_shift_schedule builds a corrected one) and does not give legal advice on scheduling laws.

Input parameters:

- `allow_overtime` (boolean): false (default): nobody is scheduled past overtime_after_hours. true: overtime is allowed when needed for coverage, kept as low as possible, and flagged.
- `assignments` (array): The schedule to check, one item per shift with its people, e.g. [{"day":"Fri","start":"16:00","end":"23:00","staff":["Sam"]},{"day":"Sat","start":"07:00","end":"15:00","staff":["Sam"]}].
- `business_name` (string): Optional name printed on the PDF, e.g. "Blue Door Cafe".
- `max_consecutive_days` (integer): Most days in a row anyone may work in this week, default 6, e.g. 5.
- `max_shifts_per_day` (integer): Default shifts per person per day, default 1. Use 2 to allow split shifts (same-day shifts need no rest gap, only no overlap).
- `min_rest_hours` (number): Minimum hours off between two shifts of the same person (the "clopening" rule), default 10, e.g. 8 or 11. 0 only blocks overlaps.
- `overtime_after_hours` (number): Weekly hours after which time counts as overtime, default 40 (US federal FLSA workweek), e.g. 40. 0 turns overtime tracking off.
- `schedule_file` (object): Optional existing schedule the user attached (CSV or .xlsx): a grid with a Name column and day columns (Mon..Sun) holding "07:00-15:00 cook" or "off", or a list with Employee, Day, Start, End, Role c…
- `staff` (array): Optional staff rules to check against (roles, max hours, unavailable days), same format as generate_shift_schedule, e.g. [{"name":"Sam","unavailable":["Mon"]}].
- `time_zone` (string): The business's time zone, IANA or US name, e.g. "America/Chicago", "Pacific". Default America/New_York. Used for daylight-saving weeks and calendar files.
- `week_start` (string): First day of the week to schedule, e.g. "2026-10-05". Default: next Monday. Dates pin calendar files and daylight-saving weeks to real hours.

Output parameters:

- `assumptions` (array)
- `downloads` (object)
- `notes` (array)
- `open_shifts` (array)
- `open_shifts_not_shown` (number)
- `problem_count` (number)
- `problems` (array)
- `problems_by_rule` (object)
- `rules` (object)
- `staff` (array)
- `valid` (boolean)
- `week` (object)

## Diagnostics

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

## Score history

- 2026-10-23: 73
- 2026-10-22: 72

## Common questions

### What is the Rotawise Shift Scheduler MCP server?

Rotawise Shift Scheduler is an MCP server listed in the public MCP registry as io.github.theluckystrike/shift-scheduler. Weekly staff shift schedules. This page covers its hosted endpoint (https://shift-scheduler.zovo.one/mcp).

### Is the Rotawise Shift Scheduler MCP server safe to use?

Rotawise Shift Scheduler scores 73 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 Rotawise Shift Scheduler MCP server expose?

Rotawise Shift Scheduler exposes 2 tools: generate_shift_schedule, check_schedule. Their descriptions and schemas cost roughly 1,445 tokens of context every time the server is loaded.

### Does the Rotawise Shift Scheduler MCP server require authentication?

No. We connected to Rotawise Shift Scheduler without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Rotawise Shift Scheduler MCP server still maintained?

Rotawise Shift Scheduler is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://shift-scheduler.zovo.one/mcp
- Website: https://shift-scheduler.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-shift-scheduler/shift-scheduler.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-shift-scheduler/shift-scheduler.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-shift-scheduler/shift-scheduler