tilwhen date engine
REMOTE · MCP.TILWHEN.COM
Deterministic date arithmetic with auditable receipts: business days, due dates, holidays.
Available components
Last scanned (19 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Productivity and Notes
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2079 tokens (~173/item across 12 items; 9 tools + 3 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 Management97
- Stability observed for 29 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Tool “business_days” rewrote its description, which is the text the model reads security
- Tool “days_between” rewrote its description, which is the text the model reads security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 18 Sept 26 0
- Tool “add_days” rewrote its description, which is the text the model reads security
- Tool “explain” rewrote its description, which is the text the model reads security
- Tool “subtract_days” rewrote its description, which is the text the model reads security
- Schema quality: 136 → 164 ▼ functional
- Tool coverage: 65% → 100% ▲ functional
- Schema quality: good → excellent functional
- “add_days” reworded the description of “days” cosmetic
- “business_days” reworded the description of “days” cosmetic
- “days_between” reworded the description of “to” cosmetic
- “explain” reworded the description of “days” cosmetic
- “explain” reworded the description of “event” cosmetic
- “explain” reworded the description of “net” cosmetic
- “explain” reworded the description of “op” cosmetic
- “explain” reworded the description of “roll” cosmetic
- “explain” reworded the description of “weekday” cosmetic
- “explain” reworded the description of “year” cosmetic
- “holidays” reworded the description of “jurisdiction” cosmetic
- “holidays” reworded the description of “year” cosmetic
- “invoice_due” reworded the description of “net” cosmetic
- “invoice_due” reworded the description of “roll” cosmetic
- “next_occurrence” reworded the description of “event” cosmetic
- “next_occurrence” reworded the description of “weekday” cosmetic
- “parse_date_query” reworded the description of “q” cosmetic
- “subtract_days” reworded the description of “days” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 Nov 2026 · Probed https://mcp.tilwhen.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tilwhen.com | CN=WE1,O=Google Trust Services,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 330620e5fd7514300e1b31dea4cb77c0 |
| SANs: tilwhen.com, mcp.tilwhen.com, *.mcp.tilwhen.com | ||||||
| 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 mcp.tilwhen.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tilwhen.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.tilwhen.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.tilwhen.com/mcp | HTTPS enforced | 301 | https://mcp.tilwhen.com/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 →
add_days Add calendar days to a date ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | yes | Whole calendar days to add. Negative counts backwards. |
| tz | string | – | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | The calculated answer (kind-discriminated) |
| receipt | object | yes | Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID |
No examples provided.
business_days Business-day calculations ~300
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 calendar days use add_days, subtract_days or days_between.
| Name | Type | Req | Description |
|---|---|---|---|
| customHolidays | array | – | Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction) |
| date | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | – | Add mode: business days to move. Negative counts backwards. |
| from | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| jurisdiction | string | – | 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. |
| to | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| tz | string | – | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| workweek | string | – | Working week. Default mon-fri (Sat+Sun weekend). |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | The calculated answer (kind-discriminated) |
| receipt | object | yes | Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID |
No examples provided.
days_between Days between two dates ~160
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | The calculated answer (kind-discriminated) |
| receipt | object | yes | Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID |
No examples provided.
explain Explain a calculation step by step ~398
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customHolidays | array | – | Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction) |
| date | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | – | Day count for add_days, subtract_days and business_days add mode. |
| event | string | – | Event slug (e.g. christmas). Exactly one of event/weekday. |
| from | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| invoiceDate | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| jurisdiction | string | – | 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. |
| net | integer | – | Net-N payment terms in calendar days (Net 30 = 30). |
| op | string | yes | Operation to explain. holiday_lookup is the holidays tool; the others share their tool's name. |
| roll | boolean | – | Roll a weekend or holiday due date forward to the next business day. Default false. |
| to | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| tz | string | – | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| weekday | integer | – | 0 = Sunday .. 6 = Saturday. Exactly one of event/weekday. |
| workweek | string | – | Working week. Default mon-fri (Sat+Sun weekend). |
| year | integer | – | Calendar year for holiday_lookup, e.g. 2027 |
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | Auditable receipt for the operation |
| steps | array | yes | Human-readable derivation, identical to the REST /api/v1/explain output |
No examples provided.
holidays Public holidays for a jurisdiction and year ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | The calculated answer (kind-discriminated) |
| receipt | object | yes | Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID |
No examples provided.
invoice_due Invoice due date from net terms ~223
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customHolidays | array | – | Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction) |
| invoiceDate | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| jurisdiction | string | – | 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. |
| net | integer | yes | Net-N payment terms in calendar days (Net 30 = 30). |
| roll | boolean | – | Roll a weekend or holiday due date forward to the next business day. Default false. |
| tz | string | – | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| workweek | string | – | Working week. Default mon-fri (Sat+Sun weekend). |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | The calculated answer (kind-discriminated) |
| receipt | object | yes | Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID |
No examples provided.
next_occurrence Next occurrence of an event or weekday ~147
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event | string | – | Event slug (e.g. christmas). Exactly one of event/weekday. |
| from | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| tz | string | – | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| weekday | integer | – | 0 = Sunday .. 6 = Saturday. Exactly one of event/weekday. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | The calculated answer (kind-discriminated) |
| receipt | object | yes | Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID |
No examples provided.
parse_date_query Parse a natural-language date question ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Resolves ambiguous slash dates; omit to receive clarification choices |
| q | string | yes | The date question in plain language. Pass the user's wording rather than a date you computed. |
| tz | string | – | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | – | The calculated answer, absent when parsed is null |
| canonicalUrl | string|null | – | tilwhen page that answers this query, to cite; null when no page covers it |
| confidence | number | yes | 1.0 is a clean grammar hit; below 0.5 the query is refused rather than guessed |
| needsClarification | object | – | Present when the query is genuinely ambiguous (e.g. 03/04/2027); offers explicit choices instead of a guess |
| parsed | – | yes | Normalized operation, or null when the query could not be understood confidently |
| receipt | object | – | Auditable receipt, absent when parsed is null |
| warnings | array | yes | Machine-readable notes, e.g. unsupported_unit or time_ignored |
No examples provided.
subtract_days Subtract calendar days from a date ~117
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | ISO date YYYY-MM-DD, or "today" (resolved in tz) |
| days | integer | yes | Whole calendar days to subtract. Negative counts forwards. |
| tz | string | – | IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC. |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | object | yes | The calculated answer (kind-discriminated) |
| receipt | object | yes | Auditable receipt: inputs, timezone, convention, workweek, holiday calendar, exclusions, versions, stable result ID |
No examples provided.
How do I install the tilwhen date engine MCP server?
tilwhen date engine is a hosted endpoint at https://mcp.tilwhen.com/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 · mcp.tilwhen.com
claude mcp add --transport http com-tilwhen-tilwhen 'https://mcp.tilwhen.com/mcp'
What is the tilwhen date engine MCP server?
tilwhen date engine is an MCP server listed in the public MCP registry as com.tilwhen/tilwhen. Deterministic date arithmetic with auditable receipts: business days, due dates, holidays. This page covers its hosted endpoint (https://mcp.tilwhen.com/mcp).
Is the tilwhen date engine MCP server safe to use?
tilwhen date engine scores 88 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 tilwhen date engine MCP server expose?
tilwhen date engine exposes 9 tools: parse_date_query, add_days, subtract_days, days_between, business_days, and 4 more. Their descriptions and schemas cost roughly 1,698 tokens of context every time the server is loaded.
Does the tilwhen date engine MCP server require authentication?
No. We connected to tilwhen date engine without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the tilwhen date engine MCP server still maintained?
tilwhen date engine is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.