Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Shift Scheduler

REMOTE · STAFF-SCHEDULING.KINDOFLOST.COM

Builds optimal 24/7 staff rosters with a real MILP solver: rest rules, skills, nights, fairness.

0 this week 86 Trust /100

Last scanned (22 hours ago)

Scores higher than 88% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Project Management

Trust breakdown (7 categories)

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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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
Schema Quality & AI Usability73
  • 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 1284 tokens (~256/item across 5 items; 5 tools + 0 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 73% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 −1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Oct 26 +1
    • Stability: 0.97 → pass security
  • 25 Oct 26 +3
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “build_shift_roster” rewrote its description, which is the text the model reads security
    • Schema quality: 995 → 1252 ▼ functional
    • The server now declares the “prompts” capability functional
    • First check of Schema quality: 100 functional
    • New prompt “nurse_roster_4_weeks” functional
    • New prompt “security_guard_24_7” functional
    • New prompt “turnos_rotativos_24_7” functional
    • Server version: 1.0.0 → 1.0.1 functional
    • New tool “check_request” functional
    • “build_shift_roster” added an optional parameter “goal” cosmetic
  • 24 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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 21 Nov 2026 · Probed https://staff-scheduling.kindoflost.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=staff-scheduling.kindoflost.com CN=WE1,O=Google Trust Services,C=US 20 Nov 2026 18 Feb 2027 ECDSA 256 ECDSA-SHA256 bc6969ceda3f184a0e6ce03c154da6a8
SANs: staff-scheduling.kindoflost.com
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 staff-scheduling.kindoflost.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
kindoflost.com. No DS 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=31536000; includeSubDomains
content-security-policy frame-ancestors 'self'
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin
permissions-policy geolocation=(), microphone=(), camera=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://staff-scheduling.kindoflost.com/mcp Verified 200
http (plaintext) http://staff-scheduling.kindoflost.com/mcp HTTPS enforced 301 https://staff-scheduling.kindoflost.com/mcp
MCP tools · 5 exposed · ~1,069 tokens

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 →

Tool Tokens
build_shift_roster ~784

Solve a staff rostering problem to optimality with a MILP solver and return who works which shift each day, coverage, unfilled posts, hours per person and warnings. Solves take 5-60 s. Pass either `example` (to solve a built-in example as-is) or the roster input fields. If the result has status 'running', call get_shift_roster_result with its job_id. If it has status 'too_large', shorten the horizon or reduce people/shift types and retry. If it has status 'busy', wait the retry_after_seconds it gives and call again -- one call at a time, never in parallel. Safe defaults (e.g. the next 7 days when `days` is omitted) are listed in the result's `assumptions`; tell the user about them. Roster input. Minimal example: {"days": ["2026-10-05", "2026-10-06"], "shifts": [{"shift": "Day", "start": "07:00", "end": "19:00"}, {"shift": "Night", "start": "19:00", "end": "07:00", "night": "yes"}], "demands": [{"name": "RN", "penalty": 500}], "people": [{"name": "Ana", "cost": 40, "max_hw": 48}, ...], "grids": {"RN": {"2026-10-05|Day": 2, "2026-10-05|Night": 1}}, "parameters": {"MinRestHours": 11}}. Call get_shift_example for complete, realistic inputs.

NameTypeReqDescription
daysarray–OPTIONAL. Day labels in order: ISO dates ('2026-10-05') or weekday names ('Mon'). Dates or weekdays enable weekend rules. Omit it to plan the next 7 days (ISO dates starting tomorrow); the default us…
demandsarray–Posts to fill (roles). Headcount per day/shift goes in grids.
examplestring–Solve this built-in example instead of passing the fields below.
goalstring–One sentence, in the user's own words, of what they are trying to do (e.g. 'a 4-week nurse rota for 12 nurses on 12-hour shifts'). Optional; helps improve the tool.
gridsobject–Optional per-day/shift cells, keyed by a demand name or a person name, each an object keyed 'DAY|SHIFT'. Demand grid value = headcount required (demand with no grid = 1 on every shift). Person grid v…
parametersobject–Optional rules. MinRestHours (11), MaxConsecutiveDays (6), MaxConsecutiveNights (4), ForbidDayAfterNight ('yes'), NightStartsAfter ('18:00'), MinBlockDays (1), WeekendFairnessPenalty (0), EquityPenal…
peoplearray––
shiftsarray–Shift types. A shift may cross midnight (end < start).
skillsarray–Who can cover which demand. Omitted = everyone can cover every demand.
wait_secondsinteger–How long to wait for the solve inside this call (default 25).

No output schema declared.

No examples provided.

check_request ~99

Describe what the user wants in plain words and get back whether this server can do it, which limits it would hit, and the closest thing it CAN do. Instant, no solve. Use it when unsure the tool fits (shift swaps, payroll, time clocks, very large teams or long horizons).

NameTypeReqDescription
descriptionstringyesThe user's request in their own words, e.g. 'rota for 80 nurses over 3 months with shift swaps'.

No output schema declared.

No examples provided.

get_shift_example ~67

Return the full input JSON of one example, in exactly the shape build_shift_roster accepts. Edit it (names, days, headcounts, rules) to match the user's situation.

NameTypeReqDescription
langstring–es = Spanish shift and post names.
namestringyes–

No output schema declared.

No examples provided.

get_shift_roster_result ~67

Fetch the result of a build_shift_roster job that returned status 'running'. Waits up to wait_seconds; call again while status is 'running'. Jobs expire 15 minutes after they finish.

NameTypeReqDescription
job_idstringyes–
wait_secondsinteger––

No output schema declared.

No examples provided.

list_shift_examples ~52

List the built-in example rostering problems (hospital ward, 3-shift plant, security post, fire station, 24/7 help desk). Use one as a starting point for the user's own roster.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the Shift Scheduler MCP server?

Shift Scheduler is a hosted endpoint at https://staff-scheduling.kindoflost.com/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 · staff-scheduling.kindoflost.com

# add to Claude Code
claude mcp add --transport http com-kindoflost-staff-scheduling-shift-scheduler 'https://staff-scheduling.kindoflost.com/mcp'
Common questions

What is the Shift Scheduler MCP server?

Shift Scheduler is an MCP server listed in the public MCP registry as com.kindoflost.staff-scheduling/shift-scheduler. Builds optimal 24/7 staff rosters with a real MILP solver: rest rules, skills, nights, fairness. This page covers its hosted endpoint (https://staff-scheduling.kindoflost.com/mcp).

Is the Shift Scheduler MCP server safe to use?

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

Shift Scheduler exposes 5 tools: list_shift_examples, get_shift_example, build_shift_roster, get_shift_roster_result, check_request. Their descriptions and schemas cost roughly 1,069 tokens of context every time the server is loaded.

Does the Shift Scheduler MCP server require authentication?

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

Is the Shift Scheduler MCP server still maintained?

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

What did VerifyMCP test on the Shift Scheduler MCP server?

VerifyMCP ran 13 checks on Shift Scheduler, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.