io.usefulapi/when-i-work
REMOTE · WHEN-I-WORK.USEFULAPI.IO · SCANNED OCT 4
Check shifts, time clock entries, time-off requests, swaps and availability, and manage shifts.
Available components
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 Security89
- 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3676 tokens (~175/item across 21 items; 21 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 Management13
- Stability observed for 4 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
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 21 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
How do I install the io.usefulapi/when-i-work MCP server?
io.usefulapi/when-i-work is a hosted endpoint at https://when-i-work.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 · when-i-work.usefulapi.io
claude mcp add --transport http io-usefulapi-when-i-work 'https://when-i-work.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-when-i-work": {
"url": "https://when-i-work.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-when-i-work": {
"type": "http",
"url": "https://when-i-work.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-when-i-work] url = "https://when-i-work.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-when-i-work": {
"type": "remote",
"url": "https://when-i-work.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-when-i-work --url 'https://when-i-work.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-when-i-work:
url: "https://when-i-work.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-when-i-work": {
"Transport": "http",
"Url": "https://when-i-work.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-when-i-work -t streamable-http -u 'https://when-i-work.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-when-i-work": {
"type": "http",
"url": "https://when-i-work.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 0
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +52
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
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 4 Oct 2026 · Probed https://when-i-work.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 when-i-work.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 | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://when-i-work.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://when-i-work.usefulapi.io/.well-known/oauth-protected-resource/mcp" Protected resource metadata
| Document | https://when-i-work.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://when-i-work.usefulapi.io/mcp |
| Authorisation server | https://when-i-work.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://when-i-work.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://when-i-work.usefulapi.io/mcp | HTTPS enforced | 301 | https://when-i-work.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 →
wheniwork_create_shift Create a shift ~263
Create one shift on a schedule — assigned to a user, or open (user_id 0). Created as a draft unless published is true. Undo by editing it or unpublishing. When I Work: POST /2/shifts.
| Name | Type | Req | Description |
|---|---|---|---|
| break_time | number | – | Unpaid break length in hours, e.g. 0.5. |
| color | string | – | Hex colour without #, e.g. cc0000. |
| end_time | string | yes | Shift end, date-time with offset. |
| is_shared | boolean | – | For an open shift: a shared open shift. |
| location_id | integer | yes | The schedule (location) the shift belongs to id. |
| notes | string | – | Shift notes shown to the employee. |
| position_id | integer | – | Position for the shift. |
| published | boolean | – | Publish it immediately (default: draft). |
| site_id | integer | – | Job site for the shift. |
| start_time | string | yes | Shift start, date-time with offset, e.g. 2026-10-05T08:00:00-05:00. |
| user_id | integer | – | The user to assign. 0 (or omitted on create) makes it an open shift. |
No output schema declared.
No examples provided.
wheniwork_create_time_off_request Create a time-off request ~166
Create a time-off request for a user (default the calling user). It starts pending; cancel it with wheniwork_update_time_off_request (status 1). Get type ids from wheniwork_list_time_off_types. When I Work: POST /2/requests.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | yes | End of the time off, full date-time. |
| hours | number | – | Hours of paid time off to use. |
| paid | boolean | – | Whether it is paid time off. |
| start_time | string | yes | Start of the time off, full date-time. |
| type_id | integer | – | Time-off type id (Personal, Sick, Holiday...). |
| user_id | integer | – | Who is taking time off (default the calling user). |
No output schema declared.
No examples provided.
wheniwork_get_account Get the account ~60
Fetch the When I Work account (workplace) the token acts on — company name, plan and settings; for a parent account also its child accounts. A cheap way to confirm the credentials work. When I Work: GET /2/account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wheniwork_get_shift Get one shift ~129
Fetch one shift by id, including its breaks and publish state. When I Work: GET /2/shifts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| include_repeating_shifts_to | string | – | Also expand the shift's repeating series up to this date. Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| shift_id | integer | yes | The shift id. |
No output schema declared.
No examples provided.
wheniwork_get_time_off_request Get one time-off request ~54
Fetch one time-off request by id, with its message thread and users. When I Work: GET /2/requests/{request_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | integer | yes | The time-off request id. |
No output schema declared.
No examples provided.
wheniwork_get_user Get one user ~51
Fetch one user by id — name, email, role, positions, schedules, wage. When I Work: GET /2/users/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| user_id | integer | yes | The user id. |
No output schema declared.
No examples provided.
wheniwork_list_annotations List schedule annotations ~218
List schedule annotations — announcements, business-closed days and blackout dates when time off is not allowed. Defaults to today through one year out. When I Work: GET /2/annotations.
| Name | Type | Req | Description |
|---|---|---|---|
| end_date | string | – | End of the range (default one year after start). Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| no_time_off | boolean | – | Only annotations that block time off. |
| start_date | string | – | Start of the range (default the start of today). Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
No output schema declared.
No examples provided.
wheniwork_list_availability List availability ~241
List availability events — when people said they can or cannot work, including recurring patterns that fall in the window. Defaults to the caller, from now to two weeks out. When I Work: GET /2/availabilityevents.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | End of the window (default two weeks from now). Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| include_all | boolean | – | Everyone's availability, not just one user's — managers only. |
| start | string | – | Start of the window (default now). Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| user_id | integer | – | Whose availability (default the calling user). |
No output schema declared.
No examples provided.
wheniwork_list_eligible_users_for_shift List users eligible for an open shift ~294
Find who could take an open shift — either an existing shift (shift_id) or a hypothetical one (start, end, position_id and location_id all required). When I Work: GET /2/shifts/eligible.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | End of the potential shift (required without shift_id). Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| include_objects | boolean | – | Include the users' schedules and positions in the output. |
| is_shared | boolean | – | Whether it is a shared open shift. |
| location_id | integer | – | Schedule of the potential shift (required without shift_id). |
| position_id | integer | – | Position of the potential shift (required without shift_id). |
| shift_id | integer | – | An existing shift's id. |
| start | string | – | Start of the potential shift (required without shift_id). Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
No output schema declared.
No examples provided.
wheniwork_list_locations List schedules (locations) ~64
List the schedules in the account. The API calls a schedule a "location"; its id is the location_id every shift belongs to. When I Work: GET /2/locations.
| Name | Type | Req | Description |
|---|---|---|---|
| only_unconfirmed | boolean | – | Only schedules whose address is unconfirmed. |
No output schema declared.
No examples provided.
wheniwork_list_positions List positions ~49
List the positions (job roles such as Cashier or Dishwasher) in the account. When I Work: GET /2/positions.
| Name | Type | Req | Description |
|---|---|---|---|
| show_deleted | boolean | – | Include deleted positions. |
No output schema declared.
No examples provided.
wheniwork_list_shift_swaps List shift swaps and drops ~330
List shift requests: swaps, drops and alerts, with the shifts and users involved. Status: 0 pending, 1 approved, 2 declined, 3 completed, 4 canceled, 5 expired. Type: 1 swap, 2 drop, 3 alert. start and end must be given together. When I Work: GET /2/swaps.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | End of the shift window (give with start). Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| limit | integer | – | Maximum number of results. |
| open_only | boolean | – | Only open swaps. |
| page | integer | – | Page of results to load (the response says whether there are `more`). |
| shift_id | array | – | One or more shift ids. |
| start | string | – | Start of the shift window (give with end). Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| status | array | – | One or more statuses. |
| type | array | – | One or more types. |
| user_id | array | – | One or more user ids. |
No output schema declared.
No examples provided.
wheniwork_list_shifts List shifts ~437
List scheduled shifts in a time window — who works when, where and in which position — optionally including open shifts and unpublished drafts. Answers "who is on on Friday?" and "what open shifts are left?". When I Work: GET /2/shifts.
| Name | Type | Req | Description |
|---|---|---|---|
| all_locations | boolean | – | Include shifts from all schedules. |
| deleted | boolean | – | Also return deleted_ids: shifts deleted in the window. |
| end | string | – | End of the window. Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| include_allopen | boolean | – | Include open shifts across all schedules — manager or admin. |
| include_onlyopen | boolean | – | Return only open shifts. |
| include_open | boolean | – | Include open (unassigned) shifts from the user's schedules. |
| include_repeating_shifts_to | string | – | Also expand repeating shift series up to this date. Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| include_swaps | boolean | – | Include swap requests attached to the shifts. |
| limit | integer | – | Maximum number of results. |
| location_id | array | – | One or more schedule (location) ids. |
| start | string | – | Start of the window. Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| unpublished | boolean | – | Include unpublished (draft) shifts — supervisor or above. |
| user_id | integer | – | Only this user's shifts. |
No output schema declared.
No examples provided.
wheniwork_list_time_off_requests List time-off requests ~235
List time-off requests in a date range, with the requesting users. Status: 0 pending, 1 canceled, 2 accepted, 3 expired, 4 denied. When I Work: GET /2/requests.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | End date, yyyy-mm-dd. |
| include_deleted_users | boolean | – | Include requests made by deleted users. |
| limit | integer | – | Maximum number of results. |
| location_id | integer | – | Only requests for this schedule. |
| max_id | integer | – | Only requests created before this request id. |
| page | integer | – | Page of results to load (the response says whether there are `more`). |
| since_id | integer | – | Only requests created after this request id. |
| sortby | string | – | 'created' sorts newest first; anything else sorts by status then last update. |
| start | string | – | Start date, yyyy-mm-dd. |
| status | integer | – | Only requests with this status. |
| type | integer | – | Only this request type. |
| user_id | array | – | One or more user ids. |
No output schema declared.
No examples provided.
wheniwork_list_time_off_types List time-off types ~56
List the time-off types (e.g. Personal, Sick, Holiday) and whether each allows paid time. Their ids are the type_id for a new request. When I Work: GET /2/requesttypes.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
wheniwork_list_times List clocked times (timesheets) ~300
List clocked time entries — actual hours worked, clock-in/out times, length and approval state. Use only_open to see who is clocked in right now. When I Work: GET /2/times.
| Name | Type | Req | Description |
|---|---|---|---|
| end | string | – | End of the window. Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| only_open | boolean | – | Only times with no end yet (people currently clocked in). |
| start | string | – | Start of the window. Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| updated_at | string | – | Only times updated since this timestamp. Date-time, e.g. 2026-10-05T08:00:00-05:00 (When I Work's own examples also use RFC 2822, e.g. "Mon, 05 Oct 2026 08:00:00 -0500"). |
| user_id | array | – | One or more user ids. |
No output schema declared.
No examples provided.
wheniwork_list_users List users ~159
List the employees, supervisors, managers and admins in the account, optionally limited to some schedules or searched by name/email. Role codes: 1 admin, 2 manager, 3 employee, 5 supervisor. When I Work: GET /2/users.
| Name | Type | Req | Description |
|---|---|---|---|
| location_id | array | – | One or more schedule (location) ids. |
| only_deleted | boolean | – | Only deleted/archived users (supervisor or above). |
| only_pending | boolean | – | Only pending users. |
| search | string | – | Search first name, last name or email. |
| show_deleted | boolean | – | Include deleted users (supervisor or above). |
| show_pending | boolean | – | Include users who have not accepted their invite (default true). |
No output schema declared.
No examples provided.
wheniwork_publish_shifts Publish shifts ~62
Publish draft shifts so employees can see them. Publishing does not itself send notifications. Undo with wheniwork_unpublish_shifts. When I Work: POST /2/shifts/publish.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | The shift ids to publish. |
No output schema declared.
No examples provided.
wheniwork_unpublish_shifts Unpublish shifts ~58
Return published shifts to draft, hiding them from employees. Undo with wheniwork_publish_shifts. When I Work: POST /2/shifts/unpublish.
| Name | Type | Req | Description |
|---|---|---|---|
| ids | array | yes | The shift ids to unpublish. |
No output schema declared.
No examples provided.
wheniwork_update_shift Update a shift ~294
Change a shift — reassign it, move it, change position or notes. When I Work requires start_time, end_time and location_id on every update, so fetch the shift first and pass them back. This tool never sends a breaks array; When I Work documents that breaks omitted from an update's breaks list are removed, so re-check the shift's breaks afterwards. When I Work: PUT /2/shifts/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| break_time | number | – | Unpaid break length in hours, e.g. 0.5. |
| color | string | – | Hex colour without #, e.g. cc0000. |
| end_time | string | yes | Shift end (required by the API even if unchanged). |
| is_shared | boolean | – | For an open shift: a shared open shift. |
| location_id | integer | yes | The schedule (location) id. |
| notes | string | – | Shift notes shown to the employee. |
| position_id | integer | – | Position for the shift. |
| published | boolean | – | Publish it immediately (default: draft). |
| shift_id | integer | yes | The shift id. |
| site_id | integer | – | Job site for the shift. |
| start_time | string | yes | Shift start (required by the API even if unchanged). |
| user_id | integer | – | The user to assign. 0 (or omitted on create) makes it an open shift. |
No output schema declared.
No examples provided.
wheniwork_update_time_off_request Approve, deny or change a time-off request ~156
Change a time-off request: set its status (0 pending, 1 canceled, 2 accepted/approved, 3 expired, 4 denied) and/or its dates or hours. Reversible — set the status back. start_time and end_time must be given together. When I Work: PUT /2/requests/{request_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| end_time | string | – | New end, full date-time (give with start_time). |
| hours | number | – | Hours of paid time off to use. |
| request_id | integer | yes | The time-off request id. |
| start_time | string | – | New start, full date-time (give with end_time). |
| status | integer | – | New status. |
No output schema declared.
No examples provided.
What is the io.usefulapi/when-i-work MCP server?
io.usefulapi/when-i-work is an MCP server listed in the public MCP registry as io.usefulapi/when-i-work. Check shifts, time clock entries, time-off requests, swaps and availability, and manage shifts. This page covers its hosted endpoint (https://when-i-work.usefulapi.io/mcp).
Is the io.usefulapi/when-i-work MCP server safe to use?
io.usefulapi/when-i-work scores 76 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 io.usefulapi/when-i-work MCP server expose?
io.usefulapi/when-i-work exposes 21 tools: wheniwork_get_account, wheniwork_list_users, wheniwork_get_user, wheniwork_list_locations, wheniwork_list_positions, and 16 more. Their descriptions and schemas cost roughly 3,676 tokens of context every time the server is loaded.
Does the io.usefulapi/when-i-work MCP server require authentication?
Yes. io.usefulapi/when-i-work 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 io.usefulapi/when-i-work MCP server still maintained?
io.usefulapi/when-i-work is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.