protogrid

Search / com.rotase/rotase

Rotase

R0· no sign-in

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

v1.0.0 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality81new
Trust83of 100
Uptime, 30 days100%
Latency p50717 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "rotase": {
      "type": "http",
      "url": "https://rotase.com/mcp"
    }
  }
}
claude mcp add --transport http rotase https://rotase.com/mcp
[mcp_servers.rotase]
url = "https://rotase.com/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rotase": {
      "type": "remote",
      "url": "https://rotase.com/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "rotase": {
      "type": "http",
      "url": "https://rotase.com/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=rotase&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vcm90YXNlLmNvbS9tY3AifQ%3D%3D"
}
{
  "servers": {
    "rotase": {
      "type": "http",
      "url": "https://rotase.com/mcp"
    }
  }
}
{
  "mcpServers": {
    "rotase": {
      "httpUrl": "https://rotase.com/mcp"
    }
  }
}
extensions:
  "rotase":
    enabled: true
    name: "rotase"
    type: streamable_http
    uri: "https://rotase.com/mcp"
    timeout: 300

Quality 81 / 100new

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene86 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • pass
    tools.annotations8 of 8 tools declare readOnlyHint or destructiveHint
  • fail
    tools.directory_hintsno 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_costabout 1,894 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stabilityn/a · weight 15
  • n/a
    stability.changes, stability.rug_pulltool history recorded for 6 of the 7 days needed
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

8 tools, about 1,894 tokens to load them all · tool set 6bdabade7982 · checked 2026-10-20 11:08 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 83 / 100

no-repository
provenance55
liveness100
freshness100
hygiene80

+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. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://rotase.com/mcp streamable-httpnoneyes100%717 ms2025-03-262026-10-20

Tools (8)

rotase_check_feasibilityread-onlyCheck 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_projectCreate 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_examplesread-onlyRead 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_csvread-onlyExport 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_scheduleread-onlyGenerate 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_healthread-onlyRead-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_reportread-onlyCalculate 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_projectread-onlyValidate 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.

Schemas: list_tools.

Similar MCP servers

Official server.json
{
  "name": "com.rotase/rotase",
  "title": "Rotase",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://rotase.com/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "websiteUrl": "https://rotase.com",
  "description": "Employee scheduling, staffing feasibility, localized demos, schedule reports and CSV export."
}