Rotase
REMOTE · ROTASE.COM
Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export.
Available components
Last scanned (5 hours ago)
Scores higher than 58% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Project Management
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. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 9% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 +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.
- 21 Oct 26 +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.
- 19 Oct 26 +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.
- 17 Oct 26 +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.
- 15 Oct 26 +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.
- 14 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Oct 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 24 Oct 2026 · Probed https://rotase.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=rotase.com | CN=home pl DV TLS G2 R36 CA,O=home.pl sp. z o.o.,C=PL | 9 Oct 2026 | 26 Apr 2027 | RSA 2048 | SHA256-RSA | 127bb94139d46cba7b71df3f667073ee |
| SANs: rotase.com, www.rotase.com | ||||||
| CN=home pl DV TLS G2 R36 CA,O=home.pl sp. z o.o.,C=PL (CA) | CN=Certum Trusted Root CA,OU=Certum Certification Authority,O=Asseco Data Systems S.A.,C=PL | 14 Jan 2026 | 2 Jan 2036 | RSA 4096 | SHA512-RSA | f453dcd31a9fe1f6564096ce96f05ba |
| CN=Certum Trusted Root CA,OU=Certum Certification Authority,O=Asseco Data Systems S.A.,C=PL (CA) | CN=Certum Trusted Root CA,OU=Certum Certification Authority,O=Asseco Data Systems S.A.,C=PL | 16 Mar 2018 | 16 Mar 2043 | RSA 4096 | SHA512-RSA | 1ebf5950b8c980374c06f7eb554fb5ed |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rotase.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| rotase.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rotase.com/mcp | Verified | 200 | |
| http (plaintext) | http://rotase.com/mcp | HTTPS enforced | 308 | https://rotase.com/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
rotase_check_feasibility Check schedule feasibility ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | array | – | – |
| employees | array | yes | – |
| monthlyTargets | array | – | – |
| preferences | array | – | – |
| project | object | yes | – |
| schedules | array | – | – |
| schemaVersion | string | – | – |
| store | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
rotase_create_demo_project Create a Rotase demo project ~172
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| optimization | object|null | – | – |
| project | object | – | – |
No examples provided.
rotase_examples Get Rotase examples ~81
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.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| employees | array | – | – |
| project | object | – | – |
| store | object | – | – |
No examples provided.
rotase_export_csv Export an employee schedule as CSV ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | array | – | – |
| employees | array | yes | – |
| monthlyTargets | array | – | – |
| preferences | array | – | – |
| project | object | yes | – |
| schedules | array | – | – |
| schemaVersion | string | – | – |
| store | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | string | – | – |
| csv | string | – | – |
| filename | string | – | – |
No examples provided.
rotase_generate_schedule Generate an employee schedule ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | array | – | – |
| employees | array | yes | – |
| monthlyTargets | array | – | – |
| preferences | array | – | – |
| project | object | yes | – |
| schedules | array | – | – |
| schemaVersion | string | – | – |
| store | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
rotase_health Check Rotase health ~43
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| phpVersion | string | – | – |
| service | string | – | – |
| status | string | – | – |
No examples provided.
rotase_schedule_report Create an employee schedule report ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | array | – | – |
| employees | array | yes | – |
| monthlyTargets | array | – | – |
| preferences | array | – | – |
| project | object | yes | – |
| schedules | array | – | – |
| schemaVersion | string | – | – |
| store | object | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| employees | array | – | – |
| store | object | – | – |
No examples provided.
rotase_validate_project Validate a Rotase project ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| availability | array | – | – |
| employees | array | yes | – |
| monthlyTargets | array | – | – |
| preferences | array | – | – |
| project | object | yes | – |
| schedules | array | – | – |
| schemaVersion | string | – | – |
| store | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
remote · rotase.com
claude mcp add --transport http com-rotase-rotase 'https://rotase.com/mcp'
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.