Rotase MCP server
com.rotase/rotaserotase.comstreamable-httpv1.0.0Scanned
Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export.
8 tools: 5 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
5 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Rotase MCP server can do
The Rotase MCP server is published by rotase.com, a domain the MCP Registry verified. It has 8 tools. It can create or change data (5 tools: rotase_create_demo_project, rotase_generate_schedule, rotase_check_feasibility, rotase_schedule_report and 1 more), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
8 tools
Changes things 5Claude Code: ask
rotase_check_feasibilityCheck whether a complete Rotase project can satisfy opening hours, staffing requirements, availability, rest rules and work-hour limits.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
rotase_create_demo_projectCreate a localized demonstration project using the same project-creation operation as the Rotase API.No findings
Why it is in this group
- The name "rotase_create_demo_project" says "create": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
rotase_export_csvExport a generated monthly schedule as spreadsheet-compatible CSV.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
rotase_generate_scheduleGenerate a monthly employee schedule from a complete Rotase project payload.1 finding
Why it is in this group
- The name "rotase_generate_schedule" says "generate": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "rotase_generate_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true}; The name "rotase_generate_schedule" says "generate": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
rotase_schedule_reportCalculate per-store and per-employee statistics for a generated monthly schedule.1 finding
Why it is in this group
- The name "rotase_schedule_report" says "schedule": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "rotase_schedule_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true}; The name "rotase_schedule_report" says "schedule": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
Only reads 3Show 3 read-only tools
rotase_examplesRead an example store, employees and complete project payload.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
rotase_healthRead-only check that the Rotase scheduling service is available.No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
rotase_validate_projectValidate a complete Rotase project payload without saving or modifying it.No findings
Why it is in this group
- The name "rotase_validate_project" says "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:46 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 5
- Protocol version
- 2025-03-26
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 5 tools that change things (5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://rotase.com/mcp: tools/list returned 8 tools to an anonymous client, including rotase_create_demo_project (write), rotase_generate_schedule (write), rotase_check_feasibility (write), rotase_schedule_report (write), rotase_export_csv (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "rotase_generate_schedule" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true}; The name "rotase_generate_schedule" says "generate": a word for a change.
The server marks "rotase_schedule_report" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true}; The name "rotase_schedule_report" says "schedule": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http rotase https://rotase.com/mcpclaude mcp add --transport http rotase https://rotase.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__rotase__rotase_health",
"mcp__rotase__rotase_examples",
"mcp__rotase__rotase_validate_project"
],
"ask": [
"mcp__rotase__rotase_create_demo_project",
"mcp__rotase__rotase_generate_schedule",
"mcp__rotase__rotase_check_feasibility",
"mcp__rotase__rotase_schedule_report",
"mcp__rotase__rotase_export_csv"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as rotase. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.rotase/rotase/verify?hash=bca23ebdbabe3c39dec6e0234e1bd239c31979bd8e974e2cee8e57568639cf7b" | jq -e '.changed == false'Pinned hash bca23ebdbabe, from Nov 14, 2026, 06:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.rotase/rotase/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.rotase/rotase)Source: MCP Registry. Synced Oct 21, 2026, 18:02 UTC.
Rotase MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Rotase MCP server safe?
- No scan can promise that. What its definitions show: 8 tools, 5 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Rotase MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Rotase MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Rotase MCP server have?
- 8 tools: 5 write, 3 read. rotase_create_demo_project, rotase_generate_schedule, rotase_check_feasibility, rotase_schedule_report, rotase_export_csv, rotase_health, rotase_examples and rotase_validate_project.
Does the Rotase MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Rotase MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Rotase MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.