# Rotase

> Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export.

- name: com.rotase/rotase
- version: 1.0.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 81/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.rotase%2Frotase
- tools: https://api.protogrid.dev/v1/servers/com.rotase%2Frotase/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "rotase": {
      "type": "http",
      "url": "https://rotase.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-7d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 81/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 86 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: rotase_health (openWorldHint); rotase_examples (openWorldHint); rotase_create_demo_project (openWorldHint); …
- pass `tools.token_cost`: about 1,894 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 6 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 8, about 1,894 tokens to load them all
- tool set hash: 6bdabade798229ab71450f48f768ab35
- badge: [![protogrid quality](https://protogrid.dev/badge/com.rotase/rotase.svg)](https://protogrid.dev/servers/com.rotase/rotase)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://rotase.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (8)

- `rotase_check_feasibility`: Check whether a complete Rotase project can satisfy opening hours, staffing requirements, availability, rest rules and work-hour limits. Use after rotase_validate_project and before generation when the user asks whether a schedule is possible. This operation is read-only and does not save or modify the project.
- `rotase_create_demo_project`: Create a localized demonstration project using the same project-creation operation as the Rotase API. The server chooses the current period in the requested timezone, loads the localized demo names and company name, applies the selected country calendar and can generate an initial schedule. The result is returned in the response; nothing is saved on the server or in a browser.
- `rotase_examples`: Read an example store, employees and complete project payload. Defaults to English labels; pass a supported language code to localize names. Call this when the project structure or field names are unknown. The returned project can be copied and edited before validation. This operation is read-only and does not access a user browser or saved project.
- `rotase_export_csv`: Export a generated monthly schedule as spreadsheet-compatible CSV. Pass the complete project object and either provide the generated schedule as the top-level "schedule" property or put it in the project schedules array. The response contains the CSV text; nothing is saved on the server.
- `rotase_generate_schedule`: Generate a monthly employee schedule from a complete Rotase project payload. Use rotase_examples to obtain a template, then rotase_validate_project first. The operation calculates and returns a schedule; it does not save a project, modify browser storage or create an account. Explain returned violations or shortages instead of assuming that every project is schedulable.
- `rotase_health`: Read-only check that the Rotase scheduling service is available. Use this when connectivity or service availability is uncertain. It does not require a project and does not change data.
- `rotase_schedule_report`: Calculate per-store and per-employee statistics for a generated monthly schedule. Pass the complete project object and either provide the generated schedule as the top-level "schedule" property or put it in the project schedules array. This operation is read-only and does not save data.
- `rotase_validate_project`: Validate a complete Rotase project payload without saving or modifying it. Use rotase_examples first if the payload shape is unknown. Call this before feasibility checks or schedule generation. The input is the project object itself, not a wrapper with an additional "project" property.