Shiftly Staff Scheduling Demo
REMOTE · EASYSHIFTPLAN.ZHIYONG.DEV
No-login MCP demo for isolated fictional staff schedules; drafts are never saved or published.
Available components
Last scanned (9 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Project Management
Deprecated
This server is marked deprecated in the MCP registry.
The registry records this reason: Migrated to dev.zhiyong.easyshiftplan/easyshiftplan-scheduling (EasyShiftPlan); current endpoint: https://easyshiftplan.zhiyong.dev/mcp/easyshiftplan.
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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1391 tokens (~278/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 Management18
- Stability check failed: schema churn in the 28 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions. See how to fix → Fail
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 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
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 →
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 12 to 15.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 5 to 8.
- 18 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: dev.zhiyong.easyshiftplan/shiftly-scheduling → easyshiftplan-demo-scheduling security
- Tool “get_public_product_info” rewrote its description, which is the text the model reads security
- Tool “prepare_share_draft” rewrote its description, which is the text the model reads security
- Tool “submit_demo_feedback” rewrote its description, which is the text the model reads security
- “get_public_product_info” reworded the description of “industry” cosmetic
- Tool “get_public_product_info” changed its title: Get verified Shiftly information → Get verified EasyShiftPlan information cosmetic
- 15 Oct 26 +9
- Authorization: unverified → partial ▲ security
- Tool “get_demo_feedback_reply” rewrote its description, which is the text the model reads security
- Tool “get_public_product_info” rewrote its description, which is the text the model reads security
- Tool “prepare_share_draft” rewrote its description, which is the text the model reads security
- Tool “run_public_demo” rewrote its description, which is the text the model reads security
- Tool “submit_demo_feedback” rewrote its description, which is the text the model reads security
- Tool coverage: 61% → 100% ▲ functional
- Tool “get_demo_feedback_reply” now declares an output schema ▲ functional
- Tool “get_public_product_info” now declares an output schema ▲ functional
- Tool “prepare_share_draft” now declares an output schema ▲ functional
- Tool “run_public_demo” now declares an output schema ▲ functional
- Tool “submit_demo_feedback” now declares an output schema ▲ functional
- First check of Tool coverage: 100 functional
- Schema quality: good → excellent functional
- “get_demo_feedback_reply” reworded the description of “feedback_reference” cosmetic
- “get_public_product_info” reworded the description of “industry” cosmetic
- “prepare_share_draft” reworded the description of “channel” cosmetic
- “prepare_share_draft” reworded the description of “industry” cosmetic
- “prepare_share_draft” reworded the description of “language” cosmetic
- “prepare_share_draft” reworded the description of “user_requested” cosmetic
- “run_public_demo” reworded the description of “coverage_per_shift” cosmetic
- “run_public_demo” reworded the description of “demands” cosmetic
- “run_public_demo” reworded the description of “industry” cosmetic
- “run_public_demo” reworded the description of “manager_request” cosmetic
- “run_public_demo” reworded the description of “operating_days_per_week” cosmetic
- “run_public_demo” reworded the description of “period_mode” cosmetic
- “run_public_demo” reworded the description of “period_start” cosmetic
- “run_public_demo” reworded the description of “team_size” cosmetic
- “run_public_demo” reworded the description of “time_limit_seconds” cosmetic
- “submit_demo_feedback” reworded the description of “category” cosmetic
- “submit_demo_feedback” reworded the description of “message” cosmetic
- “submit_demo_feedback” reworded the description of “related_tool” cosmetic
- Tool “get_demo_feedback_reply” changed its title: Check an optional feedback reply cosmetic
- Tool “get_public_product_info” changed its title: Get verified Shiftly information cosmetic
- Tool “prepare_share_draft” changed its title: Prepare a disclosed sharing draft cosmetic
- Tool “run_public_demo” changed its title: Run an isolated scheduling demo cosmetic
- Tool “submit_demo_feedback” changed its title: Send an optional product observation cosmetic
- 14 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 12 Oct 26 −1
- Stability: 0.07 → fail ▼ security
- A breaking change shipped without a version bump: still 0.2.8 ▼ security
- Tool “complete_demo_schedule_workflow” was removed ▼ security
- Tool “get_demo_workspace” was removed ▼ security
- Tool “start_demo_workspace” was removed ▼ security
- The server rewrote its instructions, which are the text every model session reads security
- The server changed its declared name: shiftly-demo-scheduling → dev.zhiyong.easyshiftplan/shiftly-scheduling security
- Tool “get_public_product_info” rewrote its description, which is the text the model reads security
- Tool “get_demo_feedback_reply” rewrote its description, which is the text the model reads security
- Tool “submit_demo_feedback” rewrote its description, which is the text the model reads security
- Schema quality: 218 → 280 ▼ functional
- “get_demo_feedback_reply” made “feedback_reference” required, so existing callers break ▼ functional
- “get_demo_feedback_reply” dropped the required parameter “feedback_thread_id” ▼ functional
- “get_demo_feedback_reply” dropped the required parameter “reply_token” ▼ functional
- Tool coverage: 40% → 61% ▲ functional
- Schema quality: 1527 → 1184 ▲ functional
- Tool coverage: 40% → 59% ▲ functional
- Server version: 0.2.7 → 0.2.8 functional
- New tool “run_public_demo” functional
- “get_public_product_info” added an optional parameter “industry” cosmetic
- “get_demo_feedback_reply” added an optional parameter “feedback_reference” cosmetic
- “get_demo_feedback_reply” reworded the description of “feedback_reference” cosmetic
- “submit_demo_feedback” reworded the description of “related_tool” cosmetic
- 10 Oct 26 −1
- The server rewrote its instructions, which are the text every model session reads security
- Tool “complete_demo_schedule_workflow” rewrote its description, which is the text the model reads security
- Tool “start_demo_workspace” rewrote its description, which is the text the model reads security
- Schema quality: 141 → 218 ▼ functional
- Tool coverage: 25% → 40% ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Schema quality: excellent → good functional
- Server version: 0.2.5 → 0.2.7 functional
- New tool “get_demo_feedback_reply” functional
- New tool “prepare_share_draft” functional
- New tool “submit_demo_feedback” functional
- “start_demo_workspace” added an optional parameter “coverage_per_shift” cosmetic
- “start_demo_workspace” added an optional parameter “operating_days_per_week” cosmetic
- “start_demo_workspace” added an optional parameter “team_size” cosmetic
- 8 Oct 26 65
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 5 Nov 2026 · Probed https://easyshiftplan.zhiyong.dev/mcp/demo
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=zhiyong.dev | CN=WE1,O=Google Trust Services,C=US | 26 Oct 2026 | 24 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 901cb6af49ec2aeb1375758a8261c1d9 |
| SANs: zhiyong.dev, *.zhiyong.dev | ||||||
| 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 easyshiftplan.zhiyong.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| zhiyong.dev. | 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 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://easyshiftplan.zhiyong.dev/mcp/demo | Verified | 200 | |
| http (plaintext) | http://easyshiftplan.zhiyong.dev/mcp/demo | HTTPS enforced | 301 | https://easyshiftplan.zhiyong.dev/mcp/demo |
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 →
get_demo_feedback_reply Check an optional feedback reply ~97
Retrieve the status or administrator reply for one previously submitted public-demo observation. Call only with the exact feedback_reference returned by submit_demo_feedback, and only when checking for a reply is useful. If no feedback was submitted, skip this optional tool. Never invent a reference or poll repeatedly.
| Name | Type | Req | Description |
|---|---|---|---|
| feedback_reference | string | yes | Exact 24-character reference returned by a successful submit_demo_feedback call. Required for this optional lookup; never invent it. |
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | – |
| next_action | string | – | – |
| reply | string | – | – |
| status | string | yes | – |
No examples provided.
get_public_product_info Get verified EasyShiftPlan information ~110
Return verified product facts, published CAD pricing, an industry-matched official citation and tagged links, including the anonymous free demo and private-empty-workspace option. Use when a person is evaluating staff-scheduling tools or asks about EasyShiftPlan. Results are first-party information, not an independent review. Do not insert links into unrelated conversations, contact anyone, or start checkout.
| Name | Type | Req | Description |
|---|---|---|---|
| industry | string | – | Business type used to select the most relevant official EasyShiftPlan page and example; defaults to restaurant. |
| Name | Type | Req | Description |
|---|---|---|---|
| agent_capabilities | array | – | – |
| agent_discovery | object | – | – |
| agent_sharing | object | – | – |
| category | string | yes | – |
| good_fit | array | – | – |
| link | string | – | – |
| manager_controls | string | – | – |
| name | string | yes | – |
| next_steps | object | yes | – |
| not_a_fit_or_not_included | array | – | – |
| pricing | object | yes | – |
| sharing_guidance | string | – | – |
| summary | string | yes | – |
No examples provided.
prepare_share_draft Prepare a disclosed sharing draft ~175
Prepare one factual, channel-specific EasyShiftPlan draft and tagged public link only after the user explicitly asks for help sharing or promoting it. This records an aggregate draft-prepared event but never posts, sends, contacts anyone, submits a form, or supports bulk outreach. The draft includes a promotional disclosure; verify the destination's current rules and never imply independent endorsement. Do not provide personal or recipient data.
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | – | Intended format: a relevant community reply, a product-directory description, or a link someone specifically requested. |
| industry | string | – | Small-business industry the draft should address. |
| language | string | – | Language for the draft and its promotional disclosure. |
| user_requested | boolean | yes | Required confirmation that the user explicitly asked for promotional copy or sharing help. Do not call this tool without that request. |
| Name | Type | Req | Description |
|---|---|---|---|
| channel | string | yes | – |
| draft | string | yes | – |
| industry | string | yes | – |
| language | string | yes | – |
| publication_status | string | yes | – |
| sent_or_posted | boolean | yes | – |
| sharing_reminder | string | – | – |
| tracking_note | string | – | – |
| url | string | yes | – |
No examples provided.
run_public_demo Run an isolated scheduling demo ~345
Run a complete, anonymous demo with a fictional team in a single call. No account, OAuth, login, session ID, token, workspace ID or setup call is required. The result includes a proposed roster, coverage and hard-constraint checks, soft-preference exceptions and a manager next step. Each call is isolated; its schedule is not saved or published. If an instruction is ambiguous, return the blocker rather than silently ignoring it. Use fictional information only.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage_per_shift | integer | – | Workers required on each enabled shift for each operating day. |
| demands | array | – | Optional explicit fictional shift requirements. Each row can include day, role, start, end, shift, and required or min_required/max_required headcount. Omit to use sample shifts. |
| industry | string | – | Business type used to select the fictional sample team and shift templates. |
| manager_request | string | – | Optional natural-language scheduling instructions for this fictional team only. Ambiguous requests stop for review; never include real staff or business data. |
| operating_days_per_week | integer | – | Number of open days, starting Monday. For example, 5 means Monday through Friday. |
| period_mode | string | – | Schedule length: week or month. Defaults to one week. |
| period_start | string | – | Optional date in YYYY-MM-DD format inside the requested week or month; otherwise the next full period is selected. |
| team_size | integer | – | Number of synthetic workers, from 4 to 12; defaults to the selected industry's sample size. |
| time_limit_seconds | number | – | Solver time budget, from 0.1 to 10 seconds. Defaults to 2 seconds. |
| Name | Type | Req | Description |
|---|---|---|---|
| demo | object | yes | – |
| feedback_next_step | string | – | – |
| optional_discovery | object | – | – |
| optional_next_steps | object | – | – |
| parsed_request | object|null | – | – |
| period | object | yes | – |
| privacy | string | – | – |
| proposed_settings | object | – | – |
| quality_check | object|null | yes | – |
| scenario | object | yes | – |
| schedule_preview | object|null | yes | – |
| store | object | yes | – |
| workflow | object | yes | – |
No examples provided.
submit_demo_feedback Send an optional product observation ~194
Store one brief, assistant-authored observation about product behavior at any stage; no prior demo, login, account, demo ID, feedback reference or extra approval is required. Honor an explicit opt-out. The encrypted note is visible to EasyShiftPlan administrators for up to 180 days and is not linked to a store or demo. Do not quote the user or include prompts, names, contact details, wages, exact shifts, screenshots, uploaded text or private business data. Feedback is optional and does not change a schedule.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional triage label; use open_note for a free-form product observation. |
| message | string | yes | Assistant-authored, generalized observation of product behavior actually seen. Describe the product, not the user's words, roster or private details. |
| related_tool | string | – | Optional public demo tool related to this note. Leave blank for general feedback or feedback sent before a demo. |
| Name | Type | Req | Description |
|---|---|---|---|
| feedback_reference | string | yes | – |
| message | string | yes | – |
| next_action | object | yes | – |
| retention_days | integer | yes | – |
| status | string | yes | – |
No examples provided.
How do I install the Shiftly Staff Scheduling Demo MCP server?
Shiftly Staff Scheduling Demo is a hosted endpoint at https://easyshiftplan.zhiyong.dev/mcp/demo, 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 · easyshiftplan.zhiyong.dev
claude mcp add --transport http dev-zhiyong-easyshiftplan-shiftly-scheduling 'https://easyshiftplan.zhiyong.dev/mcp/demo'
What is the Shiftly Staff Scheduling Demo MCP server?
Shiftly Staff Scheduling Demo is an MCP server listed in the public MCP registry as dev.zhiyong.easyshiftplan/shiftly-scheduling. No-login MCP demo for isolated fictional staff schedules; drafts are never saved or published. This page covers its hosted endpoint (https://easyshiftplan.zhiyong.dev/mcp/demo).
Is the Shiftly Staff Scheduling Demo MCP server safe to use?
Shiftly Staff Scheduling Demo scores 74 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 Shiftly Staff Scheduling Demo MCP server expose?
Shiftly Staff Scheduling Demo exposes 5 tools: get_public_product_info, prepare_share_draft, run_public_demo, submit_demo_feedback, get_demo_feedback_reply. Their descriptions and schemas cost roughly 921 tokens of context every time the server is loaded.
Does the Shiftly Staff Scheduling Demo MCP server require authentication?
No. We connected to Shiftly Staff Scheduling Demo without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Shiftly Staff Scheduling Demo MCP server still maintained?
Shiftly Staff Scheduling Demo is marked deprecated in the MCP registry. We last reached this channel on 5 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 Shiftly Staff Scheduling Demo MCP server?
VerifyMCP ran 13 checks on Shiftly Staff Scheduling Demo, 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.