MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

io.usefulapi/rotacloud

Read RotaCloud shifts, attendance, leave, availability and payroll; create shifts and handle leave. — the publisher's description

4 of 5 record checks metRead-only · tools listed 2026-10-23Topic: productivity-and-docs · AI-classifiedPricing: freemium · AI-classifiedversion 1.7.4JavaScriptstreamable HTTP26 tools

Summary

io.usefulapi/rotacloud is a remote MCP server listed in the official MCP registry at version 1.7.4. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 26 tools, 0 resources and 1 prompt.

Record checks

4 of 5 record checks met · 4 do not apply

met: Registry entry is active and says how to run it
met: Source repository link opens
met: Repository is not archived
met: Code pushed to the repository in the 90 days before our check
not met: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Repository: public
Tools: 26
Described as changing data: 6 of 26 toolsAI-classified
Mainly works on: accounts and data in outside web servicesAI-classified
Topic: productivity-and-docsAI-classified
Pricing: freemiumAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 6 tools whose name or declaration suggests they change data (rotacloud_create_shift, rotacloud_update_shift, rotacloud_publish_shifts, rotacloud_create_leave_request, rotacloud_approve_leave_request and 1 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

6 tools are described as changing something (rotacloud_create_shift, rotacloud_update_shift, rotacloud_publish_shifts, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested

yes, a real session (not a text-only review)

Last tested

2026-10-23

Mode

read-only (no tool calls)

Latest version

1.7.4, published 2026-10-22 (registry, as of the 2026-10-23 snapshot)

First listed version

2026-10-08 (earliest version still in the registry; older removed versions would be earlier)

Version history

5 versions listed, 2026-10-08 to 2026-10-22; 5 in the 90 days before the 2026-10-23 snapshot.

Most recent 5 versions

1.7.4 · 2026-10-22
1.7.3 · 2026-10-21
1.2.1 · 2026-10-09
1.1.0 · 2026-10-08
1.0.0 · 2026-10-08

(versions still listed in the registry only)

Registry data

snapshot 2026-10-23

Package and repository

checked 2026-10-23

Engine

mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.7.4 (published 2026-10-22).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

26tools

0resources

1prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

6 of 26 tools are described as changing something (creating, editing, deleting, sending or running).

rotacloud_list_accountsreads or searches
“The RotaCloud account(s) this API key belongs to: name, plan, time zone, employee count.”
Publisher declares: read-only yes
2 inputs
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_usersreads or searches
“List employees (users) with their level, roles, locations, contact details and pay settings.”
Publisher declares: read-only yes
5 inputs
- idsarray“Only these user ids.”
- locationsarray“Only users in these location ids.”
- include_deletedboolean“Include deleted (former) users.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_get_userreads or searches
“One employee by id.”
Publisher declares: read-only yes
1 input, 1 required
- user_idintegerrequired“RotaCloud user id.”
rotacloud_list_locationsreads or searches
“List locations (sites/branches) with address, time zone and managers.”
Publisher declares: read-only yes
4 inputs
- idsarray“Only these location ids.”
- include_deletedboolean“Include deleted locations.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_rolesreads or searches
“List job roles (positions) with colour, default break and pay rate.”
Publisher declares: read-only yes
4 inputs
- idsarray“Only these role ids.”
- include_deletedboolean“Include deleted roles.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_shiftsreads or searches
“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.”
Publisher declares: read-only yes
10 inputs, 2 required
- startinteger or stringrequired“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).”
- endinteger or stringrequired“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).”
- usersarray“Only shifts of these user ids (add 0 to include open shifts).”
- locationsarray“Only shifts at these location ids.”
- rolesarray“Only shifts with these role ids.”
- openboolean“true = only open (unassigned) shifts, false = only assigned shifts.”
- publishedboolean“true = only published shifts, false = only unpublished (draft) shifts.”
- include_deletedboolean“Include deleted shifts.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_get_shiftreads or searches
“One shift by id.”
Publisher declares: read-only yes
1 input, 1 required
- shift_idintegerrequired“RotaCloud shift id.”
rotacloud_list_swap_requestsreads or searches
“List shift swap requests with their status, the shifts and the users involved.”
Publisher declares: read-only yes
3 inputs
- include_deletedboolean“Include deleted swap requests.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_day_notesreads or searches
“List day notes (notices pinned to rota dates, e.g.”
Publisher declares: read-only yes
5 inputs
- startstring“First date (yyyy-mm-dd).”
- endstring“Last date (yyyy-mm-dd).”
- locationinteger“Only notes for this location id.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_attendancereads or searches
“List time & attendance records (clock-in/out times, breaks, minutes late, hours, approval state) in a time range.”
Publisher declares: read-only yes
9 inputs, 2 required
- startinteger or stringrequired“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).”
- endinteger or stringrequired“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).”
- usersarray“Only these user ids.”
- locationsarray“Only these location ids.”
- rolesarray“Only these role ids.”
- approvedboolean“true = only approved records, false = only unapproved.”
- include_deletedboolean“Include deleted records.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_clocked_inreads or searches
“Who is clocked in right now: user, location, role, clock-in time, minutes late and break state.”
Publisher declares: read-only yes
2 inputs
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_leavereads or searches
“List booked leave (holiday, sickness, etc.) with type, user, dates, hours and status.”
Publisher declares: read-only yes
11 inputs
- startstring“First date (yyyy-mm-dd).”
- endstring“Last date (yyyy-mm-dd).”
- yearinteger“Leave year instead of a date range.”
- usersarray“Only these user ids.”
- typesarray“Only these leave type ids (see rotacloud_list_leave_types).”
- include_requestedboolean“Include pending leave requests.”
- include_deniedboolean“Include denied leave requests.”
- include_expiredboolean“Include expired leave requests.”
- include_deletedboolean“Include deleted leave.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”

