Rotawise Shift Scheduler
REMOTE · SHIFT-SCHEDULER.ZOVO.ONE
Weekly staff shift schedules
Available components
Last scanned (2 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Project Management
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 Security80
- 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 check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
- Supports UI / widget rendering.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.
- 23 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 22 Oct 26 72
First indexed and scored.
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 23 Oct 2026 · Probed https://shift-scheduler.zovo.one/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zovo.one | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 2bef4296c084825e0e01c3dc4c598d04 |
| SANs: zovo.one, shift-scheduler.zovo.one, *.shift-scheduler.zovo.one | ||||||
| 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 insecure
Validation of shift-scheduler.zovo.one. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| one. | present | 64939 | 8 | Verified |
| zovo.one. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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=15552000; includeSubDomains; preload |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shift-scheduler.zovo.one/mcp | Verified | 200 | |
| http (plaintext) | http://shift-scheduler.zovo.one/mcp | HTTPS enforced | 301 | https://shift-scheduler.zovo.one/mcp |
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 →
check_schedule Check a shift schedule ~676
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| downloads | object | yes | – |
| notes | array | yes | – |
| open_shifts | array | yes | – |
| open_shifts_not_shown | number | – | – |
| problem_count | number | yes | – |
| problems | array | yes | – |
| problems_by_rule | object | yes | – |
| rules | object | yes | – |
| staff | array | yes | – |
| valid | boolean | yes | – |
| week | object | yes | – |
No examples provided.
generate_shift_schedule Make a shift schedule ~769
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| assumptions | array | yes | – |
| coverage | object | yes | – |
| downloads | object | yes | – |
| fairness | object | yes | – |
| notes | array | yes | – |
| open_shifts | array | yes | – |
| open_shifts_not_shown | number | – | – |
| rules | object | yes | – |
| schedule | array | yes | – |
| staff | array | yes | – |
| week | object | yes | – |
No examples provided.
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.
remote · shift-scheduler.zovo.one
claude mcp add --transport http theluckystrike-shift-scheduler 'https://shift-scheduler.zovo.one/mcp'
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.