Skip to content

RotaCloud MCP by usefulapi

io.usefulapi/rotacloudusefulapi.iostreamable-httpv1.32.5Scanned

Read RotaCloud shifts, attendance, leave, availability and payroll; create shifts and handle leave.

28 tools: 7 can delete or cancel things and 21 only read.

Tools: 7 delete, 0 irreversible, 0 write, 21 read.
  • Reads private data · 5
  • Reads text others write · 1
  • Can send data out · 1
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

7 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the RotaCloud MCP by usefulapi can do

The RotaCloud MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 28 tools. It can delete or cancel things (7 tools: rotacloud_create_shift, rotacloud_update_shift, rotacloud_publish_shifts, rotacloud_delete_shifts and 3 more). 21 tools only read.

5 tools read private data (rotacloud_list_users, rotacloud_list_locations, rotacloud_list_shifts and 2 more); 1 tool brings in text other people can write (rotacloud_list_leave_requests); 1 tool can send data out of your system (rotacloud_publish_shifts). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its tools changed once since Anlyon Radar first saw them.

Last scanned Oct 25, 2026, version 1.32.5.

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.

28 tools

Deletes or cancels 7Claude Code: deny
  • rotacloud_approve_leave_requestWRITE: approve a pending leave request (it becomes booked leave and the employee is notified).No findings

    Why it is in this group

    • The name "rotacloud_approve_leave_request" says "approve": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: approve a pending leave request (it becomes booked leave and the employee is notified). POST /leave_requests/{id}/approve.

    Annotations the server declares

    • title: Approve leave request
    • destructiveHint: true
    • idempotentHint: true
  • rotacloud_create_leave_requestWRITE: submit a leave request on behalf of an employee (sent as that user, for a manager to approve).No findings

    Why it is in this group

    • The name "rotacloud_create_leave_request" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: submit a leave request on behalf of an employee (sent as that user, for a manager to approve). POST /leave_requests with the User header.

    Annotations the server declares

    • title: Request leave
    • destructiveHint: true
  • rotacloud_create_shiftWRITE: create a shift on the rota.No findings

    Why it is in this group

    • The name "rotacloud_create_shift" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: create a shift on the rota. Leave user_id out for an open shift. Unpublished by default (employees see it once published). POST /shifts.

    Annotations the server declares

    • title: Create shift
    • destructiveHint: true
  • rotacloud_delete_shiftsWRITE — deletes shifts from the rota (assigned employees lose the shift).No findings

    Why it is in this group

    • The name "rotacloud_delete_shifts" says "delete": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE — deletes shifts from the rota (assigned employees lose the shift). Delete 1-100 shifts by id; select them first with rotacloud_find_shifts. Without confirm it only previews: it reads each shift and deletes nothing. Show the preview to the user, then call again with confirm: true. Guards re-check each shift right before its delete and skip it if it no longer qualifies: require_open (skip assigned shifts), require_shorter_than_minutes (skip shifts whose elapsed duration is not strictly less). After each delete the shift is read again to verify it is gone. DELETE /shifts/{id}.

    Annotations the server declares

    • title: Delete shifts
    • destructiveHint: true
    • idempotentHint: true
  • rotacloud_deny_leave_requestWRITE: deny a pending leave request (the employee is notified).No findings

    Why it is in this group

    • The name "rotacloud_deny_leave_request" says "request": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: deny a pending leave request (the employee is notified). POST /leave_requests/{id}/deny.

    Annotations the server declares

    • title: Deny leave request
    • destructiveHint: true
    • idempotentHint: true
  • rotacloud_publish_shiftsWRITE: publish shifts so the assigned employees see them (and get notified).Can send data outNo findings

    Why it is in this group

    • The name "rotacloud_publish_shifts" says "publish": a word for a change that another call does not undo.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • outboundThe name "rotacloud_publish_shifts" says "publish": it sends or publishes something to other people.
    Description, as the server wrote it
    WRITE: publish shifts so the assigned employees see them (and get notified). POST /shifts_published.

    Annotations the server declares

    • title: Publish shifts
    • destructiveHint: true
    • idempotentHint: true
  • rotacloud_update_shiftWRITE: change a shift's times, assignee, location, role, break, notes or published state.No findings

    Why it is in this group

    • The name "rotacloud_update_shift" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    WRITE: change a shift's times, assignee, location, role, break, notes or published state. Only the fields you pass change. POST /shifts/{id}.

    Annotations the server declares

    • title: Update shift
    • destructiveHint: true
    • idempotentHint: true
