RotaCloud MCP by usefulapi
REMOTE · ROTACLOUD.USEFULAPI.IO
Read RotaCloud shifts, attendance, leave, availability and payroll; create shifts and handle leave.
Available components
Last scanned (22 hours ago)
Scores higher than 47% of remote servers
Reachable. Last reached 16 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 Security78
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3618 tokens (~139/item across 26 items; 26 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "rotacloud_list_pay_periods" implies "pay" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 27 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; 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.
- 15 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +2
- The server rewrote its instructions, which are the text every model session reads security
- The server now declares the “prompts” capability functional
- First check of Schema quality: 100 functional
- New prompt “getting_started” functional
- Server version: 1.4.0 → 1.5.0 functional
- 13 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 59
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 16 Oct 2026 · Probed https://rotacloud.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of rotacloud.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 302 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://rotacloud.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://rotacloud.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://rotacloud.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://rotacloud.usefulapi.io/mcp |
| Authorisation server | https://rotacloud.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://rotacloud.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/rotacloud/ |
| http (plaintext) | http://rotacloud.usefulapi.io/mcp | Inconclusive | 302 | http://rotacloud.usefulapi.io/mcp |
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 →
rotacloud_approve_leave_request Approve leave request ~63
WRITE: approve a pending leave request (it becomes booked leave and the employee is notified). POST /leave_requests/{id}/approve.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_message | string | – | Message to the employee. |
| request_id | integer | yes | Leave request id. |
No output schema declared.
No examples provided.
rotacloud_create_leave_request Request leave ~175
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_am_pm | string | – | 'am' ends at midday (half day); default 'pm'. |
| end_date | string | yes | Last day (yyyy-mm-dd). |
| leave_type_id | integer | yes | Leave type id (see rotacloud_list_leave_types; must be requestable). |
| message | string | – | Message from the employee to the manager. |
| start_am_pm | string | – | 'pm' starts at midday (half day); default 'am'. |
| start_date | string | yes | First day (yyyy-mm-dd). |
| user_id | integer | yes | The employee requesting leave (the request is made as this user). |
No output schema declared.
No examples provided.
rotacloud_create_shift Create shift ~246
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | – | yes | Unix timestamp (seconds), an ISO 8601 date (2026-10-12 = 00:00 UTC) or an ISO 8601 date-time with a time zone (2026-10-12T09:00:00+01:00 or ...Z). |
| location_id | integer | yes | Location id. |
| minutes_break | integer | – | Unpaid break in minutes. |
| notes | string | – | Shift notes shown to the employee. |
| published | boolean | – | Publish immediately (default false). |
| role_id | integer | – | Role id. |
| start_time | – | yes | Unix timestamp (seconds), an ISO 8601 date (2026-10-12 = 00:00 UTC) or an ISO 8601 date-time with a time zone (2026-10-12T09:00:00+01:00 or ...Z). |
| user_id | integer | – | Assigned user id; omit for an open shift. |
No output schema declared.
No examples provided.
rotacloud_deny_leave_request Deny leave request ~59
WRITE: deny a pending leave request (the employee is notified). POST /leave_requests/{id}/deny.
| Name | Type | Req | Description |
|---|---|---|---|
| admin_message | string | – | Reason shown to the employee. |
| request_id | integer | yes | Leave request id. |
No output schema declared.
No examples provided.
rotacloud_get_availability Get availability ~122
Employees' availability per date in a range (available / unavailable times). GET /availability.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | Last date (yyyy-mm-dd). |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| start | string | yes | First date (yyyy-mm-dd). |
| users | array | – | Only these user ids. |
No output schema declared.
No examples provided.
rotacloud_get_leave_request Get leave request ~42
One leave request by id, with the per-day breakdown. GET /leave_requests/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | integer | yes | Leave request id. |
No output schema declared.
No examples provided.
rotacloud_get_payroll Get payroll for a pay period ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| pay_period_id | integer | yes | Pay period id (from rotacloud_list_pay_periods). |
No output schema declared.
No examples provided.
rotacloud_get_shift Get shift ~36
One shift by id. GET /shifts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| shift_id | integer | yes | RotaCloud shift id. |
No output schema declared.
No examples provided.
rotacloud_get_user Get user ~35
One employee by id. GET /users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | yes | RotaCloud user id. |
No output schema declared.
No examples provided.
rotacloud_list_accounts List accounts ~93
The RotaCloud account(s) this API key belongs to: name, plan, time zone, employee count. GET /accounts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
rotacloud_list_attendance List attendance records ~283
List time & attendance records (clock-in/out times, breaks, minutes late, hours, approval state) in a time range. GET /attendance.
| Name | Type | Req | Description |
|---|---|---|---|
| approved | boolean | – | true = only approved records, false = only unapproved. |
| end | – | yes | Unix timestamp (seconds), an ISO 8601 date (2026-10-12 = 00:00 UTC) or an ISO 8601 date-time with a time zone (2026-10-12T09:00:00+01:00 or ...Z). |
| include_deleted | boolean | – | Include deleted records. |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| locations | array | – | Only these location ids. |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| roles | array | – | Only these role ids. |
| start | – | yes | Unix timestamp (seconds), an ISO 8601 date (2026-10-12 = 00:00 UTC) or an ISO 8601 date-time with a time zone (2026-10-12T09:00:00+01:00 or ...Z). |
| users | array | – | Only these user ids. |
No output schema declared.
No examples provided.
rotacloud_list_clocked_in List clocked-in users ~99
Who is clocked in right now: user, location, role, clock-in time, minutes late and break state. GET /users_clocked_in.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
rotacloud_list_day_notes List day notes ~134
List day notes (notices pinned to rota dates, e.g. events or deliveries), optionally for one location. GET /day_notes.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Last date (yyyy-mm-dd). |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| location | integer | – | Only notes for this location id. |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| start | string | – | First date (yyyy-mm-dd). |
No output schema declared.
No examples provided.
rotacloud_list_days_off List days off ~120
Employees' scheduled days off per date in a range. GET /days_off.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | Last date (yyyy-mm-dd). |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| start | string | yes | First date (yyyy-mm-dd). |
| users | array | – | Only these user ids. |
No output schema declared.
No examples provided.
rotacloud_list_holiday_allowances List holiday allowances ~113
Every employee's holiday allowance for a leave year (default and custom allowance, unit, carried over). GET /holiday_allowances/{year}.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| year | integer | yes | Leave year, e.g. 2026. |
No output schema declared.
No examples provided.
rotacloud_list_leave List leave ~237
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | Last date (yyyy-mm-dd). |
| include_deleted | boolean | – | Include deleted leave. |
| include_denied | boolean | – | Include denied leave requests. |
| include_expired | boolean | – | Include expired leave requests. |
| include_requested | boolean | – | Include pending leave requests. |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| start | string | – | First date (yyyy-mm-dd). |
| types | array | – | Only these leave type ids (see rotacloud_list_leave_types). |
| users | array | – | Only these user ids. |
| year | integer | – | Leave year instead of a date range. |
No output schema declared.
No examples provided.
rotacloud_list_leave_requests List leave requests ~109
List leave requests awaiting a decision (and past ones): user, leave type, dates, half days, the employee's message. GET /leave_requests.
| Name | Type | Req | Description |
|---|---|---|---|
| include_deleted | boolean | – | Include deleted requests. |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
rotacloud_list_leave_types List leave types ~97
List leave types (Holiday, Sickness, Unpaid, ...) with id, short name and whether employees can request them. GET /leave_types.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
rotacloud_list_locations List locations ~107
List locations (sites/branches) with address, time zone and managers. GET /locations.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Only these location ids. |
| include_deleted | boolean | – | Include deleted locations. |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
rotacloud_list_pay_periods List pay periods ~118
List pay periods overlapping a date range (id, name, start/end date, locked). GET /pay_periods.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | yes | Last date (yyyy-mm-dd). |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| start | string | yes | First date (yyyy-mm-dd). |
No output schema declared.
No examples provided.
rotacloud_list_roles List roles ~107
List job roles (positions) with colour, default break and pay rate. GET /roles.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Only these role ids. |
| include_deleted | boolean | – | Include deleted roles. |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
rotacloud_list_shifts List shifts ~345
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.
| Name | Type | Req | Description |
|---|---|---|---|
| end | – | yes | Unix timestamp (seconds), an ISO 8601 date (2026-10-12 = 00:00 UTC) or an ISO 8601 date-time with a time zone (2026-10-12T09:00:00+01:00 or ...Z). |
| include_deleted | boolean | – | Include deleted shifts. |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| locations | array | – | Only shifts at these location ids. |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| open | boolean | – | true = only open (unassigned) shifts, false = only assigned shifts. |
| published | boolean | – | true = only published shifts, false = only unpublished (draft) shifts. |
| roles | array | – | Only shifts with these role ids. |
| start | – | yes | Unix timestamp (seconds), an ISO 8601 date (2026-10-12 = 00:00 UTC) or an ISO 8601 date-time with a time zone (2026-10-12T09:00:00+01:00 or ...Z). |
| users | array | – | Only shifts of these user ids (add 0 to include open shifts). |
No output schema declared.
No examples provided.
rotacloud_list_swap_requests List shift swap requests ~99
List shift swap requests with their status, the shifts and the users involved. GET /swap_requests.
| Name | Type | Req | Description |
|---|---|---|---|
| include_deleted | boolean | – | Include deleted swap requests. |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
rotacloud_list_users List users ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | – | Only these user ids. |
| include_deleted | boolean | – | Include deleted (former) users. |
| limit | integer | – | Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left). |
| locations | array | – | Only users in these location ids. |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
No output schema declared.
No examples provided.
rotacloud_publish_shifts Publish shifts ~49
WRITE: publish shifts so the assigned employees see them (and get notified). POST /shifts_published.
| Name | Type | Req | Description |
|---|---|---|---|
| shift_ids | array | yes | Ids of the shifts to publish. |
No output schema declared.
No examples provided.
rotacloud_update_shift Update shift ~252
WRITE: change a shift's times, assignee, location, role, break, notes or published state. Only the fields you pass change. POST /shifts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | – | – | Unix timestamp (seconds), an ISO 8601 date (2026-10-12 = 00:00 UTC) or an ISO 8601 date-time with a time zone (2026-10-12T09:00:00+01:00 or ...Z). |
| location_id | integer | – | New location id. |
| minutes_break | integer | – | Unpaid break in minutes. |
| notes | string | – | Shift notes. |
| published | boolean | – | Published state. |
| role_id | integer | – | New role id. |
| shift_id | integer | yes | Shift id. |
| start_time | – | – | Unix timestamp (seconds), an ISO 8601 date (2026-10-12 = 00:00 UTC) or an ISO 8601 date-time with a time zone (2026-10-12T09:00:00+01:00 or ...Z). |
| user_id | – | – | New assignee; null makes it an open shift. |
No output schema declared.
No examples provided.
How do I install the RotaCloud MCP by usefulapi server?
RotaCloud MCP by usefulapi is a hosted endpoint at https://rotacloud.usefulapi.io/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 · rotacloud.usefulapi.io
claude mcp add --transport http io-usefulapi-rotacloud 'https://rotacloud.usefulapi.io/mcp'
What is the RotaCloud MCP by usefulapi server?
RotaCloud MCP by usefulapi is listed in the public MCP registry as io.usefulapi/rotacloud. Read RotaCloud shifts, attendance, leave, availability and payroll; create shifts and handle leave. This page covers its hosted endpoint (https://rotacloud.usefulapi.io/mcp).
Is the RotaCloud MCP by usefulapi server safe to use?
RotaCloud MCP by usefulapi scores 64 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 RotaCloud MCP by usefulapi server expose?
RotaCloud MCP by usefulapi exposes 26 tools: rotacloud_list_accounts, rotacloud_list_users, rotacloud_get_user, rotacloud_list_locations, rotacloud_list_roles, and 21 more. Their descriptions and schemas cost roughly 3,410 tokens of context every time the server is loaded.
Does the RotaCloud MCP by usefulapi server require authentication?
Yes. RotaCloud MCP by usefulapi asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the RotaCloud MCP by usefulapi server still maintained?
RotaCloud MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 16 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.