accueil / serveurs / Finance & Paiement / com.tilwhen/tilwhen
com.tilwhen/tilwhen
serveur MCP (Model Context Protocol) · tilwhen 1.0.0
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.
Est-ce que com.tilwhen/tilwhen est sûr ?
Au dernier audit MCP Hub, le serveur MCP « com.tilwhen/tilwhen » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.
Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.
Les 9 outils
- add_days≈ 382 tokens
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.
Paramètres, retour & exemple (3)
Paramètrestz· string · optionnel
IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC.date· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)days· integer · requis
Whole calendar days to add. Negative counts backwards.
Exemple d'appel{"name": "add_days", "arguments": {"days": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"answer": {}, "receipt": {}}} - business_days≈ 640 tokens
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.
Paramètres, retour & exemple (8)
Paramètresto· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)tz· string · optionnel
IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC.date· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)days· integer · optionnel
Add mode: business days to move. Negative counts backwards.from· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)workweek· string · optionnel · mon-fri | sun-thu | mon-sat
Working week. Default mon-fri (Sat+Sun weekend).jurisdiction· string · optionnel
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 · optionnel
Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction)
Exemple d'appel{"name": "business_days", "arguments": {"to": "texte", "tz": "texte", "date": "texte", "days": 1, "from": "texte", "workweek": "mon-fri"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"answer": {}, "receipt": {}}} - days_between≈ 423 tokens
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.
Paramètres, retour & exemple (3)
Paramètresto· string · requis
ISO date YYYY-MM-DD, or "today" (resolved in tz)tz· string · optionnel
IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC.from· string · requis
ISO date YYYY-MM-DD, or "today" (resolved in tz)
Exemple d'appel{"name": "days_between", "arguments": {"to": "texte", "from": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"answer": {}, "receipt": {}}} - explain≈ 830 tokens
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.
Paramètres, retour & exemple (15)
Paramètresop· string · requis · add_days | subtract_days | days_between | business_days | invoice_due | next_occurrence | holiday_lookup
Operation to explain. holiday_lookup is the holidays tool; the others share their tool's name.to· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)tz· string · optionnel
IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC.net· integer · optionnel
Net-N payment terms in calendar days (Net 30 = 30).date· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)days· integer · optionnel
Day count for add_days, subtract_days and business_days add mode.from· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)roll· boolean · optionnel
Roll a weekend or holiday due date forward to the next business day. Default false.year· integer · optionnel
Calendar year for holiday_lookup, e.g. 2027event· string · optionnel
Event slug (e.g. christmas). Exactly one of event/weekday.weekday· integer · optionnel
0 = Sunday .. 6 = Saturday. Exactly one of event/weekday.workweek· string · optionnel · mon-fri | sun-thu | mon-sat
Working week. Default mon-fri (Sat+Sun weekend).invoiceDate· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)jurisdiction· string · optionnel
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 · optionnel
Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction)
Exemple d'appel{"name": "explain", "arguments": {"op": "add_days"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"steps": [], "receipt": {}}} - holidays≈ 352 tokens
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.
Paramètres, retour & exemple (2)
Paramètresyear· integer · requis
Calendar year to list, e.g. 2027jurisdiction· string · requis
Holiday jurisdiction id: US, GB, GB-SCT, GB-NIR, IE, FR, CA, AU, UG (alias UK for GB).
Exemple d'appel{"name": "holidays", "arguments": {"year": 1, "jurisdiction": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"answer": {}, "receipt": {}}} - invoice_due≈ 541 tokens
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.
Paramètres, retour & exemple (7)
Paramètrestz· string · optionnel
IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC.net· integer · requis
Net-N payment terms in calendar days (Net 30 = 30).roll· boolean · optionnel
Roll a weekend or holiday due date forward to the next business day. Default false.workweek· string · optionnel · mon-fri | sun-thu | mon-sat
Working week. Default mon-fri (Sat+Sun weekend).invoiceDate· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)jurisdiction· string · optionnel
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 · optionnel
Custom organizational holiday calendar as ISO dates (mutually exclusive with jurisdiction)
Exemple d'appel{"name": "invoice_due", "arguments": {"net": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"answer": {}, "receipt": {}}} - next_occurrence≈ 405 tokens
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.
Paramètres, retour & exemple (4)
Paramètrestz· string · optionnel
IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC.from· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)event· string · optionnel
Event slug (e.g. christmas). Exactly one of event/weekday.weekday· integer · optionnel
0 = Sunday .. 6 = Saturday. Exactly one of event/weekday.
Exemple d'appel{"name": "next_occurrence", "arguments": {"tz": "texte", "from": "texte", "event": "texte", "weekday": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"answer": {}, "receipt": {}}} - parse_date_query≈ 588 tokens
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.
Paramètres, retour & exemple (3)
Paramètresq· string · requis
The date question in plain language. Pass the user's wording rather than a date you computed.tz· string · optionnel
IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC.locale· string · optionnel · mdy | dmy
Resolves ambiguous slash dates; omit to receive clarification choices
Exemple d'appel{"name": "parse_date_query", "arguments": {"q": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"answer": {}, "parsed": "texte", "receipt": {}, "warnings": [], "confidence": 1, "canonicalUrl": "texte", "needsClarification": {}}} - subtract_days≈ 387 tokens
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.
Paramètres, retour & exemple (3)
Paramètrestz· string · optionnel
IANA timezone that defines "today" (e.g. Africa/Kampala). Default UTC.date· string · optionnel
ISO date YYYY-MM-DD, or "today" (resolved in tz)days· integer · requis
Whole calendar days to subtract. Negative counts forwards.
Exemple d'appel{"name": "subtract_days", "arguments": {"days": 1}}Exemple de retour{"content": [{"type": "text", "text": "…"}], "structuredContent": {"answer": {}, "receipt": {}}}
C'est votre serveur ?
Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».