# Shiftbase MCP by usefulapi (remote · shiftbase.usefulapi.io)

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

- Trust score: 65/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `shiftbase.usefulapi.io`: 65/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-shiftbase/shiftbase.md), [page](https://verifymcp.io/servers/io-usefulapi-shiftbase/shiftbase)

## Channel facts

- Endpoint: `https://shiftbase.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.2.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-17.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 81/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 23 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http io-usefulapi-shiftbase 'https://shiftbase.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-shiftbase": {
      "url": "https://shiftbase.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-shiftbase": {
      "type": "http",
      "url": "https://shiftbase.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-shiftbase]
url = "https://shiftbase.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-shiftbase": {
      "type": "remote",
      "url": "https://shiftbase.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-shiftbase --url 'https://shiftbase.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-shiftbase:
    url: "https://shiftbase.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-shiftbase": {
      "Transport": "http",
      "Url": "https://shiftbase.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-shiftbase -t streamable-http -u 'https://shiftbase.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-shiftbase": {
      "type": "http",
      "url": "https://shiftbase.usefulapi.io/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-15 (score 65, +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.

### 2026-10-13 (score 64, +3)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] 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

### 2026-10-12 (score 61, +1)

- [functional improvement] Stability: unverified → 0.07

### 2026-10-10 (score 60)

First indexed and scored.

## MCP tools (22)

### `shiftbase_get_account` (~39 tokens)

Get account

The Shiftbase account this API key belongs to: company, country, time zone, working-day start/end, plan facts. GET /accounts.

### `shiftbase_list_users` (~164 tokens)

List employees

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.

Input parameters:

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

### `shiftbase_get_user` (~55 tokens)

Get employee

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

Input parameters:

- `email` (string): Or the employee's email address.
- `user_id` (integer): Shiftbase user id.

### `shiftbase_list_departments` (~91 tokens)

List departments

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

Input parameters:

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

### `shiftbase_list_teams` (~96 tokens)

List teams

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

Input parameters:

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

### `shiftbase_list_locations` (~74 tokens)

List locations

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

Input parameters:

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

### `shiftbase_list_shift_types` (~135 tokens)

List shift types

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.

Input parameters:

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

### `shiftbase_list_rosters` (~196 tokens)

List scheduled shifts

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.

Input parameters:

- `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, required): Last date (yyyy-mm-dd), at most 62 days after min_date.
- `min_date` (string, required): 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.

### `shiftbase_get_roster` (~83 tokens)

Get scheduled shift

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

Input parameters:

- `occurrence_id` (string, required): The occurrence_id from shiftbase_list_rosters: "<roster id>" or, for a recurring shift, "<roster id>:<yyyy-mm-dd>".

### `shiftbase_list_open_shifts` (~169 tokens)

List open shifts

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.

Input parameters:

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

### `shiftbase_get_availability` (~185 tokens)

Get employee availability

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

Input parameters:

- `department_ids` (array): Only these departments.
- `from` (string, required): 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, required): Last date (yyyy-mm-dd), at most 62 days after from.
- `user_id` (integer): Only this employee.

### `shiftbase_list_timesheets` (~178 tokens)

List timesheets

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.

Input parameters:

- `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, required): Last date (yyyy-mm-dd), at most 62 days after min_date.
- `min_date` (string, required): 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.

### `shiftbase_get_timesheet` (~46 tokens)

Get timesheet

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

Input parameters:

- `timesheet_id` (integer, required): Shiftbase timesheet id.

### `shiftbase_list_clocked_in` (~93 tokens)

List clocked-in employees

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

Input parameters:

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

### `shiftbase_list_absences` (~262 tokens)

List absences

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.

Input parameters:

- `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, required): Last date (yyyy-mm-dd), at most 366 days after min_date.
- `min_date` (string, required): 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.

### `shiftbase_get_absence` (~52 tokens)

Get absence

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

Input parameters:

- `absence_id` (integer, required): Shiftbase absence (absentee) id.

### `shiftbase_list_absence_types` (~111 tokens)

List absence types

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.

Input parameters:

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

### `shiftbase_get_expected_absence_hours` (~121 tokens)

Get expected absence hours

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.

Input parameters:

- `absence_type_id` (integer, required): Absence type id (shiftbase_list_absence_types).
- `end_date` (string, required): Last day (yyyy-mm-dd).
- `start_date` (string, required): First day (yyyy-mm-dd).
- `user_id` (integer, required): The employee.

### `shiftbase_create_roster` (~245 tokens)

Schedule a shift

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.

Input parameters:

- `break_minutes` (integer): Unpaid break in minutes (default 0).
- `date` (string, required): Date of the shift (yyyy-mm-dd).
- `department_id` (integer, required): Department of the team.
- `description` (string): Note shown on the shift.
- `end_time` (string, required): 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, required): Shift type (shiftbase_list_shift_types).
- `start_time` (string, required): Start, 24-hour hh:mm (e.g. 09:00).
- `team_id` (integer, required): Team (shiftbase_list_teams).
- `user_id` (integer, required): The employee to schedule.

### `shiftbase_update_roster` (~290 tokens)

Change a scheduled shift

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

Input parameters:

- `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, required): occurrence_id from shiftbase_list_rosters.
- `paid_break_minutes` (integer): New paid break in minutes.
- `scope` (string, required): "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.

### `shiftbase_request_absence` (~202 tokens)

Request an absence

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.

Input parameters:

- `absence_type_id` (integer, required): Absence type id (shiftbase_list_absence_types).
- `end_date` (string, required): 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, required): First day (yyyy-mm-dd).
- `status` (string): Pending (default) = a request to review; Approved = book it directly.
- `user_id` (integer, required): The employee.

### `shiftbase_review_absence` (~104 tokens)

Approve or decline an absence

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

Input parameters:

- `absence_id` (integer, required): Absence (absentee) id, e.g. from shiftbase_list_absences with status Pending.
- `decision` (string, required): Approved or Declined.
- `notify_employee` (boolean): Notify the employee (default false).

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/io-usefulapi-shiftbase/shiftbase#diagnostics

## Score history

- 2026-10-17: 65
- 2026-10-16: 65
- 2026-10-15: 65
- 2026-10-14: 64
- 2026-10-13: 64
- 2026-10-12: 61
- 2026-10-10: 60

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

## Links

- Remote endpoint: https://shiftbase.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/shiftbase/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-shiftbase/shiftbase.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-shiftbase/shiftbase.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-shiftbase/shiftbase