Show 14 more tools

rotacloud_list_leave_requestsreads or searches
“List leave requests awaiting a decision (and past ones): user, leave type, dates, half days, the employee's message.”
Publisher declares: read-only yes
3 inputs
- include_deletedboolean“Include deleted requests.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_get_leave_requestreads or searches
“One leave request by id, with the per-day breakdown.”
Publisher declares: read-only yes
1 input, 1 required
- request_idintegerrequired“Leave request id.”
rotacloud_list_leave_typesreads or searches
“List leave types (Holiday, Sickness, Unpaid, ...) with id, short name and whether employees can request them.”
Publisher declares: read-only yes
2 inputs
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_holiday_allowancesreads or searches
“Every employee's holiday allowance for a leave year (default and custom allowance, unit, carried over).”
Publisher declares: read-only yes
3 inputs, 1 required
- yearintegerrequired“Leave year, e.g.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_get_availabilityreads or searches
“Employees' availability per date in a range (available / unavailable times).”
Publisher declares: read-only yes
5 inputs, 2 required
- startstringrequired“First date (yyyy-mm-dd).”
- endstringrequired“Last date (yyyy-mm-dd).”
- usersarray“Only these user ids.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_days_offreads or searches
“Employees' scheduled days off per date in a range.”
Publisher declares: read-only yes
5 inputs, 2 required
- startstringrequired“First date (yyyy-mm-dd).”
- endstringrequired“Last date (yyyy-mm-dd).”
- usersarray“Only these user ids.”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_list_pay_periodsreads or searches
“List pay periods overlapping a date range (id, name, start/end date, locked).”
Publisher declares: read-only yes
4 inputs, 2 required
- startstringrequired“First date (yyyy-mm-dd).”
- endstringrequired“Last date (yyyy-mm-dd).”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_get_payrollreads or searches
“Payroll for one pay period, per employee: pay settings, attendance worked, paid/unpaid leave, overtime and pay totals.”
Publisher declares: read-only yes
3 inputs, 1 required
- pay_period_idintegerrequired“Pay period id (from rotacloud_list_pay_periods).”
- limitinteger“Results per page, 1-500 (RotaCloud may cap it lower; the reply's total and next_offset show what is left).”
- offsetinteger“Index of the first result; pass the previous reply's next_offset.”
rotacloud_create_shiftcreates or changes datadescribed as changing data
“WRITE: create a shift on the rota.”
Publisher declares: destructive yes
8 inputs, 3 required
- start_timeinteger or stringrequired“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).”
- end_timeinteger or stringrequired“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_idintegerrequired“Location id.”
- user_idinteger“Assigned user id; omit for an open shift.”
- role_idinteger“Role id.”
- minutes_breakinteger“Unpaid break in minutes.”
- notesstring“Shift notes shown to the employee.”
- publishedboolean“Publish immediately (default false).”
rotacloud_update_shiftcreates or changes datadescribed as changing data
“WRITE: change a shift's times, assignee, location, role, break, notes or published state.”
Publisher declares: destructive yes · idempotent yes
9 inputs, 1 required
- shift_idintegerrequired“Shift id.”
- start_timeinteger or string“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).”
- end_timeinteger or string“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_idinteger or null“New assignee; null makes it an open shift.”
- location_idinteger“New location id.”
- role_idinteger“New role id.”
- minutes_breakinteger“Unpaid break in minutes.”
- notesstring“Shift notes.”
- publishedboolean“Published state.”
rotacloud_publish_shiftscreates or changes datadescribed as changing data
“WRITE: publish shifts so the assigned employees see them (and get notified).”
Publisher declares: destructive yes · idempotent yes
1 input, 1 required
- shift_idsarrayrequired“Ids of the shifts to publish.”
rotacloud_create_leave_requestcreates or changes datadescribed as changing data
“WRITE: submit a leave request on behalf of an employee (sent as that user, for a manager to approve).”
Publisher declares: destructive yes
7 inputs, 4 required
- user_idintegerrequired“The employee requesting leave (the request is made as this user).”
- leave_type_idintegerrequired“Leave type id (see rotacloud_list_leave_types; must be requestable).”
- start_datestringrequired“First day (yyyy-mm-dd).”
- end_datestringrequired“Last day (yyyy-mm-dd).”
- start_am_pmstring“'pm' starts at midday (half day); default 'am'.”
- end_am_pmstring“'am' ends at midday (half day); default 'pm'.”
- messagestring“Message from the employee to the manager.”
rotacloud_approve_leave_requestcreates or changes datadescribed as changing data
“WRITE: approve a pending leave request (it becomes booked leave and the employee is notified).”
Publisher declares: destructive yes · idempotent yes
2 inputs, 1 required
- request_idintegerrequired“Leave request id.”
- admin_messagestring“Message to the employee.”
rotacloud_deny_leave_requestcreates or changes datadescribed as changing data
“WRITE: deny a pending leave request (the employee is notified).”
Publisher declares: destructive yes · idempotent yes
2 inputs, 1 required
- request_idintegerrequired“Leave request id.”
- admin_messagestring“Reason shown to the employee.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 26 tools
Says what it returns: 80% of 25 tools
States limits, defaults or errors: 65% of 26 tools
Says when to use it: 4% of 26 tools
Items covered per tool: 2.5 of 4 on average

