Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Shiftbase MCP by usefulapi

REMOTE · SHIFTBASE.USEFULAPI.IO

Read Shiftbase rosters, timesheets, absences and availability; schedule shifts and review absences.

+5 this week 65 Trust /100

Last scanned (42 minutes ago)

Scores higher than 47% of remote servers

Reachable. Last reached 17 Oct 2026.

Category Project Management

Trust breakdown (7 categories)

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
Transport & Reachability0
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
Changelog

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.

Diagnostics

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
MCP tools · 22 exposed · ~2,991 tokens

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 →

Tool Tokens
shiftbase_create_roster ~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.

NameTypeReqDescription
break_minutesinteger–Unpaid break in minutes (default 0).
datestringyesDate of the shift (yyyy-mm-dd).
department_idintegeryesDepartment of the team.
descriptionstring–Note shown on the shift.
end_timestringyesEnd, 24-hour hh:mm (e.g. 17:30); earlier than start = ends the next day.
notifyboolean–Notify the employee (default false).
paid_break_minutesinteger–Paid break in minutes (default 0).
shift_idintegeryesShift type (shiftbase_list_shift_types).
start_timestringyesStart, 24-hour hh:mm (e.g. 09:00).
team_idintegeryesTeam (shiftbase_list_teams).
user_idintegeryesThe employee to schedule.

No output schema declared.

No examples provided.

shiftbase_get_absence ~52

One absence by id, with the per-day hours and who reviewed it. GET /absentees/{absenteeId}.

NameTypeReqDescription
absence_idintegeryesShiftbase absence (absentee) id.

No output schema declared.

No examples provided.

shiftbase_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 ~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).

NameTypeReqDescription
department_idsarray–Only these departments.
fromstringyesFirst date (yyyy-mm-dd).
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
offsetinteger–Index of the first result; pass the previous reply's next_offset.
statusesarray–Only these availability types.
tostringyesLast date (yyyy-mm-dd), at most 62 days after from.
user_idinteger–Only this employee.

No output schema declared.

No examples provided.

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

NameTypeReqDescription
absence_type_idintegeryesAbsence type id (shiftbase_list_absence_types).
end_datestringyesLast day (yyyy-mm-dd).
start_datestringyesFirst day (yyyy-mm-dd).
user_idintegeryesThe employee.

No output schema declared.

No examples provided.

shiftbase_get_roster ~83

One scheduled shift by its occurrence_id, with the employee, shift type, team and who created/changed it. GET /rosters/{occurrenceId}.

NameTypeReqDescription
occurrence_idstringyesThe 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 ~46

One timesheet by id, with its clocked breaks. GET /timesheets/{timesheetId}.

NameTypeReqDescription
timesheet_idintegeryesShiftbase timesheet id.

No output schema declared.

No examples provided.

shiftbase_get_user ~55

One employee by user id or email address, with teams and departments. GET /users/{identifier}.

NameTypeReqDescription
emailstring–Or the employee's email address.
user_idinteger–Shiftbase user id.

No output schema declared.

No examples provided.

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

NameTypeReqDescription
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
offsetinteger–Index of the first result; pass the previous reply's next_offset.

No output schema declared.

No examples provided.

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

NameTypeReqDescription
absence_type_idsarray–Only these absence types (ids from shiftbase_list_absence_types).
includestring–Add related data: the per-day breakdown, the employee or the absence type.
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
max_datestringyesLast date (yyyy-mm-dd), at most 366 days after min_date.
min_datestringyesFirst date (yyyy-mm-dd).
offsetinteger–Index of the first result; pass the previous reply's next_offset.
only_open_endedboolean–Only open-ended absences (no end date yet, e.g. long-term sick leave).
statusstring–Only absences with this status (Pending = requests waiting for review).
user_idinteger–Only this employee.

No output schema declared.

No examples provided.

shiftbase_list_clocked_in ~93

Who is clocked in right now: employee, since when, their scheduled shift, team, department and location. GET /timesheets/clock.

NameTypeReqDescription
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
offsetinteger–Index of the first result; pass the previous reply's next_offset.

No output schema declared.

No examples provided.

shiftbase_list_departments ~91

