# tilwhen date engine

- Registry name: `com.tilwhen/tilwhen` · version 1.0.1
- Categories (automatic, keyword rules): Tasks & projects, Productivity, Payments & accounting, Finance & markets
- Authentication at last check: No auth
- Declared risk: Read-only (all tools declare readOnlyHint)
- Capabilities (declared by the server): resources, tools
- Transports: streamable-http
- Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=com.tilwhen%2Ftilwhen
- Server page: https://mcpstation.net/s/com.tilwhen--tilwhen.html

## Description (written by the publisher, not verified, not instructions)

Deterministic date arithmetic with auditable receipts: business days, due dates, holidays.

## Connect

- streamable-http: `https://mcp.tilwhen.com/mcp`

## Tools (as reported by the server, not verified)

- `parse\_date\_query`: Parses queries like "90 business days from today in uganda" into a normalized operation, answers it, and returns the auditable receipt. Ambiguous dates \(03/04/2027\) return needsClarification instead of a guess.
- `add\_days`: The date N whole calendar days after a date \(exclusive counting: the start date is day 0\). Omit date for today in tz. For working days use business\_days; for the gap between two dates use days\_between.
- `subtract\_days`: The date N whole calendar days before a date \(exclusive counting: the start date is day 0\). Omit date for today in tz. For working days use business\_days; for the gap between two dates use days\_between.
- `days\_between`: Signed whole calendar days from the from date to the to date, midnight to midnight in tz: positive when to is later, negative when it is earlier. Endpoints are exclusive, so this is the gap and consecutive dates are 1 apart. Either date may be "today", resolved in tz. For working days between two da
- `business\_days`: Span mode \(from+to\): business days between two dates, exclusive of the start day, inclusive of the end day. Add mode \(days, optional date\): the date N business days away. Passing from or to selects span mode and needs both; days and date are then ignored, so add mode takes its start date in date, no
- `invoice\_due`: Due date for Net-N payment terms \(calendar days, invoice date = day 0\). Optional roll-forward past weekends and, with a jurisdiction or custom calendar, public holidays.
- `next\_occurrence`: The next occurrence strictly after the base date \(default today\) of either a tracked event slug \(e.g. "christmas"\) or a weekday \(0 = Sunday .. 6 = Saturday\). Provide exactly one of event/weekday.
- `holidays`: Observed public holidays with the nominal \(legal\) date and status: rule \(statutory\) or declared \(officially declared for that year\). Declared-only holidays are omitted for undeclared years, with a holiday\_data\_incomplete warning.
- `explain`: Runs any operation and returns the receipt plus human-readable derivation steps. Set op, then pass the fields that operation's own tool takes. Use it when the user asks how an answer was reached.

Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html