io.github.everyai-com/service-schedule

Est-ce que io.github.everyai-com/service-schedule est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.github.everyai-com/service-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 4 outils

• due_services≈ 1276 tokens

  Work out which car maintenance services (oil, tires, brakes, filters, coolant, plugs, transmission, battery) are due, due soon or ok from the current odometer and optional service history, and name the next one. Use to check what a car needs now. Do NOT use for prices (use service_cost_estimate) or a 12-month plan (use service_timeline).

  Paramètres, retour & exemple (5)

  Paramètres

  • unit · string · optionnel · km | mi
    Unit of odometer and last_service odometer values: 'km' (default) or 'mi'
  • odometer · number · requis
    Current odometer reading, non-negative, in the unit given by unit, e.g. 48000
  • km_per_month · number · optionnel
    Average distance driven per month in km (always km, 100-10000); adds a 'next due in about N months' hint
  • last_service · array · optionnel
    Optional per-service history, one entry per service id; items without an entry assume last service at odometer 0
  • months_since_last_oil · number · optionnel
    Months since the last oil change; used as the time baseline for every item without its own history, default 0

  Exemple d'appel

  {"name": "due_services", "arguments": {"odometer": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "services": [], "odometer_km": 1, "next_service": {}, "odometer_input": {}}}

• seasonal_checklist≈ 398 tokens

  Generate a preventive car checklist for spring, summer, fall or winter, grouped by area (tires, battery, fluids, wipers and more) and tuned for a hot, cold or mixed climate. Use when getting a car ready for the season ahead. Do NOT use for mileage-based maintenance status (use due_services).

  Paramètres, retour & exemple (2)

  Paramètres

  • season · string · requis · spring | summer | fall | winter
    Season to prepare for
  • climate · string · optionnel · hot | cold | mixed
    Local climate: 'hot', 'cold' or 'mixed' (default)

  Exemple d'appel

  {"name": "seasonal_checklist", "arguments": {"season": "spring"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "season": "spring", "climate": "hot", "checklist": []}}

• service_cost_estimate≈ 562 tokens

  Estimate typical US parts-and-labor price ranges (USD) for a list of car maintenance services at an economy, mid or luxury shop, with low and high totals. Use when budgeting for known services. An estimate, not a quote. Do NOT use to find which services are due (use due_services).

  Paramètres, retour & exemple (2)

  Paramètres

  • tier · string · optionnel · economy | mid | luxury
    Shop tier: 'economy' (x0.85), 'mid' (default) or 'luxury' (x1.6)
  • services · array · requis
    Service ids to price (duplicates ignored), e.g. ["oil_change","brake_inspection"]

  Exemple d'appel

  {"name": "service_cost_estimate", "arguments": {"services": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "tier": "economy", "items": [], "total_low": 1, "total_high": 1, "source_note": "texte"}}

• service_timeline≈ 487 tokens

  Project the next 12 months of driving and list which maintenance services fall due in each month, from the odometer and monthly distance. Use when planning maintenance over the coming year. Do NOT use for what is due right now (use due_services) or prices (use service_cost_estimate).

  Paramètres, retour & exemple (4)

  Paramètres

  • unit · string · optionnel · km | mi
    Unit of the odometer value: 'km' (default) or 'mi'
  • odometer · number · requis
    Current odometer reading, non-negative, in the unit given by unit, e.g. 48000
  • km_per_month · number · requis
    Average distance driven per month in km (always km, 100-10000), e.g. 1200
  • months_since_last_oil · number · optionnel
    Months since the last oil change; time baseline for every service, default 0

  Exemple d'appel

  {"name": "service_timeline", "arguments": {"odometer": 1, "km_per_month": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"note": "texte", "months": []}}

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://service-schedule.magicteams.ai/mcp