Combien d'outils expose io.github.theluckystrike/leave-pto-requests-approvals ?

io.github.theluckystrike/leave-pto-requests-approvals expose 12 outil(s). Le coût de contexte pour les charger tous est d'environ 2155 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Dev & Code / io.github.theluckystrike/leave-pto-requests-approvals

io.github.theluckystrike/leave-pto-requests-approvals

serveur MCP (Model Context Protocol) · mcp-leave 0.22.0

▸ Dev & Code

[ Non encore testé ]

Verdict MCP Hub
Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur.

?Type / transport

?Accès

~2155 tokensCoût de contexte

12Outils

Est-ce que io.github.theluckystrike/leave-pto-requests-approvals est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.theluckystrike/leave-pto-requests-approvals » 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 12 outils

leave_approve≈ 163 tokens
Approve a pending leave request by id. Also used to re-open a rejected one. Nothing to approve on an already-approved request.
Paramètres, retour & exemple (2)
Paramètres
- comment · string · optionnel
  Approval note
- request · string · requis
  The request id (e.g. LV-0001).
Exemple d'appel
```
{"name": "leave_approve", "arguments": {"request": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
leave_balance≈ 154 tokens
Show one employee's leave balance: allowance + carried-over, minus approved and pending, as whole days plus a possible half day. Remaining is rounded down to whole days on the report.
Paramètres, retour & exemple (1)
Paramètres
- employee · string · requis
  Employee id or name
Exemple d'appel
```
{"name": "leave_balance", "arguments": {"employee": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
leave_cancel≈ 174 tokens
Cancel a pending or approved request by id, keeping its record with status cancelled. Differs from leave_reject in intent (voluntary withdrawal). Nothing happened if already cancelled.
Paramètres, retour & exemple (2)
Paramètres
- reason · string · optionnel
  Why
- request · string · requis
  The request id (e.g. LV-0001).
Exemple d'appel
```
{"name": "leave_cancel", "arguments": {"request": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
leave_employee_add≈ 270 tokens
Add an employee to the leave tracker and return their EMP-NNNN id. Give their annual paid-leave allowance in whole days and any days carried over from last year. Balances charge approved plus pending leave against allowance + carried-over. Free tier: unlimited.
Paramètres, retour & exemple (4)
Paramètres
- name · string · requis
  Full name, e.g. Taylor Wren
- email · string · optionnel
  Work email, for calendar lookup
- carriedOver · integer · optionnel
  Days carried over from last year (default 0)
- annualAllowance · integer · requis
  Annual paid leave allowance in whole days
Exemple d'appel
```
{"name": "leave_employee_add", "arguments": {"name": "texte", "annualAllowance": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
leave_export_ics≈ 142 tokens
Pro. Export all APPROVED leave as an .ics calendar (RFC5545). Returns the calendar text; pass path to also write it to a local file. watermark-free.
Paramètres, retour & exemple (1)
Paramètres
- path · string · optionnel
  Local .ics file to write
Exemple d'appel
```
{"name": "leave_export_ics", "arguments": {"path": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
leave_import≈ 206 tokens
Pro. Bulk-create leave requests from a CSV/TSV. First row is a header: employee,type,start,end,halfDay,status,reason. status may be omitted (defaults to pending) or be approved/rejected. Each request is still checked for overlap conflicts; a conflicting row is reported, not applied. watermark-free, full CRUD.
Paramètres, retour & exemple (1)
Paramètres
- csv · string · requis
  CSV text, newline-separated, first row header: employee,type,start,end,halfDay,status,reason
Exemple d'appel
```
{"name": "leave_import", "arguments": {"csv": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
leave_list≈ 171 tokens
List all employees, or all leave requests (optionally filtered by employee and/or status). Omit the filter to list requests.
Paramètres, retour & exemple (2)
Paramètres
- status · string · optionnel · pending | approved | rejected | cancelled
  Filter requests by status
- employee · string · optionnel
  Filter requests to one employee
Exemple d'appel
```
{"name": "leave_list", "arguments": {"status": "pending", "employee": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
leave_out_range≈ 188 tokens
Who is out in a date range: start and end are inclusive YYYY-MM-DD. Each employee appears once per day; pending requests count as a plan. Use for coverage, calendars and absence summaries. Free tier: unlimited.
Paramètres, retour & exemple (2)
Paramètres
- end · string · requis
  Last day, YYYY-MM-DD, inclusive
- start · string · requis
  First day, YYYY-MM-DD, inclusive
Exemple d'appel
```
{"name": "leave_out_range", "arguments": {"end": "texte", "start": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
leave_reject≈ 180 tokens
Reject or cancel a leave request by id. A pending or approved request becomes rejected; a rejected one can be reopened via leave_approve. Use leave_cancel (via reject with reason) for voluntary withdrawal.
Paramètres, retour & exemple (2)
Paramètres
- reason · string · optionnel
  Why
- request · string · requis
  The request id (e.g. LV-0001).
Exemple d'appel
```
{"name": "leave_reject", "arguments": {"request": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
leave_request≈ 327 tokens
Create a leave or PTO request and return its LV-NNNN id. type is vacation, sick, unpaid or parental. start and end are inclusive YYYY-MM-DD dates; halfDay charges half a day for the whole span. A pending request is refussed if it would overlap another approved or pending request of the same employee. Free tier: unlimited requests.
Paramètres, retour & exemple (6)
Paramètres
- end · string · requis
  Last day off, YYYY-MM-DD, inclusive
- type · string · requis · vacation | sick | unpaid | parental
  Kind of leave
- start · string · requis
  First day off, YYYY-MM-DD, inclusive
- reason · string · optionnel
  Why, shown in reports and calendar
- halfDay · boolean · optionnel
  Half-day charge for the whole span (default false)
- employee · string · requis
  The employee id or name
Exemple d'appel
```
{"name": "leave_request", "arguments": {"end": "texte", "type": "vacation", "start": "texte", "employee": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
license_activate≈ 167 tokens
Turn Pro on for this connection with key, an MCPL1.<payload>.<signature> issued at checkout for this server or the bundle. Data under your token stays; a wrong or expired key changes nothing. license_status confirms it.
Paramètres, retour & exemple (1)
Paramètres
- key · string · requis
  License key from checkout, MCPL1.<payload>.<signature>
Exemple d'appel
```
{"name": "license_activate", "arguments": {"key": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
license_status≈ 125 tokens
Report this endpoint's licence state for your token as JSON: the product, the tier free or pro, why it is not Pro, and the checkout URL. Call it to explain a free-tier refusal. No arguments, nothing changes.
Paramètres, retour & exemple (0)
Exemple d'appel
```
{"name": "license_status", "arguments": {}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```

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é ».

Créer un compte / revendiquer →

Source

https://mcp.zovo.one/mcp/leave-pto-requests-approvals