dev.zhiyong.easyshiftplan/shiftly-scheduling

Est-ce que dev.zhiyong.easyshiftplan/shiftly-scheduling est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.zhiyong.easyshiftplan/shiftly-scheduling » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 5 outils

• get_demo_feedback_reply≈ 303 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • feedback_reference · string · requis
    Exact 24-character reference returned by a successful submit_demo_feedback call. Required for this optional lookup; never invent it.

  Exemple d'appel

  {"name": "get_demo_feedback_reply", "arguments": {"feedback_reference": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"reply": "texte", "status": "waiting", "message": "texte", "next_action": "texte"}}

• get_public_product_info≈ 452 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • industry · string · optionnel · auto-repair | clinic | restaurant | retail | warehouse
    Business type used to select the most relevant official EasyShiftPlan page and example; defaults to restaurant.

  Exemple d'appel

  {"name": "get_public_product_info", "arguments": {"industry": "auto-repair"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"link": "texte", "name": "texte", "pricing": {}, "summary": "texte", "category": "texte", "good_fit": [], "next_steps": {}, "agent_sharing": {}, "agent_discovery": {}, "manager_controls": "texte", "sharing_guidance": "texte", "agent_capabilities": []}}

• prepare_share_draft≈ 591 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • channel · string · optionnel · community_reply | directory_listing | requested_share
    Intended format: a relevant community reply, a product-directory description, or a link someone specifically requested.
  • industry · string · optionnel · auto-repair | clinic | restaurant | retail | warehouse
    Small-business industry the draft should address.
  • language · string · optionnel · en | zh | ar
    Language for the draft and its promotional disclosure.
  • user_requested · boolean · requis
    Required confirmation that the user explicitly asked for promotional copy or sharing help. Do not call this tool without that request.

  Exemple d'appel

  {"name": "prepare_share_draft", "arguments": {"user_requested": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "draft": "texte", "channel": "community_reply", "industry": "auto-repair", "language": "en", "tracking_note": "texte", "sent_or_posted": true, "sharing_reminder": "texte", "publication_status": "texte"}}

• run_public_demo≈ 1690 tokens

  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.

  Paramètres, retour & exemple (9)

  Paramètres

  • demands · array · optionnel
    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 · optionnel · auto-repair | clinic | restaurant | retail | warehouse
    Business type used to select the fictional sample team and shift templates.
  • team_size · integer · optionnel
    Number of synthetic workers, from 4 to 12; defaults to the selected industry's sample size.
  • period_mode · string · optionnel · week | month
    Schedule length: week or month. Defaults to one week.
  • period_start · string · optionnel
    Optional date in YYYY-MM-DD format inside the requested week or month; otherwise the next full period is selected.
  • manager_request · string · optionnel
    Optional natural-language scheduling instructions for this fictional team only. Ambiguous requests stop for review; never include real staff or business data.
  • coverage_per_shift · integer · optionnel
    Workers required on each enabled shift for each operating day.
  • time_limit_seconds · number · optionnel
    Solver time budget, from 0.1 to 10 seconds. Defaults to 2 seconds.
  • operating_days_per_week · integer · optionnel
    Number of open days, starting Monday. For example, 5 means Monday through Friday.

  Exemple d'appel

  {"name": "run_public_demo", "arguments": {"demands": [], "industry": "auto-repair", "team_size": 1, "period_mode": "week", "period_start": "texte", "manager_request": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"demo": {}, "store": {}, "period": {}, "privacy": "texte", "scenario": {}, "workflow": {}, "quality_check": {}, "parsed_request": {}, "schedule_preview": {}, "proposed_settings": {}, "feedback_next_step": "texte", "optional_discovery": {}}}

• submit_demo_feedback≈ 583 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • message · string · requis
    Assistant-authored, generalized observation of product behavior actually seen. Describe the product, not the user's words, roster or private details.
  • category · string · optionnel · open_note | worked_well | confusing | incorrect_result | missing_capability | other
    Optional triage label; use open_note for a free-form product observation.
  • related_tool · string · optionnel · | get_public_product_info | prepare_share_draft | run_public_demo | submit_demo_feedback | get_demo_feedback_reply
    Optional public demo tool related to this note. Leave blank for general feedback or feedback sent before a demo.

  Exemple d'appel

  {"name": "submit_demo_feedback", "arguments": {"message": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"status": "texte", "message": "texte", "next_action": {}, "retention_days": 1, "feedback_reference": "texte"}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://easyshiftplan.zhiyong.dev/mcp/demo