Interact with Microsoft 365 and Office services through the Microsoft Graph API.
Bedrijfsrooster MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read employees, contracts, timetable shifts, availability and reports in Bedrijfsrooster.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http bedrijfsrooster-mcp-by-usefulapi https://bedrijfsrooster.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# bedrijfsrooster_get_configuration, bedrijfsrooster_list_users, bedrijfsrooster_list_contracts and 3 more
Bedrijfsrooster MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http bedrijfsrooster-mcp-by-usefulapi https://bedrijfsrooster.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get the company this access token belongs to: its id and name, its group, and its locations, departments, functions and shift types. Call this first. The ids it returns are the filters for the other tools. Bedrijfsrooster API: GET /configuration.
No parameter schema on file.
List the employees (CompanyUsers) with an active or future employment in the company, optionally within a period. Set extendedDetails only when the user asks for personal details: it adds birthday, email and address. Bedrijfsrooster API: GET /users.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| periodStart | string | no | Only employees with an active contract on or after this date. |
| periodEnd | string | no | Only employees with an active contract on or before this date. |
| snapshotDate | string | no | Date for date-bound computed fields. Default: today, or periodEnd. |
| extendedDetails | boolean | no | Add personal details (birthday, email, address). Default false. |
List the contracts between the company and its employees that are active at the snapshot date or within a period. Bedrijfsrooster API: GET /contracts.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| periodStart | string | no | Only contracts on or after this date. |
| periodEnd | string | no | Only contracts on or before this date. |
| snapshotDate | string | no | Date for date-bound computed fields. Default: today, or periodEnd. |
List the shifts of the company timetable: scheduled work shifts, availability, relief (vacation, days off) and non-attendance (sick days, no-shows). Choose which kinds to include with the shifts* flags. The reply is paged: use pageIndex (from 1) and itemsPerPage (1 to 1000), or disablePaging for a single reply. Bedrijfsrooster API: GET /timetable.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| periodStart | string | no | A date, or a date-time such as 2026-11-06 09:00:00 or 2026-11-06T09:00:00+01:00. |
| periodEnd | string | no | A date, or a date-time such as 2026-11-06 09:00:00 or 2026-11-06T09:00:00+01:00. |
| status | string | no | Comma-separated status constants, for example "SHIFT_STATUS_VALIDATED,SHIFT_STATUS_SCHEDULED". |
| updatedAfter | string | no | Only shifts whose timetable data changed after this date-time. |
| shiftsNormal | boolean | no | Include scheduled work shifts. |
| shiftsAvailable | boolean | no | Include availability overrides set by employees. |
| shiftsRelief | boolean | no | Include relief (vacation, planned days off). |
| shiftsNonAttendance | boolean | no | Include non-attendance (sick days, no-shows). |
| shiftData | boolean | no | Attach the shift data items that management or employees registered. |
| companyUserId | integer | no | Only shifts of this employee id. |
| companyLocationId | integer | no | Only shifts at this location id. |
| companyFunctionId | integer | no | Only shifts of this function id. |
| companyDepartmentId | integer | no | Only shifts of this department id. |
| itemsPerPage | integer | no | Shifts per page, 1 to 1000 (default 1000). |
| pageIndex | integer | no | Page number, starting at 1. |
| disablePaging | boolean | no | Return one reply without paging. Use only for small periods. |
Get the stored result of one finished Bedrijfsrooster report by its reportId, for example the relief hours balance. A report that is still running returns HTTP 409 with its percentage_complete: call again later. Needs the company:reports:read integration permission. Bedrijfsrooster API: GET /reports.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reportId | integer | yes | The report id as the Bedrijfsrooster app shows it. |
Get the availability (beschikbaarheid) per date, for each employee (companyUser) or each function (companyFunction). Use periodStart and periodEnd together, within one month (up to 31 days). Needs the company:availability:read integration permission. Bedrijfsrooster API: GET /availability.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entity | string | yes | companyUser: hours per employee and date. companyFunction: headcount per function and date. |
| periodStart | string | no | First date. Give periodEnd too. Default: first day of this month. |
| periodEnd | string | no | Last date. Give periodStart too. Default: last day of this month. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Bedrijfsrooster MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| bedrijfsrooster_get_configuration | no tags | |
| bedrijfsrooster_list_users | no tags | |
| bedrijfsrooster_list_contracts | no tags | |
| bedrijfsrooster_list_timetable | no tags | |
| bedrijfsrooster_get_report | no tags | |
| bedrijfsrooster_get_availability | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Bedrijfsrooster MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.