# Rotase (remote · rotase.com)

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

- Trust score: 69/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-24

## Components

- remote · `rotase.com`: 69/100 (this document), [markdown](https://verifymcp.io/servers/com-rotase-rotase/rotase.md), [page](https://verifymcp.io/servers/com-rotase-rotase/rotase)

## Channel facts

- Endpoint: `https://rotase.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

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

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1204 tokens (~150/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 74/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 9% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### How do I install the Rotase MCP server?

Rotase is a hosted endpoint at https://rotase.com/mcp, 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 com-rotase-rotase 'https://rotase.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-rotase-rotase": {
      "url": "https://rotase.com/mcp"
    }
  }
}
```

### VS Code

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

### Codex

```toml
[mcp_servers.com-rotase-rotase]
url = "https://rotase.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-rotase-rotase": {
      "type": "remote",
      "url": "https://rotase.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-rotase-rotase --url 'https://rotase.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-rotase-rotase:
    url: "https://rotase.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-rotase-rotase": {
      "Transport": "http",
      "Url": "https://rotase.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-rotase-rotase -t streamable-http -u 'https://rotase.com/mcp'
```

### Other

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

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-10-24 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-19 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-17 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-15 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

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

- [functional improvement] Stability: unverified → 0.03

### 2026-10-13 (score 64)

First indexed and scored.

## MCP tools (8)

### `rotase_health` (~43 tokens)

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

Output parameters:

- `phpVersion` (string)
- `service` (string)
- `status` (string)

### `rotase_examples` (~81 tokens)

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

Input parameters:

- `language` (string)

Output parameters:

- `employees` (array)
- `project` (object)
- `store` (object)

### `rotase_create_demo_project` (~172 tokens)

Create a Rotase 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.

Input parameters:

- `closeOnHolidays` (boolean)
- `country` (string): ISO country code, for example PL, DE, GB or US.
- `kind` (string)
- `language` (string): Demo language code, for example en, pl, de, fr or es.
- `region` (string|null): Optional region code supported by the selected country.
- `timezone` (string): IANA timezone, for example Europe/Warsaw.

Output parameters:

- `optimization` (object|null)
- `project` (object)

### `rotase_validate_project` (~121 tokens)

Validate a Rotase 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.

Input parameters:

- `availability` (array)
- `employees` (array, required)
- `monthlyTargets` (array)
- `preferences` (array)
- `project` (object, required)
- `schedules` (array)
- `schemaVersion` (string)
- `store` (object, required)

### `rotase_generate_schedule` (~136 tokens)

Generate an employee 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.

Input parameters:

- `availability` (array)
- `employees` (array, required)
- `monthlyTargets` (array)
- `preferences` (array)
- `project` (object, required)
- `schedules` (array)
- `schemaVersion` (string)
- `store` (object, required)

### `rotase_check_feasibility` (~127 tokens)

Check schedule 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.

Input parameters:

- `availability` (array)
- `employees` (array, required)
- `monthlyTargets` (array)
- `preferences` (array)
- `project` (object, required)
- `schedules` (array)
- `schemaVersion` (string)
- `store` (object, required)

### `rotase_schedule_report` (~121 tokens)

Create an employee 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.

Input parameters:

- `availability` (array)
- `employees` (array, required)
- `monthlyTargets` (array)
- `preferences` (array)
- `project` (object, required)
- `schedules` (array)
- `schemaVersion` (string)
- `store` (object, required)

Output parameters:

- `employees` (array)
- `store` (object)

### `rotase_export_csv` (~120 tokens)

Export an employee schedule as 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.

Input parameters:

- `availability` (array)
- `employees` (array, required)
- `monthlyTargets` (array)
- `preferences` (array)
- `project` (object, required)
- `schedules` (array)
- `schemaVersion` (string)
- `store` (object, required)

Output parameters:

- `contentType` (string)
- `csv` (string)
- `filename` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-rotase-rotase/rotase#diagnostics

## Score history

- 2026-10-24: 69
- 2026-10-23: 68
- 2026-10-22: 68
- 2026-10-21: 68
- 2026-10-20: 67
- 2026-10-19: 67
- 2026-10-18: 66
- 2026-10-17: 66
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 64

## Common questions

### What is the Rotase MCP server?

Rotase is an MCP server listed in the public MCP registry as com.rotase/rotase. Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export. This page covers its hosted endpoint (https://rotase.com/mcp).

### Is the Rotase MCP server safe to use?

Rotase scores 69 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 Rotase MCP server expose?

Rotase exposes 8 tools: rotase_health, rotase_examples, rotase_create_demo_project, rotase_validate_project, rotase_generate_schedule, and 3 more. Their descriptions and schemas cost roughly 921 tokens of context every time the server is loaded.

### Does the Rotase MCP server require authentication?

No. We connected to Rotase without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Rotase MCP server still maintained?

Rotase is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://rotase.com/mcp
- Website: https://rotase.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-rotase-rotase/rotase.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-rotase-rotase/rotase.json
- HTML version of this page: https://verifymcp.io/servers/com-rotase-rotase/rotase