Only reads 21Show 21 read-only tools
  • rotacloud_find_shiftsFind shifts in a time range by open/assigned state, published state, location, role and ELAPSED duration (end − start; the break is not subtracted).No findings

    Why it is in this group

    • The name "rotacloud_find_shifts" says "find": a word for reading.
    Description, as the server wrote it
    Find shifts in a time range by open/assigned state, published state, location, role and ELAPSED duration (end − start; the break is not subtracted). It reads page after page, so it is the way to select shifts for a bulk change such as rotacloud_delete_shifts: e.g. open shifts shorter than 3 hours = open: true, shorter_than_minutes: 180 (a shift of exactly 180 minutes does not match). Deleted shifts never match. Returns up to max_results matches (shift_ids plus a summary each: UTC times, elapsed_minutes, user, location, role, published). complete: true = the whole range was read. Otherwise pass next_offset as offset to continue — but after deleting or changing shifts, search again from offset 0, because the list positions move. GET /shifts.

    Annotations the server declares

    • title: Find shifts
    • readOnlyHint: true
  • rotacloud_get_availabilityEmployees' availability per date in a range (available / unavailable times).No findings

    Why it is in this group

    • The name "rotacloud_get_availability" says "get": a word for reading.
    Description, as the server wrote it
    Employees' availability per date in a range (available / unavailable times). GET /availability.

    Annotations the server declares

    • title: Get availability
    • readOnlyHint: true
  • rotacloud_get_leave_requestOne leave request by id, with the per-day breakdown.No findings

    Why it is in this group

    • The name "rotacloud_get_leave_request" says "get": a word for reading.
    Description, as the server wrote it
    One leave request by id, with the per-day breakdown. GET /leave_requests/{id}.

    Annotations the server declares

    • title: Get leave request
    • readOnlyHint: true
  • rotacloud_get_payrollPayroll for one pay period, per employee: pay settings, attendance worked, paid/unpaid leave, overtime and pay totals.No findings

    Why it is in this group

    • The name "rotacloud_get_payroll" says "get": a word for reading.
    Description, as the server wrote it
    Payroll for one pay period, per employee: pay settings, attendance worked, paid/unpaid leave, overtime and pay totals. Contains pay data. GET /pay_periods/{id}/payroll.

    Annotations the server declares

    • title: Get payroll for a pay period
    • readOnlyHint: true
  • rotacloud_get_shiftOne shift by id.No findings

    Why it is in this group

    • The name "rotacloud_get_shift" says "get": a word for reading.
    Description, as the server wrote it
    One shift by id. GET /shifts/{id}.

    Annotations the server declares

    • title: Get shift
    • readOnlyHint: true
  • rotacloud_get_userOne employee by id.No findings

    Why it is in this group

    • The name "rotacloud_get_user" says "get": a word for reading.
    Description, as the server wrote it
    One employee by id. GET /users/{id}.

    Annotations the server declares

    • title: Get user
    • readOnlyHint: true
  • rotacloud_list_accountsThe RotaCloud account(s) this API key belongs to: name, plan, time zone, employee count.No findings

    Why it is in this group

    • The name "rotacloud_list_accounts" says "list": a word for reading.
    Description, as the server wrote it
    The RotaCloud account(s) this API key belongs to: name, plan, time zone, employee count. GET /accounts.

    Annotations the server declares

    • title: List accounts
    • readOnlyHint: true
  • rotacloud_list_attendanceList time & attendance records (clock-in/out times, breaks, minutes late, hours, approval state) in a time range.No findings

    Why it is in this group

    • The name "rotacloud_list_attendance" says "list": a word for reading.
    Description, as the server wrote it
    List time & attendance records (clock-in/out times, breaks, minutes late, hours, approval state) in a time range. GET /attendance.

    Annotations the server declares

    • title: List attendance records
    • readOnlyHint: true
  • rotacloud_list_clocked_inWho is clocked in right now: user, location, role, clock-in time, minutes late and break state.No findings

    Why it is in this group

    • The name "rotacloud_list_clocked_in" says "list": a word for reading.
    Description, as the server wrote it
    Who is clocked in right now: user, location, role, clock-in time, minutes late and break state. GET /users_clocked_in.

    Annotations the server declares

    • title: List clocked-in users
    • readOnlyHint: true
  • rotacloud_list_day_notesList day notes (notices pinned to rota dates, e.g.Reads private dataNo findings

    Why it is in this group

    • The name "rotacloud_list_day_notes" says "list": a word for reading.

    What it can reach

    • private-dataThe name "rotacloud_list_day_notes" says "list" and "note": it reads notes.
    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    Description, as the server wrote it
    List day notes (notices pinned to rota dates, e.g. events or deliveries), optionally for one location. GET /day_notes.

    Annotations the server declares

    • title: List day notes
    • readOnlyHint: true
  • rotacloud_list_days_offEmployees' scheduled days off per date in a range.No findings

    Why it is in this group

    • The name "rotacloud_list_days_off" says "list": a word for reading.
    Description, as the server wrote it
    Employees' scheduled days off per date in a range. GET /days_off.

    Annotations the server declares

    • title: List days off
    • readOnlyHint: true
  • rotacloud_list_holiday_allowancesEvery employee's holiday allowance for a leave year (default and custom allowance, unit, carried over).No findings

    Why it is in this group

    • The name "rotacloud_list_holiday_allowances" says "list": a word for reading.
    Description, as the server wrote it
    Every employee's holiday allowance for a leave year (default and custom allowance, unit, carried over). GET /holiday_allowances/{year}.

    Annotations the server declares

    • title: List holiday allowances
    • readOnlyHint: true
  • rotacloud_list_leaveList booked leave (holiday, sickness, etc.) with type, user, dates, hours and status.No findings

    Why it is in this group

    • The name "rotacloud_list_leave" says "list": a word for reading.
    Description, as the server wrote it
    List booked leave (holiday, sickness, etc.) with type, user, dates, hours and status. Filter by date range or leave year, users and leave types; pending/denied/expired requests are excluded unless asked for. GET /leave.

    Annotations the server declares

    • title: List leave
    • readOnlyHint: true
  • rotacloud_list_leave_requestsList leave requests awaiting a decision (and past ones): user, leave type, dates, half days, the employee's message.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "rotacloud_list_leave_requests" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "message": it reads messages.
    • untrusted-inputThe description's first sentence says "list" and "message": it reads messages, which other people can write.
    Description, as the server wrote it
    List leave requests awaiting a decision (and past ones): user, leave type, dates, half days, the employee's message. GET /leave_requests.

    Annotations the server declares

    • title: List leave requests
    • readOnlyHint: true
  • rotacloud_list_leave_typesList leave types (Holiday, Sickness, Unpaid, ...) with id, short name and whether employees can request them.No findings

    Why it is in this group

    • The name "rotacloud_list_leave_types" says "list": a word for reading.
    Description, as the server wrote it
    List leave types (Holiday, Sickness, Unpaid, ...) with id, short name and whether employees can request them. GET /leave_types.

    Annotations the server declares

    • title: List leave types
    • readOnlyHint: true
  • rotacloud_list_locationsList locations (sites/branches) with address, time zone and managers.Reads private dataNo findings

    Why it is in this group

    • The name "rotacloud_list_locations" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "branch": it reads repositories.
    Description, as the server wrote it
    List locations (sites/branches) with address, time zone and managers. GET /locations.

    Annotations the server declares

    • title: List locations
    • readOnlyHint: true
  • rotacloud_list_pay_periodsList pay periods overlapping a date range (id, name, start/end date, locked).No findings

    Why it is in this group

    • The name "rotacloud_list_pay_periods" says "list": a word for reading.
    Description, as the server wrote it
    List pay periods overlapping a date range (id, name, start/end date, locked). GET /pay_periods.

    Annotations the server declares

    • title: List pay periods
    • readOnlyHint: true
  • rotacloud_list_rolesList job roles (positions) with colour, default break and pay rate.No findings

    Why it is in this group

    • The name "rotacloud_list_roles" says "list": a word for reading.
    Description, as the server wrote it
    List job roles (positions) with colour, default break and pay rate. GET /roles.

    Annotations the server declares

    • title: List roles
    • readOnlyHint: true
  • rotacloud_list_shiftsList rota shifts in a time range: start/end times (Unix seconds), break, assigned user (null = open shift), location, role, notes, published and acknowledged state.Reads private dataNo findings

    Why it is in this group

    • The name "rotacloud_list_shifts" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "note": it reads notes.
    Description, as the server wrote it
    List rota shifts in a time range: start/end times (Unix seconds), break, assigned user (null = open shift), location, role, notes, published and acknowledged state. Filter by users, locations, roles, open or published. GET /shifts.

    Annotations the server declares

    • title: List shifts
    • readOnlyHint: true
  • rotacloud_list_swap_requestsList shift swap requests with their status, the shifts and the users involved.No findings

    Why it is in this group

    • The name "rotacloud_list_swap_requests" says "list": a word for reading.
    Description, as the server wrote it
    List shift swap requests with their status, the shifts and the users involved. GET /swap_requests.

    Annotations the server declares

    • title: List shift swap requests
    • readOnlyHint: true
  • rotacloud_list_usersList employees (users) with their level, roles, locations, contact details and pay settings.Reads private dataNo findings

    Why it is in this group

    • The name "rotacloud_list_users" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    List employees (users) with their level, roles, locations, contact details and pay settings. Use it to map user ids in shifts, leave and attendance to names. GET /users.

    Annotations the server declares

    • title: List users
    • readOnlyHint: 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.

5 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 outbound tool breaks every one.

Reads private data5
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out1
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
deny to break every path
{
  "permissions": {
    "deny": [
      "mcp__rotacloud__rotacloud_publish_shifts"
    ]
  }
}

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.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
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

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://rotacloud.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://rotacloud.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 6 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://rotacloud.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://rotacloud.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed
  2. Tools2 added.+2 addedView diff

Install

Pinned to version 1.32.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http rotacloud https://rotacloud.usefulapi.io/mcp
claude mcp add --transport http rotacloud https://rotacloud.usefulapi.io/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__rotacloud__rotacloud_list_accounts",
      "mcp__rotacloud__rotacloud_list_users",
      "mcp__rotacloud__rotacloud_get_user",
      "mcp__rotacloud__rotacloud_list_locations",
      "mcp__rotacloud__rotacloud_list_roles",
      "mcp__rotacloud__rotacloud_list_shifts",
      "mcp__rotacloud__rotacloud_get_shift",
      "mcp__rotacloud__rotacloud_list_swap_requests",
      "mcp__rotacloud__rotacloud_list_day_notes",
      "mcp__rotacloud__rotacloud_list_attendance",
      "mcp__rotacloud__rotacloud_list_clocked_in",
      "mcp__rotacloud__rotacloud_list_leave",
      "mcp__rotacloud__rotacloud_list_leave_requests",
      "mcp__rotacloud__rotacloud_get_leave_request",
      "mcp__rotacloud__rotacloud_list_leave_types",
      "mcp__rotacloud__rotacloud_list_holiday_allowances",
      "mcp__rotacloud__rotacloud_get_availability",
      "mcp__rotacloud__rotacloud_list_days_off",
      "mcp__rotacloud__rotacloud_list_pay_periods",
      "mcp__rotacloud__rotacloud_get_payroll",
      "mcp__rotacloud__rotacloud_find_shifts"
    ],
    "ask": [],
    "deny": [
      "mcp__rotacloud__rotacloud_create_shift",
      "mcp__rotacloud__rotacloud_update_shift",
      "mcp__rotacloud__rotacloud_publish_shifts",
      "mcp__rotacloud__rotacloud_delete_shifts",
      "mcp__rotacloud__rotacloud_create_leave_request",
      "mcp__rotacloud__rotacloud_approve_leave_request",
      "mcp__rotacloud__rotacloud_deny_leave_request"
    ]
  }
}

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 rotacloud. Review it before you use it.

