Skip to content

Shiftbase MCP by usefulapi

io.usefulapi/shiftbaseusefulapi.iostreamable-httpv1.31.5Scanned

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

22 tools: 4 can delete or cancel things and 18 only read.

Tools: 4 delete, 0 irreversible, 0 write, 18 read.
  • Reads private data · 3
  • Reads text others write · 5
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

4 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Shiftbase MCP by usefulapi can do

The Shiftbase MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 22 tools. It can delete or cancel things (4 tools: shiftbase_create_roster, shiftbase_update_roster, shiftbase_request_absence and shiftbase_review_absence). 18 tools only read.

3 tools read private data (shiftbase_list_users, shiftbase_get_user and shiftbase_list_departments); 5 tools bring in text other people can write (shiftbase_get_user, shiftbase_create_roster, shiftbase_update_roster and 2 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 25, 2026, version 1.31.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

22 tools

Deletes or cancels 4Claude Code: deny
  • shiftbase_create_rosterWRITE: 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.Reads text others writeNo findings

    Why it is in this group

    • The name "shiftbase_create_roster" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Schedule a shift
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • shiftbase_request_absenceWRITE: add an absence (leave/time-off request) for an employee.Reads text others writeNo findings

    Why it is in this group

    • The name "shiftbase_request_absence" says "request": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Request an absence
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • shiftbase_review_absenceWRITE: approve or decline an absence request.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "write": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Approve or decline an absence
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
  • shiftbase_update_rosterWRITE: change a scheduled shift: move it to another date, time, employee, team or shift type, or change its break or note.Reads text others writeNo findings

    Why it is in this group

    • The name "shiftbase_update_roster" says "update": a word for a change.
    • The server marks it destructive (destructiveHint: true).

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Change a scheduled shift
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: true
Only reads 18Show 18 read-only tools
  • shiftbase_get_absenceOne absence by id, with the per-day hours and who reviewed it.No findings

    Why it is in this group

    • The name "shiftbase_get_absence" says "get": a word for reading.
    Description, as the server wrote it
    One absence by id, with the per-day hours and who reviewed it. GET /absentees/{absenteeId}.

    Annotations the server declares

    • title: Get absence
    • readOnlyHint: true
  • shiftbase_get_accountThe Shiftbase account this API key belongs to: company, country, time zone, working-day start/end, plan facts.No findings

    Why it is in this group

    • The name "shiftbase_get_account" says "get": a word for reading.
    Description, as the server wrote it
    The Shiftbase account this API key belongs to: company, country, time zone, working-day start/end, plan facts. GET /accounts.

    Annotations the server declares

    • title: Get account
    • readOnlyHint: true
  • shiftbase_get_availabilityEmployee availability (available / unavailable, all day or from a time) for a date range of at most 62 days, from Shiftbase's availability report.No findings

    Why it is in this group

    • The name "shiftbase_get_availability" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: Get employee availability
    • readOnlyHint: true
  • shiftbase_get_expected_absence_hoursHow 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.No findings

    Why it is in this group

    • The name "shiftbase_get_expected_absence_hours" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Get expected absence hours
    • readOnlyHint: true
  • shiftbase_get_rosterOne scheduled shift by its occurrence_id, with the employee, shift type, team and who created/changed it.No findings

    Why it is in this group

    • The name "shiftbase_get_roster" says "get": a word for reading.
    Description, as the server wrote it
    One scheduled shift by its occurrence_id, with the employee, shift type, team and who created/changed it. GET /rosters/{occurrenceId}.

    Annotations the server declares

    • title: Get scheduled shift
    • readOnlyHint: true
  • shiftbase_get_timesheetOne timesheet by id, with its clocked breaks.No findings

    Why it is in this group

    • The name "shiftbase_get_timesheet" says "get": a word for reading.
    Description, as the server wrote it
    One timesheet by id, with its clocked breaks. GET /timesheets/{timesheetId}.

    Annotations the server declares

    • title: Get timesheet
    • readOnlyHint: true
  • shiftbase_get_userOne employee by user id or email address, with teams and departments.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "shiftbase_get_user" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    One employee by user id or email address, with teams and departments. GET /users/{identifier}.

    Annotations the server declares

    • title: Get employee
    • readOnlyHint: true
  • shiftbase_list_absence_typesList absence types (e.g.No findings

    Why it is in this group

    • The name "shiftbase_list_absence_types" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List absence types
    • readOnlyHint: true
  • shiftbase_list_absencesList 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/Pend…No findings

    Why it is in this group

    • The name "shiftbase_list_absences" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List absences
    • readOnlyHint: true
  • shiftbase_list_clocked_inWho is clocked in right now: employee, since when, their scheduled shift, team, department and location.No findings

    Why it is in this group

    • The name "shiftbase_list_clocked_in" says "list": a word for reading.
    Description, as the server wrote it
    Who is clocked in right now: employee, since when, their scheduled shift, team, department and location. GET /timesheets/clock.

    Annotations the server declares

    • title: List clocked-in employees
    • readOnlyHint: true
  • shiftbase_list_departmentsList departments (sites/branches that own teams, shifts and schedules) with address and timesheet/clocking settings.Reads private dataNo findings

    Why it is in this group

    • The name "shiftbase_list_departments" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "branch": it reads repositories.
    Description, as the server wrote it
    List departments (sites/branches that own teams, shifts and schedules) with address and timesheet/clocking settings. GET /departments.

    Annotations the server declares

    • title: List departments
    • readOnlyHint: true
  • shiftbase_list_locationsList active locations (addresses that group departments).No findings

    Why it is in this group

    • The name "shiftbase_list_locations" says "list": a word for reading.
    Description, as the server wrote it
    List active locations (addresses that group departments). GET /locations.

    Annotations the server declares

    • title: List locations
    • readOnlyHint: true
  • shiftbase_list_open_shiftsList open (unassigned) shifts that employees can pick up, for a date range of at most 62 days (default: today).No findings

    Why it is in this group

    • The name "shiftbase_list_open_shifts" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List open shifts
    • readOnlyHint: true
  • shiftbase_list_rostersList 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…No findings

    Why it is in this group

    • The name "shiftbase_list_rosters" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List scheduled shifts
    • readOnlyHint: true
  • shiftbase_list_shift_typesList shift types (the templates a scheduled shift uses: name, short name, default start/end time and break), optionally for one department.No findings

    Why it is in this group

    • The name "shiftbase_list_shift_types" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List shift types
    • readOnlyHint: true
  • shiftbase_list_teamsList teams (the rows of the schedule within a department), optionally for one department.No findings

    Why it is in this group

    • The name "shiftbase_list_teams" says "list": a word for reading.
    Description, as the server wrote it
    List teams (the rows of the schedule within a department), optionally for one department. GET /teams.

    Annotations the server declares

    • title: List teams
    • readOnlyHint: true
  • shiftbase_list_timesheetsList timesheets (worked hours: clock in/out, breaks, total, status Approved/Declined/Pending, wage and surcharges) for a date range of at most 62 days.No findings

    Why it is in this group

    • The name "shiftbase_list_timesheets" says "list": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List timesheets
    • readOnlyHint: true
  • shiftbase_list_usersList employees (users) with their teams and departments, contact details, employee number, start/end dates and plus-min hours balance.Reads private dataNo findings

    Why it is in this group

    • The name "shiftbase_list_users" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "list" and "contact": it reads contacts.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List employees
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data3
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 20, 2026, 19:37 UTC, unchanged since Oct 29, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://shiftbase.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://shiftbase.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://shiftbase.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://shiftbase.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

Pinned to version 1.31.5. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__shiftbase__shiftbase_get_account",
      "mcp__shiftbase__shiftbase_list_users",
      "mcp__shiftbase__shiftbase_get_user",
      "mcp__shiftbase__shiftbase_list_departments",
      "mcp__shiftbase__shiftbase_list_teams",
      "mcp__shiftbase__shiftbase_list_locations",
      "mcp__shiftbase__shiftbase_list_shift_types",
      "mcp__shiftbase__shiftbase_list_rosters",
      "mcp__shiftbase__shiftbase_get_roster",
      "mcp__shiftbase__shiftbase_list_open_shifts",
      "mcp__shiftbase__shiftbase_get_availability",
      "mcp__shiftbase__shiftbase_list_timesheets",
      "mcp__shiftbase__shiftbase_get_timesheet",
      "mcp__shiftbase__shiftbase_list_clocked_in",
      "mcp__shiftbase__shiftbase_list_absences",
      "mcp__shiftbase__shiftbase_get_absence",
      "mcp__shiftbase__shiftbase_list_absence_types",
      "mcp__shiftbase__shiftbase_get_expected_absence_hours"
    ],
    "ask": [],
    "deny": [
      "mcp__shiftbase__shiftbase_create_roster",
      "mcp__shiftbase__shiftbase_update_roster",
      "mcp__shiftbase__shiftbase_request_absence",
      "mcp__shiftbase__shiftbase_review_absence"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as shiftbase. Review it before you use it.

Capability tags behind 7 rules
  • mcp__shiftbase__shiftbase_list_users private-data
  • mcp__shiftbase__shiftbase_get_user private-data, untrusted-input
  • mcp__shiftbase__shiftbase_list_departments private-data
  • mcp__shiftbase__shiftbase_create_roster untrusted-input
  • mcp__shiftbase__shiftbase_update_roster untrusted-input
  • mcp__shiftbase__shiftbase_request_absence untrusted-input
  • mcp__shiftbase__shiftbase_review_absence untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/shiftbase/verify?hash=06566c5829890bc8df3d97c98aab5c9b688b71b45258486c156935f2d248be7b" | jq -e '.changed == false'

Pinned hash 06566c582989, from Oct 25, 2026, 23:19 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/shiftbase/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/shiftbase
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/shiftbase.svg)](https://radar.anlyon.com/servers/io.usefulapi/shiftbase)

Source: MCP Registry · repository. Synced Nov 20, 2026, 20:18 UTC.

Shiftbase MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Shiftbase MCP by usefulapi safe?

No scan can promise that. What its definitions show: 22 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Shiftbase MCP by usefulapi delete data?

Yes. 4 tools can delete, cancel or revoke something: shiftbase_create_roster, shiftbase_update_roster, shiftbase_request_absence and shiftbase_review_absence.

Can the Shiftbase MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Shiftbase MCP by usefulapi have?

22 tools: 4 destructive, 18 read. shiftbase_create_roster, shiftbase_update_roster, shiftbase_request_absence, shiftbase_review_absence, shiftbase_get_account, shiftbase_list_users, shiftbase_get_user, shiftbase_list_departments and 14 more.

Does the Shiftbase MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Shiftbase MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Shiftbase MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 25, 2026.