Skip to content

Rotawise Shift Scheduler MCP server

io.github.theluckystrike/shift-schedulertheluckystrikestreamable-httpv1.0.1Scanned

Weekly staff shift schedules

2 tools: 2 change things.

Tools: 0 delete, 0 irreversible, 2 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • 2 findings

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Rotawise Shift Scheduler MCP server can do

The Rotawise Shift Scheduler MCP server is published by the GitHub account theluckystrike. It has 2 tools. It can create or change data (2 tools: generate_shift_schedule and check_schedule), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 8, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 2Claude Code: ask
  • check_scheduleUse 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", …1 finding

    Why it is in this group

    • The name "check_schedule" says "schedule": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "check_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_schedule" says "schedule": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check a shift schedule
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true
  • generate_shift_scheduleUse 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 si…1 finding

    Why it is in this group

    • The name "generate_shift_schedule" says "generate": a word for a change.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The server marks "generate_shift_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

      Matched text

      annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_shift_schedule" says "generate": a word for a change.

      What this check looks for
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Make a shift schedule
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
    • idempotentHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:35 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://shift-scheduler.zovo.one/mcp: tools/list returned 2 tools to an anonymous client, including generate_shift_schedule (write), check_schedule (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

2 warn
  • The server marks "generate_shift_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "generate_shift_schedule" says "generate": a word for a change.

    What this check looks for
  • The server marks "check_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".

    Matched text

    annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "check_schedule" says "schedule": a word for a change.

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http shift-scheduler https://shift-scheduler.zovo.one/mcp
claude mcp add --transport http shift-scheduler https://shift-scheduler.zovo.one/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__shift-scheduler__generate_shift_schedule",
      "mcp__shift-scheduler__check_schedule"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as shift-scheduler. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.theluckystrike/shift-scheduler/verify?hash=98974de07be9e588336537b9e1a85e03b17633e69f151091ed04237df5160c54" | jq -e '.changed == false'

Pinned hash 98974de07be9, from Nov 8, 2026, 13:17 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.theluckystrike/shift-scheduler/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.theluckystrike/shift-scheduler
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.theluckystrike/shift-scheduler.svg)](https://radar.anlyon.com/servers/io.github.theluckystrike/shift-scheduler)

Source: MCP Registry. Synced Oct 22, 2026, 06:20 UTC.

Rotawise Shift Scheduler MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Rotawise Shift Scheduler MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 2 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Rotawise Shift Scheduler MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Rotawise Shift Scheduler MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Rotawise Shift Scheduler MCP server have?

2 tools: 2 write. generate_shift_schedule and check_schedule.

Does the Rotawise Shift Scheduler MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Rotawise Shift Scheduler MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Rotawise Shift Scheduler MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.