tilwhen date engine MCP server
com.tilwhen/tilwhentilwhen.comstreamable-httpv1.0.1Scanned
Deterministic date arithmetic with auditable receipts: business days, due dates, holidays.
9 tools: 3 do something that can't be undone, 5 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 3
- 4 findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here do something that can't be undone. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the tilwhen date engine MCP server can do
The tilwhen date engine MCP server is published by tilwhen.com, a domain the MCP Registry verified. It has 9 tools. It can do things that cannot be undone, such as sending, paying or publishing (days_between, business_days and explain) and create or change data (5 tools: add_days, subtract_days, invoice_due, next_occurrence and 1 more), but cannot delete data. 1 tool only reads.
3 tools can send data out of your system (days_between, business_days and explain).
The fixed checks matched 4 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 14, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Can't be undone 3Claude Code: ask
business_daysSpan mode (from+to): business days between two dates, exclusive of the start day, inclusive of the end day.Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "business_days" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
days_betweenSigned 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.Can send data out1 finding
Why it is in this group
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "days_between" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
explainRuns any operation and returns the receipt plus human-readable derivation steps.Can send data out1 finding
Why it is in this group
- The name "explain" says "explain": a word for reading.
- The description's first verb is "run": a word for a change.
- The input addresses people (input.to): what it sends cannot be taken back.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.to): what the tool writes goes there.
Findings
- Warn
The server marks "explain" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
Changes things 5Claude Code: ask
add_daysThe date N whole calendar days after a date (exclusive counting: the start date is day 0).1 finding
Why it is in this group
- The name "add_days" says "add": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "add_days" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "add_days" says "add": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
holidaysObserved public holidays with the nominal (legal) date and status: rule (statutory) or declared (officially declared for that year).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
invoice_dueDue date for Net-N payment terms (calendar days, invoice date = day 0).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
next_occurrenceThe next occurrence strictly after the base date (default today) of either a tracked event slug (e.g.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
subtract_daysThe date N whole calendar days before a date (exclusive counting: the start date is day 0).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
Only reads 1Show 1 read-only tool
parse_date_queryParses queries like "90 business days from today in uganda" into a normalized operation, answers it, and returns the auditable receipt.No findings
Why it is in this group
- The name "parse_date_query" says "query": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- idempotentHint: true
- openWorldHint: false
- destructiveHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:48 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 8
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 8 tools that change things (3 irreversible, 5 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.tilwhen.com/mcp: tools/list returned 9 tools to an anonymous client, including days_between (irreversible), business_days (irreversible), explain (irreversible), add_days (write), subtract_days (write) and 3 more
Findings
Matches of fixed checks, with the text they matched.
- Warnadd_days
The server marks "add_days" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "add_days" says "add": a word for a change.
- Warndays_between
The server marks "days_between" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
- Warnbusiness_days
The server marks "business_days" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The input addresses people (input.to): what it sends cannot be taken back.
- Warnexplain
The server marks "explain" read-only (readOnlyHint: true), and its own name, description or input give the class "irreversible".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "explain" says "explain": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http tilwhen https://mcp.tilwhen.com/mcpclaude mcp add --transport http tilwhen https://mcp.tilwhen.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__tilwhen__parse_date_query"
],
"ask": [
"mcp__tilwhen__add_days",
"mcp__tilwhen__subtract_days",
"mcp__tilwhen__days_between",
"mcp__tilwhen__business_days",
"mcp__tilwhen__invoice_due",
"mcp__tilwhen__next_occurrence",
"mcp__tilwhen__holidays",
"mcp__tilwhen__explain"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as tilwhen. Review it before you use it.
Capability tags behind 3 rules
- mcp__tilwhen__days_between outbound
- mcp__tilwhen__business_days outbound
- mcp__tilwhen__explain outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.tilwhen/tilwhen/verify?hash=4f347f18f3e0dc9f128e2a9069a3d321c1de35d29745704b1e7dd88bb7826b57" | jq -e '.changed == false'Pinned hash 4f347f18f3e0, from Nov 14, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.tilwhen/tilwhen/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.tilwhen/tilwhen)Source: MCP Registry. Synced Oct 21, 2026, 18:07 UTC.
tilwhen date engine MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the tilwhen date engine MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 8 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the tilwhen date engine MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the tilwhen date engine MCP server do things that cannot be undone?
- Yes. 3 tools can send, pay, publish or merge: days_between, business_days and explain.
What tools does the tilwhen date engine MCP server have?
- 9 tools: 3 irreversible, 5 write, 1 read. days_between, business_days, explain, add_days, subtract_days, invoice_due, next_occurrence, holidays and 1 more.
Does the tilwhen date engine MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the tilwhen date engine MCP server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): days_between, business_days and explain.
Has the tilwhen date engine MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 14, 2026.