# Shiftly Staff Scheduling Demo (remote · easyshiftplan.zhiyong.dev)

No-login MCP demo for isolated fictional staff schedules; drafts are never saved or published.

- Trust score: 74/100 (medium)
- Change this week: +2
- Registry status: deprecated
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

> **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.`"

## Components

- remote · `easyshiftplan.zhiyong.dev`: 74/100 (this document), [markdown](https://verifymcp.io/servers/dev-zhiyong-easyshiftplan-shiftly-scheduling/mcp-demo.md), [page](https://verifymcp.io/servers/dev-zhiyong-easyshiftplan-shiftly-scheduling/mcp-demo)

## Channel facts

- Endpoint: `https://easyshiftplan.zhiyong.dev/mcp/demo`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.8`

## 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-11-05.

- **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. 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.
  - 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**: 65/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 18/100
  - Stability check failed: schema churn in the 28 days we've observed: 3 tool removals, 0 breaking changes, 0 auth/transport breaks, 4 additions.
- **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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

### Claude

```bash
claude mcp add --transport http dev-zhiyong-easyshiftplan-shiftly-scheduling 'https://easyshiftplan.zhiyong.dev/mcp/demo'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-zhiyong-easyshiftplan-shiftly-scheduling": {
      "url": "https://easyshiftplan.zhiyong.dev/mcp/demo"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-zhiyong-easyshiftplan-shiftly-scheduling": {
      "type": "http",
      "url": "https://easyshiftplan.zhiyong.dev/mcp/demo"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-zhiyong-easyshiftplan-shiftly-scheduling]
url = "https://easyshiftplan.zhiyong.dev/mcp/demo"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-zhiyong-easyshiftplan-shiftly-scheduling": {
      "type": "remote",
      "url": "https://easyshiftplan.zhiyong.dev/mcp/demo",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-zhiyong-easyshiftplan-shiftly-scheduling --url 'https://easyshiftplan.zhiyong.dev/mcp/demo' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-zhiyong-easyshiftplan-shiftly-scheduling:
    url: "https://easyshiftplan.zhiyong.dev/mcp/demo"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-zhiyong-easyshiftplan-shiftly-scheduling": {
      "Transport": "http",
      "Url": "https://easyshiftplan.zhiyong.dev/mcp/demo"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-zhiyong-easyshiftplan-shiftly-scheduling -t streamable-http -u 'https://easyshiftplan.zhiyong.dev/mcp/demo'
```

### Other

```json
{
  "mcpServers": {
    "dev-zhiyong-easyshiftplan-shiftly-scheduling": {
      "type": "http",
      "url": "https://easyshiftplan.zhiyong.dev/mcp/demo"
    }
  }
}
```

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-11-04 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 12 to 15.

### 2026-11-02 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 5 to 8.

### 2026-10-18 (score 72, 0)

- [security] 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
- [cosmetic] “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

### 2026-10-15 (score 72, +9)

- [security improvement] 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
- [functional improvement] Tool coverage: 61% → 100%
- [functional improvement] Tool “get_demo_feedback_reply” now declares an output schema
- [functional improvement] Tool “get_public_product_info” now declares an output schema
- [functional improvement] Tool “prepare_share_draft” now declares an output schema
- [functional improvement] Tool “run_public_demo” now declares an output schema
- [functional improvement] Tool “submit_demo_feedback” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Schema quality: good → excellent
- [cosmetic] “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

### 2026-10-14 (score 63, 0)

- [security] The server rewrote its instructions, which are the text every model session reads

### 2026-10-12 (score 63, −1)

- [security regression] Stability: 0.07 → fail
- [security regression] A breaking change shipped without a version bump: still 0.2.8
- [security regression] Tool “complete_demo_schedule_workflow” was removed
- [security regression] Tool “get_demo_workspace” was removed
- [security regression] 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
- [functional regression] Schema quality: 218 → 280
- [functional regression] “get_demo_feedback_reply” made “feedback_reference” required, so existing callers break
- [functional regression] “get_demo_feedback_reply” dropped the required parameter “feedback_thread_id”
- [functional regression] “get_demo_feedback_reply” dropped the required parameter “reply_token”
- [functional improvement] Tool coverage: 40% → 61%
- [functional improvement] Schema quality: 1527 → 1184
- [functional improvement] Tool coverage: 40% → 59%
- [functional] Server version: 0.2.7 → 0.2.8
- [functional] New tool “run_public_demo”
- [cosmetic] “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”

