accueil / serveurs / Dev & Code / io.github.wilbek-source/timetable-builder
io.github.wilbek-source/timetable-builder
serveur MCP (Model Context Protocol) · school-timetable-builder 0.1.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 io.github.wilbek-source/timetable-builder est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.wilbek-source/timetable-builder » 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 5 outils
- create_schedule≈ 593 tokens
Starts calculating the full timetable from the 8 input files (validate them first). Returns a job_id at once; the calculation takes about 5-8 minutes. Then keep calling get_schedule_result with the job_id in the same reply until it is done.
Paramètres, retour & exemple (3)
Paramètresfiles· object · requis
The 8 input files, exactly as described in the interview guide's 'submission' and 'topics'. JSON files are sent as JSON text inside the string; empty CSV files contain only the header line.user_country· string · optionnel
Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this.user_language· string · optionnel
Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user.
Exemple d'appel{"name": "create_schedule", "arguments": {"files": {}}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_interview_guide≈ 100 tokens
Returns the interview guide: which questions to ask the user, default values, engine limits and the exact format of the 8 input files. Call this first.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "get_interview_guide", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_schedule_result≈ 288 tokens
Gets the status or result of a job from create_schedule (or a slow validate_input). While running: progress. When done: a compact timetable as text plus a link (valid 1 hour) to the full JSON result. view='classes' (default) = one table per class, 'teachers' = one per teacher incl. preparation time, 'summary' = key figures and lists of classes/teachers only. Use 'names' to get only some classes/teachers (recommended for big schools). If impossible: the reasons.
Paramètres, retour & exemple (3)
Paramètresview· string · optionnel · classes | teachers | summary
What to show when done (default 'classes')names· array · optionnel
Only these classes (e.g. '1.A') or teacher codes (e.g. 'T01')job_id· string · requis
job_id from create_schedule or validate_input
Exemple d'appel{"name": "get_schedule_result", "arguments": {"job_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - send_feedback≈ 418 tokens
Passes the user's feedback about the timetable service on to its developer (what worked, what did not, wishes). Only call it when the user has said they want to give feedback, and send what the user said in their own words (you may shorten it; any language is fine). Never include teacher names, other personal data or the school's data files. Tell the user briefly that it was sent. Nobody replies through this channel - if the user wants an answer, give them the support email timetablingengine.support@gmail.com.
Paramètres, retour & exemple (5)
Paramètresjob_id· string · optionnel
job_id of the timetable the feedback is about, if anymessage· string · requis
The user's feedback, without names or other personal datasentiment· string · optionnel · positive | negative | mixed
Overall tone of the feedback, if clearuser_country· string · optionnel
Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this.user_language· string · optionnel
Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user.
Exemple d'appel{"name": "send_feedback", "arguments": {"message": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - validate_input≈ 596 tokens
Checks the 8 input files in a few seconds without creating a timetable: file structure, engine limits and a capacity analysis (enough teachers/time?). Returns VALID (with warnings) or INVALID (with reasons). Always run this before create_schedule.
Paramètres, retour & exemple (3)
Paramètresfiles· object · requis
The 8 input files, exactly as described in the interview guide's 'submission' and 'topics'. JSON files are sent as JSON text inside the string; empty CSV files contain only the header line.user_country· string · optionnel
Optional, for anonymous usage statistics: the school's country (e.g. 'Denmark') if the user has mentioned it. Never ask the user just for this.user_language· string · optionnel
Optional, for anonymous usage statistics: the language you talk to the user in (e.g. 'da', 'en'). Fill it in if you know it; never ask the user.
Exemple d'appel{"name": "validate_input", "arguments": {"files": {}}}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é ».