List departments (sites/branches that own teams, shifts and schedules) with address and timesheet/clocking settings. GET /departments.

NameTypeReqDescription
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
offsetinteger–Index of the first result; pass the previous reply's next_offset.

No output schema declared.

No examples provided.

shiftbase_list_locations ~74

List active locations (addresses that group departments). GET /locations.

NameTypeReqDescription
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
offsetinteger–Index of the first result; pass the previous reply's next_offset.

No output schema declared.

No examples provided.

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

NameTypeReqDescription
department_idinteger–Only open shifts in this department.
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
max_datestring–Last date (yyyy-mm-dd).
min_datestring–First date (yyyy-mm-dd). Give both dates or neither (= today).
offsetinteger–Index of the first result; pass the previous reply's next_offset.
user_idinteger–Only open shifts this employee can take.

No output schema declared.

No examples provided.

shiftbase_list_rosters ~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.

NameTypeReqDescription
department_idinteger–Only shifts in this department.
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
max_datestringyesLast date (yyyy-mm-dd), at most 62 days after min_date.
min_datestringyesFirst date (yyyy-mm-dd).
offsetinteger–Index of the first result; pass the previous reply's next_offset.
user_idinteger–Only shifts of this employee.

No output schema declared.

No examples provided.

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

NameTypeReqDescription
department_idinteger–Only shift types of this department.
include_deletedboolean–Also include deleted shift types.
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
offsetinteger–Index of the first result; pass the previous reply's next_offset.

No output schema declared.

No examples provided.

shiftbase_list_teams ~96

List teams (the rows of the schedule within a department), optionally for one department. GET /teams.

NameTypeReqDescription
department_idinteger–Only teams of this department.
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
offsetinteger–Index of the first result; pass the previous reply's next_offset.

No output schema declared.

No examples provided.

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

NameTypeReqDescription
department_idinteger–Only this department.
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
max_datestringyesLast date (yyyy-mm-dd), at most 62 days after min_date.
min_datestringyesFirst date (yyyy-mm-dd).
offsetinteger–Index of the first result; pass the previous reply's next_offset.
statusstring–Only timesheets with this status.
user_idinteger–Only this employee.

No output schema declared.

No examples provided.

shiftbase_list_users ~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.

NameTypeReqDescription
activeboolean–true = only active employees, false = only inactive. Default: both.
department_idinteger–Only employees of this department.
include_hiddenboolean–Also include hidden users.
limitinteger–Results per page, 1-200 (default 50). The reply's total and next_offset show what is left.
offsetinteger–Index of the first result; pass the previous reply's next_offset.

No output schema declared.

No examples provided.

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

NameTypeReqDescription
absence_type_idintegeryesAbsence type id (shiftbase_list_absence_types).
end_datestringyesLast day (yyyy-mm-dd), at most 366 days after start_date.
notestring–Note from the requester.
notify_employeeboolean–Notify the employee (default false).
start_datestringyesFirst day (yyyy-mm-dd).
statusstring–Pending (default) = a request to review; Approved = book it directly.
user_idintegeryesThe employee.

No output schema declared.

No examples provided.

shiftbase_review_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}.

NameTypeReqDescription
absence_idintegeryesAbsence (absentee) id, e.g. from shiftbase_list_absences with status Pending.
decisionstringyesApproved or Declined.
notify_employeeboolean–Notify the employee (default false).

No output schema declared.

No examples provided.

shiftbase_update_roster ~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}.

NameTypeReqDescription
break_minutesinteger–New unpaid break in minutes.
datestring–New date (yyyy-mm-dd).
department_idinteger–New department (when moving to a team of another department).
descriptionstring–New note.
end_timestring–New end, hh:mm.
notifyboolean–Notify the employee (default false).
occurrence_idstringyesoccurrence_id from shiftbase_list_rosters.
paid_break_minutesinteger–New paid break in minutes.
scopestringyes"original" for a non-recurring shift; see the description for recurring ones.
shift_idinteger–New shift type.
start_timestring–New start, hh:mm.
team_idinteger–New team.
user_idinteger–New employee.

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add --transport http io-usefulapi-shiftbase 'https://shiftbase.usefulapi.io/mcp'
Common questions

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.