### 2026-10-10 (score 64, −1)

- [security] 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
- [functional regression] Schema quality: 141 → 218
- [functional improvement] Tool coverage: 25% → 40%
- [functional improvement] 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”
- [cosmetic] “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”

### 2026-10-08 (score 65)

First indexed and scored.

## MCP tools (5)

### `get_public_product_info` (~110 tokens)

Get verified EasyShiftPlan information

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.

Input parameters:

- `industry` (string): Business type used to select the most relevant official EasyShiftPlan page and example; defaults to restaurant.

Output parameters:

- `agent_capabilities` (array)
- `agent_discovery` (object)
- `agent_sharing` (object)
- `category` (string)
- `good_fit` (array)
- `link` (string)
- `manager_controls` (string)
- `name` (string)
- `next_steps` (object)
- `not_a_fit_or_not_included` (array)
- `pricing` (object)
- `sharing_guidance` (string)
- `summary` (string)

### `prepare_share_draft` (~175 tokens)

Prepare a disclosed sharing draft

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.

Input parameters:

- `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, required): Required confirmation that the user explicitly asked for promotional copy or sharing help. Do not call this tool without that request.

Output parameters:

- `channel` (string)
- `draft` (string)
- `industry` (string)
- `language` (string)
- `publication_status` (string)
- `sent_or_posted` (boolean)
- `sharing_reminder` (string)
- `tracking_note` (string)
- `url` (string)

### `run_public_demo` (~345 tokens)

Run an isolated scheduling demo

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.

Input parameters:

- `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.

Output parameters:

- `demo` (object)
- `feedback_next_step` (string)
- `optional_discovery` (object)
- `optional_next_steps` (object)
- `parsed_request` (object|null)
- `period` (object)
- `privacy` (string)
- `proposed_settings` (object)
- `quality_check` (object|null)
- `scenario` (object)
- `schedule_preview` (object|null)
- `store` (object)
- `workflow` (object)

### `submit_demo_feedback` (~194 tokens)

Send an optional product observation

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.

Input parameters:

- `category` (string): Optional triage label; use open_note for a free-form product observation.
- `message` (string, required): 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.

Output parameters:

- `feedback_reference` (string)
- `message` (string)
- `next_action` (object)
- `retention_days` (integer)
- `status` (string)

### `get_demo_feedback_reply` (~97 tokens)

Check an optional feedback reply

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.

Input parameters:

- `feedback_reference` (string, required): Exact 24-character reference returned by a successful submit_demo_feedback call. Required for this optional lookup; never invent it.

Output parameters:

- `message` (string)
- `next_action` (string)
- `reply` (string)
- `status` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-zhiyong-easyshiftplan-shiftly-scheduling/mcp-demo#diagnostics

## Score history

- 2026-11-05: 74
- 2026-11-04: 74
- 2026-11-03: 73
- 2026-11-02: 73
- 2026-11-01: 72
- 2026-10-31: 72
- 2026-10-30: 72
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 72
- 2026-10-24: 72
- 2026-10-23: 72
- 2026-10-22: 72
- 2026-10-21: 72
- 2026-10-20: 72
- 2026-10-19: 72
- 2026-10-18: 72
- 2026-10-17: 72
- 2026-10-16: 72
- 2026-10-15: 72
- 2026-10-14: 63
- 2026-10-13: 63
- 2026-10-12: 63
- 2026-10-10: 64
- 2026-10-08: 65

## Common questions

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

## Links

- Remote endpoint: https://easyshiftplan.zhiyong.dev/mcp/demo
- Website: https://easyshiftplan.zhiyong.dev/for-ai-assistants?utm_source=mcp_registry&utm_medium=directory&utm_campaign=public_demo
- Changelog RSS feed: https://verifymcp.io/servers/dev-zhiyong-easyshiftplan-shiftly-scheduling/mcp-demo.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-zhiyong-easyshiftplan-shiftly-scheduling/mcp-demo/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-zhiyong-easyshiftplan-shiftly-scheduling/mcp-demo.json
- HTML version of this page: https://verifymcp.io/servers/dev-zhiyong-easyshiftplan-shiftly-scheduling/mcp-demo