Counted from the listing

Parameters with a description: 100% of 112
Tools with a description: 100% of 26
Typical description length: 118 characters

The tool set

Counted from the listing

Tools: 26
Size of the list: about 6,431 tokens for an agent to load (characters ÷ 4)
Naming: 26 of 26 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 26 of 26 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://rotacloud.usefulapi.io/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "rotacloud": {
      "url": "https://rotacloud.usefulapi.io/mcp"
    }
  }
}

VS Code · .vscode/mcp.json

{
  "servers": {
    "rotacloud": {
      "type": "http",
      "url": "https://rotacloud.usefulapi.io/mcp"
    }
  }
}

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"rotacloud","type":"http","url":"https://rotacloud.usefulapi.io/mcp"}'

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://rotacloud.usefulapi.io/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint rotacloud.usefulapi.io/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23
Repository github.com/m190/usefulapi-mcp	Opens publicly	matches	api.github.com · 2026-10-23

Who made it?

Feature #7 · lineage

Facts about the publisher. We do not turn them into a trust score.

Namespace: io.usefulapi · 341 servers
GitHub owner: a personal account (m190)

Repository: github.com/m190/usefulapi-mcp
Stars: 0
Repository age: 91–180 days
Last push: 0–30 days ago
Archived: no
Security policy: none found (we looked for SECURITY.md in the repository and in its owner’s .github repository)

