io.usefulapi/deputy
REMOTE · DEPUTY.USEFULAPI.IO · SCANNED OCT 3
See rosters, timesheets, leave and staff in Deputy, and create shifts, leave and memos.
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 Usability73
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3270 tokens (~155/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 Management10
- Stability observed for 3 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/deputy MCP server?
io.usefulapi/deputy is a hosted endpoint at https://deputy.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 · deputy.usefulapi.io
claude mcp add --transport http io-usefulapi-deputy 'https://deputy.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-deputy": {
"url": "https://deputy.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-deputy": {
"type": "http",
"url": "https://deputy.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-deputy] url = "https://deputy.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-deputy": {
"type": "remote",
"url": "https://deputy.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-deputy --url 'https://deputy.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-deputy:
url: "https://deputy.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-deputy": {
"Transport": "http",
"Url": "https://deputy.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-deputy -t streamable-http -u 'https://deputy.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-deputy": {
"type": "http",
"url": "https://deputy.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 +53
- 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 3 Oct 2026 · Probed https://deputy.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 deputy.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://deputy.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://deputy.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://deputy.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://deputy.usefulapi.io/mcp |
| Authorisation server | https://deputy.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://deputy.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://deputy.usefulapi.io/mcp | HTTPS enforced | 301 | https://deputy.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 →
deputy_add_unavailability Add unavailability for an employee ~166
Record a time an employee cannot work (one-off, or recurring with an RFC 5545-style rule such as FREQ WEEKLY, INTERVAL 1, BYDAY MO). Auto-scheduling then skips them. Deputy: POST /api/v1/supervise/unavail.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | string | – | Note the manager sees. Default empty. |
| employee_id | integer | yes | The employee id. |
| end_time | – | yes | Unavailability end: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
| recurrence | object | – | Omit for a one-off block. |
| start_time | – | yes | Unavailability start: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
No output schema declared.
No examples provided.
deputy_approve_timesheet Approve a timesheet ~69
Approve one timesheet's times as a supervisor. Approved timesheets flow toward payroll export, so check it first with deputy_get_timesheet. Deputy: POST /api/v1/supervise/timesheet/approve.
| Name | Type | Req | Description |
|---|---|---|---|
| timesheet_id | integer | yes | The timesheet id. |
No output schema declared.
No examples provided.
deputy_create_leave_request Create a leave request ~270
Add a leave request for an employee. By default it waits for manager approval (status 0); pass status 1 only when your system is the source of truth and the leave is already approved. Deputy tracks leave in hours, so give exact start and end times. Find leave type ids with deputy_query_resource on LeaveRules. Deputy: POST /api/v1/resource/Leave.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_comment | string | – | Manager's comment, when status is 1. |
| comment | string | yes | The employee's note to the manager. |
| employee_id | integer | yes | The employee id. |
| end_date | string | yes | Last day, YYYY-MM-DD. |
| end_time | – | yes | Leave end: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
| leave_rule_id | integer | yes | Leave type (LeaveRules id), e.g. annual leave. |
| location_id | integer | yes | Location (Company id) the leave is recorded against. |
| start_date | string | yes | First day, YYYY-MM-DD. |
| start_time | – | yes | Leave start: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
| status | – | – | 0 awaiting approval (default), 1 already approved. |
No output schema declared.
No examples provided.
deputy_create_memo Post a memo ~132
Post a memo to a location's news feed, optionally requiring staff to confirm they read it, or targeted to specific locations or users. Visible to staff immediately. Deputy: PUT /api/v1/supervise/memo.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The memo text. |
| location_id | integer | yes | Location (Company id) to post to. |
| location_ids | array | – | Also show at these locations. |
| require_confirm | boolean | – | Ask staff to confirm they have read it. Default false. |
| user_ids | array | – | Only these USER ids (not employee ids) receive it. |
No output schema declared.
No examples provided.
deputy_create_shift Create a shift ~280
Add a shift to the roster, assigned to an employee or left open. Created as a DRAFT unless publish is true (publishing can notify the employee). Deputy returns an empty 200 on success — use deputy_list_shifts to find the new shift's id. Deputy: POST /api/v1/supervise/roster.
| Name | Type | Req | Description |
|---|---|---|---|
| area_id | integer | yes | Area (OperationalUnit id) the shift is for. |
| comment | string | – | Comment shown on the shift. |
| confirmed | boolean | – | Mark the shift as confirmed. |
| employee_id | integer | – | Employee to put on the shift. Omit (and set open: true) for an unfilled shift. |
| end_time | – | yes | Shift end: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
| force_overwrite | boolean | – | Overwrite a clashing shift for the same employee. Default false. |
| mealbreak_minutes | integer | – | Unpaid meal break length in minutes. |
| open | boolean | – | Show the shift as open for employees to claim. |
| publish | boolean | – | Publish now. Publishing can notify the employee. Default false (draft). |
| start_time | – | yes | Shift start: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
No output schema declared.
No examples provided.
deputy_describe_resource Describe a Deputy resource ~92
Return a Resource API object's field list, field types and joinable associations — what deputy_query_resource can filter, sort and join on. Deputy: GET /api/v1/resource/{Object}/INFO.
| Name | Type | Req | Description |
|---|---|---|---|
| object | string | yes | Resource API object. Deputy names: Company = location, OperationalUnit = area, Roster = shift, LeaveRules = leave types, TimesheetPayReturn = approved pay lines. |
No output schema declared.
No examples provided.
deputy_get_employee Get one employee ~54
Fetch one employee's details as a supervisor sees them — contact, locations, role and employment. Deputy: GET /api/v1/supervise/employee/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | integer | yes | The employee id. |
No output schema declared.
No examples provided.
deputy_get_employee_unavailability Get an employee's unavailability ~61
List the times one employee has marked themselves (or been marked) unavailable to work — check before rostering them. Deputy: GET /api/v1/supervise/unavail/{employeeId}.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | integer | yes | The employee id. |
No output schema declared.
No examples provided.
deputy_get_shift Get one shift ~46
Fetch one shift (Roster record) by id. Deputy: GET /api/v1/resource/Roster/{id}.
| Name | Type | Req | Description |
|---|---|---|---|
| shift_id | integer | yes | The shift (Roster) id. |
No output schema declared.
No examples provided.
deputy_get_timesheet Get one timesheet ~55
Fetch one timesheet's full details, including breaks and approval state. Deputy: GET /api/v1/supervise/timesheet/{id}/details.
| Name | Type | Req | Description |
|---|---|---|---|
| timesheet_id | integer | yes | The timesheet id. |
No output schema declared.
No examples provided.
deputy_list_areas List areas ~152
List areas (Deputy OperationalUnits — the rosterable sections of a location, e.g. Kitchen, Front of house). Shifts and timesheets belong to an area. Optionally only one location's areas. Deputy: GET /api/v1/resource/OperationalUnit, or POST .../OperationalUnit/QUERY when filtered.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | Only active (true) or inactive (false) areas. |
| location_id | integer | – | Only areas of this location (Company id). |
| max | integer | – | Page size, 1-500 (Deputy's cap). Default 100. |
| start | integer | – | Pagination offset (0-based). Pass the previous page's next_start. |
No output schema declared.
No examples provided.
deputy_list_employees List employees ~147
Search employees by name, location or active status. Returns Id, DisplayName, Company (main location), Active, StartDate, Role and more. Deputy: POST /api/v1/resource/Employee/QUERY.
| Name | Type | Req | Description |
|---|---|---|---|
| active | boolean | – | true = current staff only; false = terminated/inactive only. |
| location_id | integer | – | Only employees whose main location is this Company id. |
| max | integer | – | Page size, 1-500 (Deputy's cap). Default 100. |
| name_contains | string | – | Only employees whose DisplayName contains this text. |
| start | integer | – | Pagination offset (0-based). Pass the previous page's next_start. |
No output schema declared.
No examples provided.
deputy_list_leave List leave requests ~242
Search leave requests by employee, location, status and time window. Status: 0 awaiting approval, 1 approved, 2 declined, 3 cancelled, 4 date approved without pay, 5 pay approved without date. Start/End are unix; LeaveRule is the leave type id. Deputy: POST /api/v1/resource/Leave/QUERY.
| Name | Type | Req | Description |
|---|---|---|---|
| employee_id | integer | – | Only this employee's leave. |
| from | – | – | Only leave starting at or after this time: a unix timestamp in seconds, or an ISO 8601 date/datetime (include an offset for local times). |
| location_id | integer | – | Only leave against this location (Company id). |
| max | integer | – | Page size, 1-500 (Deputy's cap). Default 100. |
| start | integer | – | Pagination offset (0-based). Pass the previous page's next_start. |
| status | integer | – | Only this status (0-5, see description). |
| to | – | – | Only leave starting at or before this time: a unix timestamp in seconds, or an ISO 8601 date/datetime (include an offset for local times). |
No output schema declared.
No examples provided.
deputy_list_locations List locations ~47
List the install's locations (workplaces). Deputy calls a location a Company; its Id is what other tools take as location_id. Deputy: GET /api/v1/resource/Company.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
deputy_list_shifts List shifts ~261
Search the roster (scheduled shifts) by time window, employee, area, and published/open state. Each record has StartTime/EndTime (unix), StartTimeLocalized, Employee (0 or null when open), OperationalUnit (area), Published, Open, Cost and _DPMetaData with names. Deputy: POST /api/v1/resource/Roster/QUERY.
| Name | Type | Req | Description |
|---|---|---|---|
| area_id | integer | – | Only shifts in this area (OperationalUnit id). |
| employee_id | integer | – | Only this employee's shifts. |
| from | – | – | Only shifts starting at or after this time: a unix timestamp in seconds, or an ISO 8601 date/datetime (include an offset for local times). |
| max | integer | – | Page size, 1-500 (Deputy's cap). Default 100. |
| open | boolean | – | true = open (unfilled) shifts only. |
| published | boolean | – | true = published only; false = drafts only. |
| start | integer | – | Pagination offset (0-based). Pass the previous page's next_start. |
| to | – | – | Only shifts starting at or before this time: a unix timestamp in seconds, or an ISO 8601 date/datetime (include an offset for local times). |
No output schema declared.
No examples provided.
deputy_list_timesheets List timesheets ~294
Search timesheets (actual worked time) by time window, employee, area and approval state. Each record has StartTime/EndTime (unix; EndTime null while in progress), TotalTime (hours), Cost, TimeApproved, PayRuleApproved, IsInProgress, IsLeave, Roster (linked shift) and Exported. Deputy: POST /api/v1/resource/Timesheet/QUERY.
| Name | Type | Req | Description |
|---|---|---|---|
| area_id | integer | – | Only timesheets in this area (OperationalUnit id). |
| employee_id | integer | – | Only this employee's timesheets. |
| from | – | – | Only timesheets starting at or after this time: a unix timestamp in seconds, or an ISO 8601 date/datetime (include an offset for local times). |
| in_progress | boolean | – | true = only people currently on the clock. |
| max | integer | – | Page size, 1-500 (Deputy's cap). Default 100. |
| pay_approved | boolean | – | Filter on PayRuleApproved (approved for payroll export). |
| start | integer | – | Pagination offset (0-based). Pass the previous page's next_start. |
| time_approved | boolean | – | Filter on TimeApproved (supervisor approved the times). |
| to | – | – | Only timesheets starting at or before this time: a unix timestamp in seconds, or an ISO 8601 date/datetime (include an offset for local times). |
No output schema declared.
No examples provided.
deputy_publish_shifts Publish shifts ~115
Publish draft shifts so employees see them, choosing how they are notified: 1 SMS and email, 2 SMS, 3 email, 4 no notification, 5 confirmation required. Only the listed shift ids are published. Deputy: POST /api/v1/supervise/roster/publish.
| Name | Type | Req | Description |
|---|---|---|---|
| notify_mode | integer | yes | 1 SMS+email, 2 SMS, 3 email, 4 none, 5 confirmation required. |
| shift_ids | array | yes | Roster ids to publish. |
No output schema declared.
No examples provided.
deputy_query_resource Query any Deputy resource ~281
Run a Resource API search on any business object (leave types, pay rules, public holidays, memos, events, shift templates, pay lines, availability, sales data, …). `search` is Deputy's clause map, e.g. {"s1":{"field":"Employee","data":12,"type":"eq"}}; operators: eq ne gt lt ge le is 'is not' in 'not in' starts contains. Use deputy_describe_resource to see an object's fields and joins. Read-only. Deputy: POST /api/v1/resource/{Object}/QUERY.
| Name | Type | Req | Description |
|---|---|---|---|
| join | array | – | Related objects to expand inline, e.g. ["TimesheetObject"] on TimesheetPayReturn. |
| max | integer | – | Page size, 1-500 (Deputy's cap). Default 100. |
| object | string | yes | Resource API object. Deputy names: Company = location, OperationalUnit = area, Roster = shift, LeaveRules = leave types, TimesheetPayReturn = approved pay lines. |
| search | object | – | Clauses keyed by any id (s1, s2, …). All must match. |
| sort | object | – | Field → asc/desc, e.g. {"Id":"desc"}. |
| start | integer | – | Pagination offset (0-based). Pass the previous page's next_start. |
No output schema declared.
No examples provided.
deputy_update_shift Update a shift ~283
Change an existing shift's times, area, employee, break or comment. Send the full intended shift (same fields as create) — Deputy's update is the add call with the shift id. Deputy: POST /api/v1/supervise/roster with intRosterId.
| Name | Type | Req | Description |
|---|---|---|---|
| area_id | integer | yes | Area (OperationalUnit id) the shift is for. |
| comment | string | – | Comment shown on the shift. |
| confirmed | boolean | – | Mark the shift as confirmed. |
| employee_id | integer | – | Employee to put on the shift. Omit (and set open: true) for an unfilled shift. |
| end_time | – | yes | Shift end: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
| force_overwrite | boolean | – | Overwrite a clashing shift for the same employee. Default false. |
| mealbreak_minutes | integer | – | Unpaid meal break length in minutes. |
| open | boolean | – | Show the shift as open for employees to claim. |
| publish | boolean | – | Publish now. Publishing can notify the employee. Default false (draft). |
| shift_id | integer | yes | The shift (Roster) id. |
| start_time | – | yes | Shift start: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
No output schema declared.
No examples provided.
deputy_update_timesheet Update a timesheet ~171
Correct an existing timesheet's start/end time, area, meal break or supervisor comment. Times cannot be in the future. Deputy: POST /api/v1/supervise/timesheet/update.
| Name | Type | Req | Description |
|---|---|---|---|
| area_id | integer | yes | Area (OperationalUnit id) the time was worked in. |
| comment | string | – | Comment attached to the timesheet. |
| end_time | – | yes | Timesheet end: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
| mealbreak_minutes | integer | – | Total unscheduled meal break, minutes. |
| start_time | – | yes | Timesheet start: a unix timestamp in seconds, or an ISO 8601 datetime (include an offset for local times). |
| timesheet_id | integer | yes | The timesheet id. |
No output schema declared.
No examples provided.
deputy_whoami Who am I ~52
Return the Deputy user the token belongs to — name, employee id, company and permissions. A cheap way to confirm DEPUTY_INSTALL and the token are right. Deputy: GET /api/v1/me.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.usefulapi/deputy MCP server?
io.usefulapi/deputy is an MCP server listed in the public MCP registry as io.usefulapi/deputy. See rosters, timesheets, leave and staff in Deputy, and create shifts, leave and memos. This page covers its hosted endpoint (https://deputy.usefulapi.io/mcp).
Is the io.usefulapi/deputy MCP server safe to use?
io.usefulapi/deputy scores 77 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/deputy MCP server expose?
io.usefulapi/deputy exposes 21 tools: deputy_whoami, deputy_list_locations, deputy_list_areas, deputy_list_employees, deputy_get_employee, and 16 more. Their descriptions and schemas cost roughly 3,270 tokens of context every time the server is loaded.
Does the io.usefulapi/deputy MCP server require authentication?
Yes. io.usefulapi/deputy 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/deputy MCP server still maintained?
io.usefulapi/deputy is still listed as active in the MCP registry. We last reached this channel on 3 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.