accueil / serveurs / Géo & Temps / io.github.theluckystrike/appointment
io.github.theluckystrike/appointment
serveur MCP (Model Context Protocol) · mcp-calendar 0.22.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.theluckystrike/appointment est sûr ?
Au dernier audit MCP Hub, le serveur MCP « io.github.theluckystrike/appointment » 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
- calendars_list≈ 127 tokens
List imported calendars: name, event-definition count, size, source, import time and free-tier use of the 2 slots. It also names stored .ics files with no calendar row. With none it prints the export steps.
Paramètres, retour & exemple (0)
Exemple d'appel{"name": "calendars_list", "arguments": {}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - conflicts≈ 214 tokens
Find double bookings: every PAIR of timed events that overlap, with the minutes they collide, across all calendars unless you name one. Whole-day events are reported apart. Free: 31 days. free_busy shows gaps.
Paramètres, retour & exemple (3)
Paramètresto· string · requis
Last day, YYYY-MM-DD, includedfrom· string · requis
First day, YYYY-MM-DDcalendar· string · optionnel
One calendar name; default every imported calendar
Exemple d'appel{"name": "conflicts", "arguments": {"to": "texte", "from": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - event_export≈ 289 tokens
Call this tool to write chosen events to a new .ics file you can send or import elsewhere. Pass either ids (from events_list) or a from/to window. Times are written in UTC so the file lands correctly in any client.
Paramètres, retour & exemple (5)
Paramètresto· string · optionnel
Last day, YYYY-MM-DD, includedids· array · optionnel
Event ids from events_list, events_search or next_eventfrom· string · optionnel
First day, YYYY-MM-DD (alternative to ids)calendar· string · optionnel
With from/to: limit to one calendarout_path· string · requis
Name for the downloaded .ics file, e.g. week.ics
Exemple d'appel{"name": "event_export", "arguments": {"out_path": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - event_to_time_entry≈ 305 tokens
Take one event and return the exact arguments for the time-tracker's entry_add, so a meeting that already happened becomes billable time without retyping it. Writes nothing: pass the JSON straight to entry_add.
Paramètres, retour & exemple (4)
Paramètresrate· ? · optionnel
Hourly rate for this entry; a number (120) or the words the user said ('120 euros an hour')project· string · requis
Project or client the meeting is billed tocurrency· string · optionnel
Currency of the rate: EUR, USD, GBP, PLN, or the word the user said ('euros'). Without it the time-tracker falls back to USD.event_id· string · requis
Event id from events_list, events_search or next_event
Exemple d'appel{"name": "event_to_time_entry", "arguments": {"project": "texte", "event_id": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - events_list≈ 247 tokens
Every event between two dates, recurring expanded to occurrences, sorted by start. Times shown in your zone (profile's, else this machine's) unless zone passed. Each id works for event_export or event_to_time_entry.
Paramètres, retour & exemple (4)
Paramètresto· string · requis
Last day, YYYY-MM-DD, includedfrom· string · requis
First day, YYYY-MM-DDzone· string · optionnel
Show local times in this zone or city instead of your owncalendar· string · optionnel
One calendar name; default every imported calendar
Exemple d'appel{"name": "events_list", "arguments": {"to": "texte", "from": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - events_search≈ 209 tokens
Find events whose title, description, location or attendees contain a phrase. Searches every imported calendar. Without from/to it looks a year back and a year forward on Pro, and the free window either side of today.
Paramètres, retour & exemple (3)
Paramètresto· string · optionnel
Last day, YYYY-MM-DD, includedfrom· string · optionnel
First day, YYYY-MM-DDquery· string · requis
Words to look for, case-insensitive
Exemple d'appel{"name": "events_search", "arguments": {"query": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - free_busy≈ 310 tokens
Merged busy blocks and the free gaps inside your working hours over a day range. Events marked free do not count; whole-day events block the day. Free: 31 days. Use conflicts for overlapping pairs.
Paramètres, retour & exemple (6)
Paramètresto· string · requis
Last day, YYYY-MM-DD, includedfrom· string · requis
First day, YYYY-MM-DDzone· string · optionnel
Zone the working hours and the output are in; default your ownwork_end· string · optionnel
End of your working day, HH:MM, default 17:00calendars· array · optionnel
Calendar names; default all of themwork_start· string · optionnel
Start of your working day, HH:MM, default 09:00
Exemple d'appel{"name": "free_busy", "arguments": {"to": "texte", "from": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - ics_forget≈ 159 tokens
Remove one imported calendar by name and delete this server's local copy of its .ics, freeing a slot. Your own calendar and the source file are untouched. ics_import replaces a name in place.
Paramètres, retour & exemple (1)
Paramètresname· string · requis
The calendar name from calendars_list
Exemple d'appel{"name": "ics_forget", "arguments": {"name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - ics_import≈ 274 tokens
Call this tool to read a calendar export and keep it under a name. Give path (.ics file), text (contents), or url (public .ics/webcal feed; Pro). Google, Apple, Outlook exports read. Re-importing a name replaces it.
Paramètres, retour & exemple (4)
Paramètresurl· string · optionnel
Public https:// or webcal:// .ics feed. Fetched once, only because you asked; Pro featurename· string · requis
What to call this calendar, e.g. "work" or "family"path· string · optionnel
Not available on this hosted endpoint, which has no filesystem: paste the file as text insteadtext· string · optionnel
The .ics file contents, pasted
Exemple d'appel{"name": "ics_import", "arguments": {"name": "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ètreskey· 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": "…"}]} - next_event≈ 158 tokens
The first event not yet started, within the next 366 days, across every imported calendar or one you name. Returns title, times in your zone, how long until it starts, location, attendees and its id.
Paramètres, retour & exemple (1)
Paramètrescalendar· string · optionnel
One calendar name; default every imported calendar
Exemple d'appel{"name": "next_event", "arguments": {"calendar": "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é ».