Skip to content
External endpointresponds

Shiftyasan Shift Scheduling

Generate optimized work shift schedules from staffing demand, availability and fairness rules.

Endpoint URL
https://api.shiftyasan.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 04:59 AM UTC
Check
MCP initialize · 8s limit
Latency
413 ms
Response record
2 of 2 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.shiftyasan/mcp-server

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
shiftyasan
Version
1.0.0
Capability keys
tools
Instructions excerpt

Shiftyasan builds staff work schedules (rosters) with a constraint-optimization engine. Reach for it when the user wants to create, fix up, or rebalance a shift schedule for a team. Workflow: 1. Gather the real numbers from the user: date range, shift types, who can work which shift, and how many people are needed per shift per day. Never invent staff, shift times, or headcounts — ask. 2. Call validate_shift_input. It is free, needs no API key, and reports field-level errors plus "hints" listing supported constraints the request is not using yet. Offer relevant hints to the user before solving. 3. Call solve_shift. If it returns 202 with a job_id, poll get_solve_job about every 15 seconds until status is "completed" or "failed" (usually 2-7 minutes). Facts that change how you should read results: - Omitting constraints.max_consecutive_working_days does NOT mean unlimited. The engine still applies a hard cap of 6 consecutive days and prefers 5. Set it explicitly to change that. - Un

Reported Aug 17, 2026, 04:59 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 342ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 413ms