Capability tags behind 6 rules
  • mcp__rotacloud__rotacloud_list_users private-data
  • mcp__rotacloud__rotacloud_list_locations private-data
  • mcp__rotacloud__rotacloud_list_shifts private-data
  • mcp__rotacloud__rotacloud_list_day_notes private-data
  • mcp__rotacloud__rotacloud_list_leave_requests private-data, untrusted-input
  • mcp__rotacloud__rotacloud_publish_shifts outbound

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/io.usefulapi/rotacloud/verify?hash=2d9ab29310e7e8d67b3be7cf24eaa1a2b356b3fb521dbc2210f2a1a82711e622" | jq -e '.changed == false'

Pinned hash 2d9ab29310e7, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/rotacloud/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/rotacloud
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/rotacloud.svg)](https://radar.anlyon.com/servers/io.usefulapi/rotacloud)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

RotaCloud MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the RotaCloud MCP by usefulapi safe?

No scan can promise that. What its definitions show: 28 tools, 7 of which can change, send or delete something, and 0 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 RotaCloud MCP by usefulapi delete data?

Yes. 7 tools can delete, cancel or revoke something: rotacloud_create_shift, rotacloud_update_shift, rotacloud_publish_shifts, rotacloud_delete_shifts, rotacloud_create_leave_request, rotacloud_approve_leave_request and 1 more.

Can the RotaCloud MCP by usefulapi 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 RotaCloud MCP by usefulapi have?

28 tools: 7 destructive, 21 read. rotacloud_create_shift, rotacloud_update_shift, rotacloud_publish_shifts, rotacloud_delete_shifts, rotacloud_create_leave_request, rotacloud_approve_leave_request, rotacloud_deny_leave_request, rotacloud_list_accounts and 20 more.

Does the RotaCloud MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the RotaCloud MCP by usefulapi send data to outside services?

1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): rotacloud_publish_shifts.

Has the RotaCloud MCP by usefulapi changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Oct 25, 2026. Every change is on this page and in its Atom feed.