Source: the registry entry and api.github.com · 2026-10-23; security policy read from GitHub · 2026-10-23.

Publish this server? Run these checks against it yourself before release, from your own machine: a server the command starts, or your own server at its URL after a one-time proof that you control it: npx protocolprobe-selftest.

Choosing

Record checks

Public records · not a safety rating

4 of 5 record checks met · 4 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: 0 stars (ranked from 10)

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
MetSource repository link opensThe linked GitHub repository is public.
MetRepository is not archivedNot archived.
MetCode pushed to the repository in the 90 days before our checkLast push 0-30 days before our check.
Not metRepository publishes a security policy (SECURITY.md)No SECURITY.md in the places GitHub reads it from.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about io.usefulapi/rotacloud

Answered from the data above

Is io.usefulapi/rotacloud safe to install?

We do not rate servers as safe or unsafe. 4 of its 5 applicable record checks are met (facts from public records, each listed on this page). What the records show: Its source repository opens publicly. Its repository had a push in the last 90 days. 6 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Is io.usefulapi/rotacloud free to use?

Its website (usefulapi.io/rotacloud/) describes a freemium pricing model. This is an AI-classified reading of the page on 2026-10-23, so check the page itself before relying on it.

Does io.usefulapi/rotacloud need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has io.usefulapi/rotacloud been security tested?

Partly. 3 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can io.usefulapi/rotacloud do?

It lists 26 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search and create or change data. We did not call any tool, so this describes the text, not the behaviour.

Can io.usefulapi/rotacloud change or delete data?

6 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Does io.usefulapi/rotacloud publish a security policy?

We found no SECURITY.md in its repository (root, .github/ or docs/) or in its owner's .github repository.

Where is the source code of io.usefulapi/rotacloud?

In github.com/m190/usefulapi-mcp, which opens publicly.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.usekaneo/kaneoalso has tools that creates or changes data, reads or searchescompare with this one
io.github.54yyyu/zotero-mcpZotero MCPalso has tools that creates or changes data, reads or searchescompare with this one
io.github.haris-musa/excel-mcp-serverExcel MCP Serveralso has tools that creates or changes data, reads or searchescompare with this one
io.github.iwe-org/iweIWEalso has tools that creates or changes data, reads or searchescompare with this one
io.github.silverstein/minutesalso has tools that creates or changes data, reads or searchescompare with this one
io.github.Softeria/ms-365-mcp-serverMicrosoft 365 MCP Serveralso has tools that creates or changes data, reads or searchescompare with this one

Active servers whose topic is also “productivity-and-docs” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: not run · nothing to check it against
Fake assistant turns: not run · an error was returned
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

3 exercised13 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 3 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 3

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 13

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
12Hidden content
audience-hidingChecks resources that hide content from the user.This check needs content the server returns, and nothing was read or called.not run · nothing to check it against
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.The server returned an error when its prompts were read.not run · an error was returned
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
325 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 26 tools, 0 resources, 1 prompt.
1,526 msFinished: 3 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

productivity-and-docs

AI-classified · 2026-10-23

Pricing modelAI-classified

freemium

read from usefulapi.io/rotacloud/ · 2026-10-23

“Free $0 50 tool calls / month”

Programming language

JavaScript

api.github.com · 2026-10-23

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

prompts, tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

owner: a personal account · repository age: 91–180 days · stars: 0–9

api.github.com · 2026-10-23

Maintenance

active

api.github.com · 2026-10-23

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “io.usefulapi/rotacloud: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/io.usefulapi/rotacloud

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/io.usefulapi/rotacloud)](https://protocolprobe.com/mcp/servers/io.usefulapi/rotacloud)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology