Shiftbase MCP by usefulapi
REMOTE · SHIFTBASE.USEFULAPI.IO
Read Shiftbase rosters, timesheets, absences and availability; schedule shifts and review absences.
Available components
Last scanned (42 minutes ago)
Scores higher than 47% of remote servers
Reachable. Last reached 17 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 Usability81
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3196 tokens (~145/item across 22 items; 22 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 Management23
- Stability observed for 7 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 23 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.
- 13 Oct 26 +3
- 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
- 12 Oct 26 +1
- Stability: unverified → 0.07 ▲ functional
- 10 Oct 26 60
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 17 Oct 2026 · Probed https://shiftbase.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 shiftbase.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://shiftbase.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://shiftbase.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://shiftbase.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://shiftbase.usefulapi.io/mcp |
| Authorisation server | https://shiftbase.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://shiftbase.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/shiftbase/ |
| http (plaintext) | http://shiftbase.usefulapi.io/mcp | Inconclusive | 302 | http://shiftbase.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 →
shiftbase_create_roster Schedule a shift ~245
WRITE: put one employee on the schedule for one date (a single, non-recurring shift) in a team, with a shift type, start/end time and break. The employee is notified only when notify is true. POST /rosters.
| Name | Type | Req | Description |
|---|---|---|---|
| break_minutes | integer | – | Unpaid break in minutes (default 0). |
| date | string | yes | Date of the shift (yyyy-mm-dd). |
| department_id | integer | yes | Department of the team. |
| description | string | – | Note shown on the shift. |
| end_time | string | yes | End, 24-hour hh:mm (e.g. 17:30); earlier than start = ends the next day. |
| notify | boolean | – | Notify the employee (default false). |
| paid_break_minutes | integer | – | Paid break in minutes (default 0). |
| shift_id | integer | yes | Shift type (shiftbase_list_shift_types). |
| start_time | string | yes | Start, 24-hour hh:mm (e.g. 09:00). |
| team_id | integer | yes | Team (shiftbase_list_teams). |
| user_id | integer | yes | The employee to schedule. |
No output schema declared.
No examples provided.
shiftbase_get_absence Get absence ~52
One absence by id, with the per-day hours and who reviewed it. GET /absentees/{absenteeId}.
| Name | Type | Req | Description |
|---|---|---|---|
| absence_id | integer | yes | Shiftbase absence (absentee) id. |
No output schema declared.
No examples provided.
shiftbase_get_account Get account ~39
The Shiftbase account this API key belongs to: company, country, time zone, working-day start/end, plan facts. GET /accounts.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
shiftbase_get_availability Get employee availability ~185
Employee availability (available / unavailable, all day or from a time) for a date range of at most 62 days, from Shiftbase's availability report. Needs the Basic plan and the "View reports" permission. POST /reports/availability (export json; reads only).
| Name | Type | Req | Description |
|---|---|---|---|
| department_ids | array | – | Only these departments. |
| from | string | yes | First date (yyyy-mm-dd). |
| limit | integer | – | Results per page, 1-200 (default 50). 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. |
| statuses | array | – | Only these availability types. |
| to | string | yes | Last date (yyyy-mm-dd), at most 62 days after from. |
| user_id | integer | – | Only this employee. |
No output schema declared.
No examples provided.
shiftbase_get_expected_absence_hours Get expected absence hours ~121
How many hours an absence would cost for an employee, per day and in total (from the schedule or the contract, per the absence policy), for a period of at most 366 days. Changes nothing. POST /absentees/expected.
| Name | Type | Req | Description |
|---|---|---|---|
| absence_type_id | integer | yes | Absence type id (shiftbase_list_absence_types). |
| end_date | string | yes | Last day (yyyy-mm-dd). |
| start_date | string | yes | First day (yyyy-mm-dd). |
| user_id | integer | yes | The employee. |
No output schema declared.
No examples provided.
shiftbase_get_roster Get scheduled shift ~83
One scheduled shift by its occurrence_id, with the employee, shift type, team and who created/changed it. GET /rosters/{occurrenceId}.
| Name | Type | Req | Description |
|---|---|---|---|
| occurrence_id | string | yes | The occurrence_id from shiftbase_list_rosters: "<roster id>" or, for a recurring shift, "<roster id>:<yyyy-mm-dd>". |
No output schema declared.
No examples provided.
shiftbase_get_timesheet Get timesheet ~46
One timesheet by id, with its clocked breaks. GET /timesheets/{timesheetId}.
| Name | Type | Req | Description |
|---|---|---|---|
| timesheet_id | integer | yes | Shiftbase timesheet id. |
No output schema declared.
No examples provided.
shiftbase_get_user Get employee ~55
One employee by user id or email address, with teams and departments. GET /users/{identifier}.
| Name | Type | Req | Description |
|---|---|---|---|
| string | – | Or the employee's email address. | |
| user_id | integer | – | Shiftbase user id. |
No output schema declared.
No examples provided.
shiftbase_list_absence_types List absence types ~111
List absence types (e.g. Holiday, Sick, Unpaid leave): name, unit (hours or days), whether it costs leave hours, colour. Their ids are the absence_type_id for absences. GET /absentee_options.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-200 (default 50). 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.
shiftbase_list_absences List absences ~262
List absences (leave, sick leave, other time off) overlapping a date range of at most 366 days: employee, absence type, start/end date, hours or days, status Approved/Declined/Pending and who reviewed it. Needs the Basic plan. GET /absentees.
| Name | Type | Req | Description |
|---|---|---|---|
| absence_type_ids | array | – | Only these absence types (ids from shiftbase_list_absence_types). |
| include | string | – | Add related data: the per-day breakdown, the employee or the absence type. |
| limit | integer | – | Results per page, 1-200 (default 50). The reply's total and next_offset show what is left. |
| max_date | string | yes | Last date (yyyy-mm-dd), at most 366 days after min_date. |
| min_date | string | yes | First date (yyyy-mm-dd). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| only_open_ended | boolean | – | Only open-ended absences (no end date yet, e.g. long-term sick leave). |
| status | string | – | Only absences with this status (Pending = requests waiting for review). |
| user_id | integer | – | Only this employee. |
No output schema declared.
No examples provided.
shiftbase_list_clocked_in List clocked-in employees ~93
Who is clocked in right now: employee, since when, their scheduled shift, team, department and location. GET /timesheets/clock.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-200 (default 50). 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.
shiftbase_list_departments List departments ~91
List departments (sites/branches that own teams, shifts and schedules) with address and timesheet/clocking settings. GET /departments.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-200 (default 50). 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.
shiftbase_list_locations List locations ~74
List active locations (addresses that group departments). GET /locations.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results per page, 1-200 (default 50). 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.
shiftbase_list_open_shifts List open shifts ~169
List open (unassigned) shifts that employees can pick up, for a date range of at most 62 days (default: today). Needs the Basic plan or higher. GET /open_shifts.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | integer | – | Only open shifts in this department. |
| limit | integer | – | Results per page, 1-200 (default 50). The reply's total and next_offset show what is left. |
| max_date | string | – | Last date (yyyy-mm-dd). |
| min_date | string | – | First date (yyyy-mm-dd). Give both dates or neither (= today). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| user_id | integer | – | Only open shifts this employee can take. |
No output schema declared.
No examples provided.
shiftbase_list_rosters List scheduled shifts ~196
List the schedule (rosters = shifts assigned to employees) for a date range of at most 62 days: date, start/end time, break, employee, team, shift type, department, published state, hours and cost. Each item's occurrence_id identifies it for shiftbase_get_roster and shiftbase_update_roster. GET /rosters.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | integer | – | Only shifts in this department. |
| limit | integer | – | Results per page, 1-200 (default 50). The reply's total and next_offset show what is left. |
| max_date | string | yes | Last date (yyyy-mm-dd), at most 62 days after min_date. |
| min_date | string | yes | First date (yyyy-mm-dd). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| user_id | integer | – | Only shifts of this employee. |
No output schema declared.
No examples provided.
shiftbase_list_shift_types List shift types ~135
List shift types (the templates a scheduled shift uses: name, short name, default start/end time and break), optionally for one department. Their ids are the shift_id for shiftbase_create_roster. GET /shifts.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | integer | – | Only shift types of this department. |
| include_deleted | boolean | – | Also include deleted shift types. |
| limit | integer | – | Results per page, 1-200 (default 50). 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.
shiftbase_list_teams List teams ~96
List teams (the rows of the schedule within a department), optionally for one department. GET /teams.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | integer | – | Only teams of this department. |
| limit | integer | – | Results per page, 1-200 (default 50). 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.
shiftbase_list_timesheets List timesheets ~178
List timesheets (worked hours: clock in/out, breaks, total, status Approved/Declined/Pending, wage and surcharges) for a date range of at most 62 days. GET /timesheets.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | integer | – | Only this department. |
| limit | integer | – | Results per page, 1-200 (default 50). The reply's total and next_offset show what is left. |
| max_date | string | yes | Last date (yyyy-mm-dd), at most 62 days after min_date. |
| min_date | string | yes | First date (yyyy-mm-dd). |
| offset | integer | – | Index of the first result; pass the previous reply's next_offset. |
| status | string | – | Only timesheets with this status. |
| user_id | integer | – | Only this employee. |
No output schema declared.
No examples provided.
shiftbase_list_users List employees ~164
List employees (users) with their teams and departments, contact details, employee number, start/end dates and plus-min hours balance. Use it to map user ids in schedules, timesheets and absences to names. Identity, bank and birth data are never returned. GET /users.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | true = only active employees, false = only inactive. Default: both. |
| department_id | integer | – | Only employees of this department. |
| include_hidden | boolean | – | Also include hidden users. |
| limit | integer | – | Results per page, 1-200 (default 50). 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.
shiftbase_request_absence Request an absence ~202
WRITE: add an absence (leave/time-off request) for an employee. By default it is a Pending request for a manager to review; status Approved books it directly (needs the approve-absence permission). The hours per day come from Shiftbase's own expected-hours calculation (the same as shiftbase_get_expected_absence_hours). Needs the Basic plan. POST /absentees.
| Name | Type | Req | Description |
|---|---|---|---|
| absence_type_id | integer | yes | Absence type id (shiftbase_list_absence_types). |
| end_date | string | yes | Last day (yyyy-mm-dd), at most 366 days after start_date. |
| note | string | – | Note from the requester. |
| notify_employee | boolean | – | Notify the employee (default false). |
| start_date | string | yes | First day (yyyy-mm-dd). |
| status | string | – | Pending (default) = a request to review; Approved = book it directly. |
| user_id | integer | yes | The employee. |
No output schema declared.
No examples provided.
shiftbase_review_absence Approve or decline an absence ~104
WRITE: approve or decline an absence request. Reads the absence first and sends it back unchanged except for the status (needs the approve-absence permission). PUT /absentees/{absenteeId}.
| Name | Type | Req | Description |
|---|---|---|---|
| absence_id | integer | yes | Absence (absentee) id, e.g. from shiftbase_list_absences with status Pending. |
| decision | string | yes | Approved or Declined. |
| notify_employee | boolean | – | Notify the employee (default false). |
No output schema declared.
No examples provided.
shiftbase_update_roster Change a scheduled shift ~290
WRITE: change a scheduled shift: move it to another date, time, employee, team or shift type, or change its break or note. Reads the shift first and sends it back with your changes. For a recurring shift, scope says what changes: "occurrence" (this date only), "sequence" (this date and all later ones) or "original" (the whole series; also the right scope for a non-recurring shift). PUT /rosters/{occurrenceId}/{scope}.
| Name | Type | Req | Description |
|---|---|---|---|
| break_minutes | integer | – | New unpaid break in minutes. |
| date | string | – | New date (yyyy-mm-dd). |
| department_id | integer | – | New department (when moving to a team of another department). |
| description | string | – | New note. |
| end_time | string | – | New end, hh:mm. |
| notify | boolean | – | Notify the employee (default false). |
| occurrence_id | string | yes | occurrence_id from shiftbase_list_rosters. |
| paid_break_minutes | integer | – | New paid break in minutes. |
| scope | string | yes | "original" for a non-recurring shift; see the description for recurring ones. |
| shift_id | integer | – | New shift type. |
| start_time | string | – | New start, hh:mm. |
| team_id | integer | – | New team. |
| user_id | integer | – | New employee. |
No output schema declared.
No examples provided.
How do I install the Shiftbase MCP by usefulapi server?
Shiftbase MCP by usefulapi is a hosted endpoint at https://shiftbase.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 · shiftbase.usefulapi.io
claude mcp add --transport http io-usefulapi-shiftbase 'https://shiftbase.usefulapi.io/mcp'
What is the Shiftbase MCP by usefulapi server?
Shiftbase MCP by usefulapi is listed in the public MCP registry as io.usefulapi/shiftbase. Read Shiftbase rosters, timesheets, absences and availability; schedule shifts and review absences. This page covers its hosted endpoint (https://shiftbase.usefulapi.io/mcp).
Is the Shiftbase MCP by usefulapi server safe to use?
Shiftbase MCP by usefulapi scores 65 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 Shiftbase MCP by usefulapi server expose?
Shiftbase MCP by usefulapi exposes 22 tools: shiftbase_get_account, shiftbase_list_users, shiftbase_get_user, shiftbase_list_departments, shiftbase_list_teams, and 17 more. Their descriptions and schemas cost roughly 2,991 tokens of context every time the server is loaded.
Does the Shiftbase MCP by usefulapi server require authentication?
Yes. Shiftbase 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 Shiftbase MCP by usefulapi server still maintained?
Shiftbase MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.