io.github.theluckystrike/maintenance-schedule

Est-ce que io.github.theluckystrike/maintenance-schedule est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.theluckystrike/maintenance-schedule » 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 8 outils

• asset_add≈ 330 tokens

  Add one piece of equipment to the maintenance register: its name, its serial or asset tag, where it lives, and the currency its costs are in. Returns the AST-YYYY-NNNN id. Free tier: 3 assets; logging work on the assets you have is never metered.

  Paramètres, retour & exemple (5)

  Paramètres

  • tag · string · optionnel
    The serial number or asset tag, e.g. SN-88-4412. Unique across the register: a second asset with the same tag is refused
  • name · string · requis
    What the asset is called, e.g. Lathe, Combi boiler, Van 2, or Studio camera A
  • notes · string · optionnel
    Anything worth keeping with the asset, e.g. Model, warranty end, supplier
  • currency · string · optionnel
    ISO code the costs are in. Default USD
  • location · string · optionnel
    Where the asset lives, e.g. Workshop bay 2, or 14 Nowa Street, flat 3

  Exemple d'appel

  {"name": "asset_add", "arguments": {"name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• asset_history≈ 190 tokens

  Read one asset in full by id, tag or name: every log entry in chronological order, the total spend as integer cents with a formatted amount, the last service date, and the next-due date the asset currently lives under. Reads only.

  Paramètres, retour & exemple (1)

  Paramètres

  • asset · string · requis
    The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it

  Exemple d'appel

  {"name": "asset_history", "arguments": {"asset": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• asset_remove≈ 227 tokens

  Remove an asset entered by mistake or sold off. One that carries a maintenance log is refused unless confirm is true, naming what would be lost, because removing it loses the record of work done. The AST number is never reissued.

  Paramètres, retour & exemple (2)

  Paramètres

  • asset · string · requis
    The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it
  • confirm · boolean · optionnel
    Pass true to remove an asset that carries a maintenance log. The log goes with it; this cannot be undone

  Exemple d'appel

  {"name": "asset_remove", "arguments": {"asset": "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": "…"}]}

• maintenance_due≈ 187 tokens

  The due report across every asset: what is overdue and by how many days, what falls due within the next N days (default 30), what is scheduled later, and what has no schedule at all. Computed from the stored next-due dates against today, at call time. Pro feature.

  Paramètres, retour & exemple (1)

  Paramètres

  • within_days · integer · optionnel
    How far ahead to look, in days. Default 30

  Exemple d'appel

  {"name": "maintenance_due", "arguments": {"within_days": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• maintenance_export≈ 250 tokens

  Export maintenance entries dated inside a range. CSV (free): one row per entry, ready for a spreadsheet. Markdown (Pro): one section per asset with its entries, total spend and next due date, ready to paste into notes or a report. Writes nothing.

  Paramètres, retour & exemple (3)

  Paramètres

  • to · string · optionnel
    Only entries dated on or before this, YYYY-MM-DD. Default: no upper bound
  • from · string · optionnel
    Only entries dated on or after this, YYYY-MM-DD. Default: no lower bound
  • format · string · optionnel · csv | markdown
    csv (default) or markdown. Markdown summaries are a Pro feature

  Exemple d'appel

  {"name": "maintenance_export", "arguments": {"to": "texte", "from": "texte", "format": "csv"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• maintenance_log≈ 434 tokens

  Log work done on an asset: the day, what was done, the cost in whole cents, who did it, and when the next service falls due -- as a date (next_due) or as an interval in days (interval_days), never both. A repair that sets no schedule takes neither. A future work date is refused.

  Paramètres, retour & exemple (7)

  Paramètres

  • date · string · requis
    The day the work was done, YYYY-MM-DD. A future date is refused
  • work · string · requis
    What was done, e.g. Oil and filter change, or Annual boiler service
  • asset · string · requis
    The asset id, e.g. AST-2026-0003, its serial or asset tag, or its name when only one asset has it
  • next_due · string · optionnel
    The date the next service falls due, YYYY-MM-DD. Pass either this or interval_days, not both
  • cost_cents · integer · optionnel
    What the work cost in whole cents. 12000 is 120.00. Default 0, for in-house work
  • technician · string · optionnel
    Who did the work, e.g. Anna, or Acme Heating Ltd
  • interval_days · integer · optionnel
    Days after the work date the next service falls due, e.g. 90 for quarterly. Turned into a date once, at log time

  Exemple d'appel

  {"name": "maintenance_log", "arguments": {"date": "texte", "work": "texte", "asset": "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/maintenance-schedule