A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
tilwhen date engine 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.
96/100
tool-list score
9
tools declared
remote
at its publisher
—
calls last 7d
What it does
Deterministic date arithmetic with auditable receipts: business days, due dates, holidays.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tilwhen-date-engine-mcp https://mcp.tilwhen.com/mcp
# 2 — ask your agent for something these tools do
# parse_date_query, add_days, subtract_days and 6 more
tilwhen date engine costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TIAll 1 server
tilwhen1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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.
Claude Codedeclared by this listing
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 tilwhen-date-engine-mcp https://mcp.tilwhen.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
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.
What you approve
9 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.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| q | string | yes | The date question in plain language. Pass the user's wording rather than a date you computed. |
| tz | string | no | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| locale | string | no | Resolves ambiguous slash dates; omit to receive clarification choices |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | yes | Whole calendar days to add. Negative counts backwards. |
| tz | string | no | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| date | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | yes | Whole calendar days to subtract. Negative counts forwards. |
| tz | string | no | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
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 dates use business_days; to move a date by N days use add_days or subtract_days.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | yes | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| to | string | yes | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| tz | string | no | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
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, not from. Optional holiday jurisdiction or custom calendar, and a selectable working week. For calenda
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| to | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| date | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | no | Add mode: business days to move. Negative counts backwards. |
| jurisdiction | string | no | Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). No default: omit for no holiday calendar. |
| customHolidays | array | no | Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction) |
| workweek | string | no | Working week. Default mon-fri (Sat+Sun weekend). |
| tz | string | no | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| invoiceDate | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| net | integer | yes | Net-N payment terms in calendar days (Net 30 = 30). |
| roll | boolean | no | Roll a weekend or holiday due date forward to the next business day. Default false. |
| jurisdiction | string | no | Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). No default: omit for no holiday calendar. |
| customHolidays | array | no | Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction) |
| workweek | string | no | Working week. Default mon-fri (Sat+Sun weekend). |
| tz | string | no | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event | string | no | Event slug (e.g. christmas). Exactly one of event/weekday. |
| weekday | integer | no | 0 = Sunday .. 6 = Saturday. Exactly one of event/weekday. |
| from | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| tz | string | no | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | yes | Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). |
| year | integer | yes | Calendar year to list, e.g. 2027 |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| op | string | yes | Operation to explain. holiday_lookup is the holidays tool; the others share their tool's name. |
| date | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | no | Day count for add_days, subtract_days and business_days add mode. |
| from | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| to | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| invoiceDate | string | no | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| net | integer | no | Net-N payment terms in calendar days (Net 30 = 30). |
| roll | boolean | no | Roll a weekend or holiday due date forward to the next business day. Default false. |
| event | string | no | Event slug (e.g. christmas). Exactly one of event/weekday. |
| weekday | integer | no | 0 = Sunday .. 6 = Saturday. Exactly one of event/weekday. |
| year | integer | no | Calendar year for holiday_lookup, e.g. 2027 |
| jurisdiction | string | no | Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB). No default: omit for no holiday calendar. |
| customHolidays | array | no | Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction) |
| workweek | string | no | Working week. Default mon-fri (Sat+Sun weekend). |
| tz | string | no | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
Free
$0 forever
- 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 tilwhen date engine or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.1 · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
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.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digest5d34db3bb6d2c04515959bf2e5e1ab82c3fa5c3a64415b5c2e46fb395ceb5573
Score vectorthreat 100 → client 96
| 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 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
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 |
|---|---|---|
| parse_date_query | no tags | |
| add_days | no tags | |
| subtract_days | no tags | |
| days_between | no tags | |
| business_days | no tags | |
| invoice_due | no tags | |
| next_occurrence | no tags | |
| holidays | no tags | |
| explain | 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
Integrityfirst-seen
Surface digest5d34db3bb6d2c045
Scanned2026-10-20
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.1.
1.0.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish tilwhen date engine can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.