Combien d'outils expose io.github.theluckystrike/new-hire-onboarding-tasks ?

io.github.theluckystrike/new-hire-onboarding-tasks expose 9 outil(s). Le coût de contexte pour les charger tous est d'environ 1904 tokens (coût unique au chargement, pas par appel).

accueil / serveurs / Productivité / io.github.theluckystrike/new-hire-onboarding-tasks

io.github.theluckystrike/new-hire-onboarding-tasks

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

▸ Productivité

[ 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

~1904 tokensCoût de contexte

9Outils

Est-ce que io.github.theluckystrike/new-hire-onboarding-tasks est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.theluckystrike/new-hire-onboarding-tasks » 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

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": "…"}]}
```
onboarding_hire_add≈ 239 tokens
Add a new hire and return its H-NNNN id: a name, a role and the day they start. The role is a grouping key, lower-cased and hyphenated. Add tasks with onboarding_task_add, or apply a role template with onboarding_template_apply.
Paramètres, retour & exemple (3)
Paramètres
- name · string · requis
  The hire's name, e.g. Ada Lovelace
- role · string · requis
  The role, e.g. engineer or sales. Lower-cased and hyphenated
- start_date · string · requis
  The day they start, YYYY-MM-DD. Task due dates are counted from here
Exemple d'appel
```
{"name": "onboarding_hire_add", "arguments": {"name": "texte", "role": "texte", "start_date": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
onboarding_hire_list≈ 197 tokens
Every hire with their role, start date, task counts, percent complete and overdue count. Filter by role or by a word in the name. Returns at most 500 rows, newest change first.
Paramètres, retour & exemple (2)
Paramètres
- role · string · optionnel
  Only hires in this role, matched after the same lower-case hyphenation applied on add
- contains · string · optionnel
  Only hires whose name contains this text, matched case-insensitively
Exemple d'appel
```
{"name": "onboarding_hire_list", "arguments": {"role": "texte", "contains": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
onboarding_overdue≈ 150 tokens
Every task that is still outstanding past its due date, across all hires or one hire, with how many days late. Returns at most 500 rows, most overdue first.
Paramètres, retour & exemple (1)
Paramètres
- hire · string · optionnel
  Only this hire's overdue tasks. Omit for every hire
Exemple d'appel
```
{"name": "onboarding_overdue", "arguments": {"hire": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
onboarding_progress≈ 195 tokens
One hire's whole plan: every task with its owner, due date and status, plus the percent complete, the overdue count and what is still outstanding. Pass as_csv for a Pro-only CSV export of the plan.
Paramètres, retour & exemple (2)
Paramètres
- hire · string · requis
  The hire id, e.g. H-0001, or the name when only one carries it
- as_csv · boolean · optionnel
  Return the plan as CSV. Pro only. Default false
Exemple d'appel
```
{"name": "onboarding_progress", "arguments": {"hire": "texte"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
onboarding_task_add≈ 282 tokens
Add one task to a hire's plan and return its K01-style id: the text, who owns it (hr, manager or it) and how many days after the start date it is due. The due date is counted from the hire's start date.
Paramètres, retour & exemple (4)
Paramètres
- hire · string · requis
  The hire id, e.g. H-0001, or the name when only one carries it
- text · string · requis
  The task, as the person doing it will read it, e.g. Issue laptop and security badge
- owner · string · requis · hr | manager | it
  Who owns the task: hr, manager or it
- due_offset · integer · requis
  Days after the hire's start date the task is due. 0 is day one
Exemple d'appel
```
{"name": "onboarding_task_add", "arguments": {"hire": "texte", "text": "texte", "owner": "hr", "due_offset": 1}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
onboarding_task_done≈ 273 tokens
Mark one task on a hire done or skipped, with the day it happened. done counts toward the percent complete; skipped is a deliberate dismissal and never counts as done. A task can be set back to todo to reopen it.
Paramètres, retour & exemple (4)
Paramètres
- date · string · optionnel
  The day it was completed, YYYY-MM-DD. Default today
- hire · string · requis
  The hire id, e.g. H-0001, or the name when only one carries it
- task · string · requis
  The task id, e.g. K03, as shown by onboarding_progress
- status · string · requis · todo | done | skipped
  done, skipped, or todo to put it back to outstanding
Exemple d'appel
```
{"name": "onboarding_task_done", "arguments": {"hire": "texte", "task": "texte", "status": "todo"}}
```
Exemple de retour
```
{"content": [{"type": "text", "text": "…"}]}
```
onboarding_template_apply≈ 372 tokens
Apply a role template to one hire (free) or many (Pro), copying the template's tasks into each hire with the template's version recorded. Editing the template afterwards never changes a hire already under way. If no template exists for the role, one is created from the tasks you pass.
Paramètres, retour & exemple (3)
Paramètres
- hire · string · requis
  The hire to apply the template to. Pro: pass a comma-separated list of hire ids or names to apply to many at once
- role · string · optionnel
  The role template to apply, by id (T-0001) or role. If omitted, the hire's own role is used
- tasks · array · optionnel
  When no template exists for the role, create one from these tasks and apply it. Pro only when applying to more than one hire
Exemple d'appel
```
{"name": "onboarding_template_apply", "arguments": {"hire": "texte"}}
```
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/new-hire-onboarding-tasks