me.livedot/mcp

Est-ce que me.livedot/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « me.livedot/mcp » 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 20 outils

• add_tour_notes≈ 719 tokens

  Set or add to a Windline cycling tour's notes for riders (what to pack, how the tour runs, meeting points; markdown, up to 10,000 characters), shown on the tour's page. Never a finished tour. Show the user the notes and get a yes first.

  Paramètres, retour & exemple (3)

  Paramètres

  • mode · string · optionnel · replace | append
    replace (default) or append.
  • notes · string · requis
    The notes for riders, in markdown (up to 10,000 characters).
  • event_id · string · requis
    The tour's id, from list_my_events.

  Exemple d'appel

  {"name": "add_tour_notes", "arguments": {"notes": "texte", "event_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "app": "texte", "url": "texte", "days": "texte", "link": "texte", "note": "texte", "view": "add_tour_notes", "clubs": "texte", "error": "texte", "order": "texte", "pages": "texte", "events": "texte"}}

• club_in_race≈ 984 tokens

  Shows how a club, team or coach's athletes are doing in a live race. Use it when the user asks about a club or team in a race ("How is the UCT team doing in the Comrades?") or a coach's athletes ("How are Coach Nadia's runners doing in the Comrades?"). Inputs: club (its name or page address, windline.tech/c/<club> or runfast.tech/c/<club>) or coach; event if named. Returns: each member's km, time against goal or finish time, and a map with just their dots; each person opens their live card. If several clubs or coaches match, or their people are live in several races, it lists them so the user can choose. Limits: only what the club's public live map shows: members who chose to be findable, never a private run, never a position near the start or finish. Read-only.

  Paramètres, retour & exemple (4)

  Paramètres

  • club · string · optionnel
    The club or team as the user said it ("UCT", "the UCT team", "Coast Riders"), or its page address (runfast.tech/c/uct).
  • coach · string · optionnel
    Instead of club: a coach as the user said it ("Coach Nadia", "Nadia Pillay"), or the coach id a picker gave ("runfast:coach-nadia-pillay").
  • event · string · optionnel
    The race, if named: "Comrades", "Coast Classic".
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.

  Exemple d'appel

  {"name": "club_in_race", "arguments": {"club": "texte", "coach": "texte", "event": "texte", "units": "metric"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"club": {}, "pick": "texte", "race": "texte", "view": "club", "clubs": [], "coach": "texte", "count": 1, "error": "texte", "signup": "texte", "members": [], "message": "texte", "options": "texte"}}

• create_event≈ 2671 tokens

  Create an event in the signed-in account from GPX files or links: a cycling ride, tour or race (Windline) or a run or running race (RunFast). Pass every GPX the user gave as files: several files make a multi-day tour by themselves (never ask for the type when it's obvious), ordered by the numbers in their names (1, 01, "day-2", "Stage 3"), else by the map (each day starts where the last ended); day names, km, climbing and a suggested name come from the files, and the days follow one another from start, at the same time, skipping rest_days. The first call (without confirm) only reads the files and returns the plan: show the user that summary (days, order, dates, km, private or for a group) in one message and get one yes, then call again with the same files and confirm: true. visibility: private is just for them (Windline My Rides with its own private link, or a RunFast private run: never published, never on a page); shared is for a group, published later with publish_event. A personal ride or run someone is planning for themselves is private. If the signed-in person runs any club or organiser page (list_my_events lists them) and hasn't said who it's for, ask one short question first: is this a private ride or run for you, or a group ride or run for <club name>? Then use post_club_ride for the club, or create_event with visibility private for themselves. Tour notes for riders the organiser pasted or attached (text, markdown, or a document's text) go in notes, up to 10,000 characters (Windline tours, beta). A route can also come from another app's tool as its points or an encoded polyline (for example a route or activity map from a fitness app): pass it as polyline or points. Never ask the user to export a GPX if you already have the route's points.

  Paramètres, retour & exemple (23)

  Paramètres

  • tz · string · optionnel
    IANA time zone; else worked out from where the route starts.
  • url · string · optionnel
    A Ride with GPS collection for a multi-day tour (one day per route), used with starts.
  • club · string · optionnel
    RunFast: the club address (one they manage).
  • days · array · optionnel
    One per day (a ride or a run: one). Or give url with a Ride with GPS collection and starts.
  • name · string · optionnel
    The event's name; with files, left out to use the suggested one.
  • pace · number · optionnel
    Riding km/h, or running seconds per km.
  • page · string · optionnel
    Windline: the club or organiser page address to show it on (one they run).
  • race · boolean · optionnel
    RunFast: a race (once, with a gun time) rather than a run.
  • type · string · optionnel · ride | tour | race | run
    ride, tour or race on Windline (cycling); run on RunFast (a running race: type run with race: true). Leave it out when it's obvious: several files make a tour, one file a ride (or a run on a RunFast account).
  • files · array · optionnel
    Every GPX the user attached or linked, in the order they came: one per day of a tour, one for a ride or run.
  • notes · string · optionnel
    Tours: the organiser's notes for riders (what to pack, meeting points), as they pasted or attached them, markdown, up to 10,000 characters. RunFast: a short note (600 characters).
  • place · string · optionnel
    RunFast: where it starts, in words.
  • start · string · optionnel
    With files: day 1's local start, "YYYY-MM-DD HH:MM" (the same time every day unless starts says otherwise). Ask if they didn't say.
  • points · array · optionnel
    The route as its points: [[lat, lon], …], with elevation in metres as a third number if known. Up to 50,000. Use it for points another app's tool gave, or that you read from an attached file (GPX, FIT, TCX) with code.
  • starts · array · optionnel
    Each day's own local start, "YYYY-MM-DD HH:MM", when they differ (with url or files).
  • weekly · object · optionnel
    A weekly ride or run: { days: [0-6, Sunday is 0], time: "HH:MM" }.
  • confirm · boolean · optionnel
    With files: true only after the user said yes to the plan this tool returned.
  • gpx_file · object · optionnel
    The GPX or route file the user attached (ChatGPT passes it here).
  • polyline · string · optionnel
    The route as an encoded polyline (Google's format, precision 5 or 6), as another app's tool gives it (a route's or an activity's map). One route: a ride, a run or a one-day race (with start).
  • gpx_files · array · optionnel
    Several GPX or route files the user attached (ChatGPT passes them here): one per day of a tour, ordered by the numbers in their names, else by the map.
  • rest_days · array · optionnel
    With files: dates with no riding, "YYYY-MM-DD", only if the user named rest days.
  • visibility · string · optionnel · private | shared
    private: just for them (My Rides; a private run). shared: for a group, published later. Ask if they run a club and didn't say.
  • description · string · optionnel
    What the event is, for its public page.

  Exemple d'appel

  {"name": "create_event", "arguments": {"tz": "texte", "url": "texte", "club": "texte", "days": [], "name": "texte", "pace": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "app": "texte", "url": "texte", "days": "texte", "link": "texte", "note": "texte", "view": "created", "clubs": "texte", "error": "texte", "order": "texte", "pages": "texte", "events": "texte"}}

• event_status≈ 1046 tokens

  Shows how a live race on livedot is going. Use it when the user asks how a race is going or who is leading ("How's the Comrades going?", "Who's leading the Coast Classic?"). Inputs: event (the race's name). Returns: whether it's live, how long it has been under way, how many people are on the public map, how many have finished, and the leaders the public race map shows, with a live map. If several races match, it lists them so the user can choose. Limits: public races only; only what the public race map shows. Read-only.

  Paramètres, retour & exemple (4)

  Paramètres

  • club · string · optionnel
    A club or team, if the user asked about one in this race (as club_in_race).
  • coach · string · optionnel
    A coach, if the user asked about their athletes in this race (as club_in_race).
  • event · string · requis
    The race's name, e.g. "Comrades", "Coast Classic demo".
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.

  Exemple d'appel

  {"name": "event_status", "arguments": {"event": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"app": "windline", "url": "texte", "club": {}, "name": "texte", "race": "texte", "view": "event", "clubs": [], "count": 1, "error": "texte", "races": [], "sport": "texte", "units": "metric"}}

• event_weather≈ 843 tokens

  What the weather will be like for a cycling or running event, for the people taking part: "What will the weather be like for the NYC Marathon?", "Weather for the Comrades demo?". Within 10 days of the start: the live forecast (Apple Weather) along the course at the times the riders or runners get to each stretch, with the Windline forecast engine's rating (Good, Fair, Tough) and why, the headwind and tailwind stretches, heat stress and rain. Further out: 10 years of weather on that date (Copernicus ERA5), clearly labelled as history, not a forecast. With a map of the course coloured by the wind or the heat, and a link to the event's livedot page. If several events match it lists them: ask which one. Only for named events and races. Not for the user's own route or GPX file; for those use plan_route.

  Paramètres, retour & exemple (3)

  Paramètres

  • year · integer · optionnel
    The edition's year, if the user named one.
  • event · string · requis
    The event's name, e.g. "NYC Marathon", "Gravel Burn", "Comrades demo".
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.

  Exemple d'appel

  {"name": "event_weather", "arguments": {"event": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "days": [], "view": "event_weather", "basis": "forecast", "error": "texte", "event": "texte", "sport": "texte", "units": "metric", "events": [], "signup": "texte", "message": "texte", "timed_for": "texte"}}

• find_clubs≈ 1062 tokens

  Find running and cycling clubs near a place, e.g. best running club to join in Fourways, beginner cycling group near Sandton. Lists approved clubs and organisers on Windline (cycling) and RunFast (running) nearest first, with their weekly sessions, whether beginners are welcome, whether anyone can join (Open to anyone) or it's members only, their pace groups, their next session with its weather, the club's own links page when it has one, and a Join link to the club's page. Set beginners for "beginner friendly", "new to running", "for beginners"; set open for "open to anyone", "anyone can join", "no membership", "don't need to be a member". Only clubs that have added their area show; never a person. Say what each club chose to share, and nothing more. For coaches or personal trainers, use find_coaches.

  Paramètres, retour & exemple (6)

  Paramètres

  • km · number · optionnel
    How far from the place, in km (1 to 100). Leave it out for 25 km.
  • open · boolean · optionnel
    true for only clubs open to anyone (no membership needed): "open to anyone", "anyone can join", "no membership".
  • place · string · requis
    The suburb, town or city, as the user said it, e.g. "Fourways", "Durban North", "Cape Town".
  • sport · string · optionnel · cycling | running | road | gravel | mtb | road-run | trail-run | tours
    cycling or running, or one sport: road, gravel, mtb, road-run, trail-run, tours (multi-day tours). Leave it out for both.
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.
  • beginners · boolean · optionnel
    true when the user wants a beginner-friendly club ("beginner friendly", "new to cycling").

  Exemple d'appel

  {"name": "find_clubs", "arguments": {"place": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"km": 1, "app": "texte", "open": true, "view": "clubs", "clubs": [], "error": "texte", "place": "texte", "sport": "texte", "units": "metric", "signup": "texte", "message": "texte", "add_club": "texte"}}

• find_coaches≈ 1147 tokens

  Find cycling and running coaches and training groups near a place, e.g. personal cycling trainer in Johannesburg, running coach near Sandton, coaches near Fourways. Use it for any coach, personal trainer, coaching or training group question (never find_clubs, which lists clubs). Lists coaches and training groups on Windline (cycling) and RunFast (running) nearest first, with what they coach (road, MTB, gravel, triathlon, beginners, racing, marathon, ultra), how (1-on-1, small group, online), their next group session with its weather, whether beginners are welcome, the qualifications they state in their own words (livedot doesn't check them), a Book / contact link (their own) and their page. Only coaches who listed themselves and added their area; never anyone else. Say what each coach chose to share, and nothing more.

  Paramètres, retour & exemple (7)

  Paramètres

  • km · number · optionnel
    How far from the place, in km (1 to 100). Leave it out for 25 km.
  • place · string · requis
    The suburb, town or city, as the user said it, e.g. "Fourways", "Durban North", "Cape Town".
  • sport · string · optionnel · cycling | running
    cycling or running. Leave it out for both.
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.
  • format · string · optionnel · one-to-one | group | online
    one-to-one for a personal trainer or private coaching, group for a training group or small group, online for remote coaching.
  • beginners · boolean · optionnel
    true when the user is new to the sport ("for beginners", "new to running").
  • specialty · string · optionnel · road | mtb | gravel | triathlon | beginners | racing | marathon | ultra
    What the coach coaches, if the user said: road, mtb, gravel, triathlon, beginners, racing, marathon or ultra.

  Exemple d'appel

  {"name": "find_coaches", "arguments": {"place": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"km": 1, "app": "texte", "view": "coaches", "error": "texte", "place": "texte", "sport": "texte", "units": "metric", "format": "texte", "signup": "texte", "coaches": [], "message": "texte", "add_club": "texte"}}

• find_events≈ 910 tokens

  Find public cycling and running events near a place and when: races, multi-day tours, club rides and club runs on Windline and RunFast, e.g. trail runs near Cape Town in November, cycle tours around Johannesburg. Each with its date, where it starts, the weather (the forecast within 10 days, typical weather beyond), its club or organiser and an I'm in link to its page. Only published public events of approved clubs and organisers.

  Paramètres, retour & exemple (6)

  Paramètres

  • km · number · optionnel
    How far from the place, in km (1 to 100). Leave it out for 50 km.
  • kind · string · optionnel · race | tour | club ride | club run
    Only races, only multi-day tours, or only club rides or runs.
  • when · string · optionnel
    When, as the user said it: "November", "this weekend", "next month", "2026-11-14", or "2026-11-01 to 2026-11-30". Leave it out for the next four months.
  • place · string · requis
    The suburb, town or city, as the user said it, e.g. "Fourways", "Durban North", "Cape Town".
  • sport · string · optionnel · cycling | running | road | gravel | mtb | road-run | trail-run | tours
    cycling or running, or one sport: road, gravel, mtb, road-run, trail-run, tours (multi-day tours). Leave it out for both.
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.

  Exemple d'appel

  {"name": "find_events", "arguments": {"place": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"km": 1, "app": "texte", "view": "events", "when": "texte", "error": "texte", "place": "texte", "sport": "texte", "units": "metric", "events": [], "signup": "texte", "message": "texte", "add_club": "texte"}}

• find_person≈ 1776 tokens

  Finds a person who is live on livedot right now (cycling on Windline, running on RunFast) and answers where they are. Use it when the user asks where someone is or how they're doing in a race ("Where's Megan in the Comrades?"), or gives a livedot handle (@megan, livedot.me/megan) or a follow link. Inputs: name_or_handle as the user wrote it; event if they named the race; surname, bib, club, place or wave to narrow. Returns: for one clear match, the live answer (position, time against goal, finish estimate, the weather there) with a live map; for several matches, the 5 most likely and the total, so the user can pick (then call where_is with the chosen person id, or call again with what they add). Limits: only people who chose to be findable on public races can be found by name; a ride or run of their own (Ride live, Run live) only by their handle or follow link, never showing where it starts or ends. Read-only.

  Paramètres, retour & exemple (8)

  Paramètres

  • bib · string · optionnel
    A bib number, if the user gave one.
  • club · string · optionnel
    A club, if the user gave one.
  • wave · string · optionnel
    A start wave or start time, if the user gave one.
  • event · string · optionnel
    The race, if named: "Comrades", "Coast Classic". Narrows the search to that race.
  • place · string · optionnel
    A home town or country, if the user gave one.
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.
  • surname · string · optionnel
    A surname or its first letter, to narrow many matches.
  • name_or_handle · string · requis
    The person's name as the user said it ("Megan", "Megan Naidoo"), a livedot handle exactly as typed ("@megan", "livedot.me/megan"; a capitalised name like "Megan" is searched as a name), or a follow link (livedot.me/megan, windline.tech/f/…, runfast.tech/f/…).

  Exemple d'appel

  {"name": "find_person", "arguments": {"name_or_handle": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "app": "windline", "eta": {}, "club": {}, "goal": {}, "name": "texte", "pace": {}, "race": "texte", "team": "texte", "view": "person", "ahead": [], "clubs": []}}

• fly_route≈ 803 tokens

  Fly over a race course inline: "Fly the Comrades", "Show me the course", "What does the NYC Marathon route look like?". Returns a flyover of the course on a map that plays in the chat, coloured by the weather along it (the live forecast within 10 days of the start, 10 years of weather on that date beyond it, as event_weather), with a "Fly it in 3D" link to the full Fly the route and the event's livedot page. If several events match it lists them: ask which one. For a route the user gave as a GPX file or link (their own route), use plan_route: it flies over that route too.

  Paramètres, retour & exemple (3)

  Paramètres

  • year · integer · optionnel
    The edition's year, if named.
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.
  • event_or_route · string · requis
    The event or route, e.g. "Comrades", "NYC Marathon", "Gravel Burn".

  Exemple d'appel

  {"name": "fly_route", "arguments": {"event_or_route": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"km": 1, "url": "texte", "days": [], "view": "fly_route", "basis": "forecast", "error": "texte", "event": "texte", "sport": "texte", "units": "metric", "events": [], "signup": "texte", "fly_url": "texte"}}

• invite_members≈ 1058 tokens

  Invite a club's members, or a tour's riders, by email, from a list the organiser gives (a CSV, a spreadsheet's text, or names and addresses typed in): for a club or organiser page the signed-in person runs (page on Windline, club on RunFast) or a published tour of theirs (event). Each person gets one email from livedot: "<club> added you as a member" (or "<organiser> added you to <tour>") with Confirm; nobody joins until they confirm, and nobody is invited twice. The first call (without confirm) only reads the list and returns who would be invited and who's skipped (listed twice, invited before, unsubscribed, no usable email): show the organiser that, get a yes, then call again with confirm: true. A day's limit: 500 for club admins and managers, 50 for a tour's organiser, 20 for an account under a week old; the preview says how many go today.

  Paramètres, retour & exemple (7)

  Paramètres

  • csv · string · optionnel
    The list as the organiser gave it: a CSV or spreadsheet's text (any delimiter, with or without a header row), up to 2,000 people.
  • club · string · optionnel
    RunFast: the club address they manage (runfast.tech/c/<address>).
  • page · string · optionnel
    Windline: the club page address they run (livedot.me/<address> or windline.tech/c/<address>).
  • event · string · optionnel
    A published Windline tour of theirs, by its id from list_my_events.
  • people · array · optionnel
    Or the people as a list: [{ name, email }].
  • confirm · boolean · optionnel
    true only after the organiser said yes to the preview this tool returned.
  • csv_file · object · optionnel
    The CSV or spreadsheet the organiser attached (ChatGPT passes it here); or pass its text as csv.

  Exemple d'appel

  {"name": "invite_members", "arguments": {"csv": "texte", "club": "texte", "page": "texte", "event": "texte", "people": [], "confirm": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"app": "texte", "sent": "texte", "view": "invites", "error": "texte", "state": "texte", "failed": "texte", "people": "texte", "signup": "texte", "target": "texte", "invalid": "texte", "message": "texte", "skipped": "texte"}}

• list_my_events≈ 690 tokens

  The signed-in organiser's own events on Windline (rides, tours, races) or RunFast (runs, races, and their clubs' runs): each with its id, status (draft or published), who it's for (private or shared), dates, distance, whether it's finished, and its dashboard, public or private links; and the club and organiser pages they run (pages on Windline, clubs on RunFast). Call it before making a new event, to know whether to ask who it's for; and to find an event id before changing one.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_my_events", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "app": "texte", "url": "texte", "days": "texte", "link": "texte", "note": "texte", "view": "my_events", "clubs": "texte", "error": "texte", "order": "texte", "pages": "texte", "events": "texte"}}

• plan_route≈ 2070 tokens

  Weather and a flyover for a GPX file or route the user shares. If the user attached a GPX or route file, call plan_route and pass the file as gpx_file; if you can read the file's contents yourself, you may instead pass its text as gpx or its points as points. Never treat a file name as an event name. Also a Ride with GPS or GPX link, or another app's route points: the weather along it at the time they'd ride or run it, and a flyover of the route (a flyby, fly over my route) that plays in the chat, coloured by the weather: the forecast within 10 days, 10 years of weather on that date beyond it, rated by Windline's forecast engine, with the headwind and tailwind stretches, heat and rain. No account needed. For "What will the wind be like on this route on Saturday at 6?" or "Show me the weather for this GPX and a flyover". The route stays theirs: nothing is published. For a 3D flight and a route video, offer to save it as a private ride or run with create_event (visibility private). Several GPX files are one multi-day tour: pass them all as files (ordered by the numbers in their names, else by the map; one day after another from start), never one call per file. A route can also come from another app's tool as its points or an encoded polyline (for example a route or activity map from a fitness app): pass it as polyline or points. Never ask the user to export a GPX if you already have the route's points.

  Paramètres, retour & exemple (15)

  Paramètres

  • tz · string · optionnel
    The route's IANA time zone, if known (else worked out from where it starts).
  • gpx · string · optionnel
    The GPX file's text (up to 5 MB): if the user pasted it, or attached a file you can read yourself (for example with code).
  • url · string · optionnel
    A link to the route: a Ride with GPS route, ride or collection (a collection gives one day per route), or any public link to a GPX file. Not Strava.
  • name · string · optionnel
    What to call the plan, if the user named it.
  • pace · number · optionnel
    Riding speed in km/h (default 25), or running pace in minutes per km (default 6).
  • files · array · optionnel
    Several GPX files (a multi-day tour): ordered by the numbers in their names, else by the map; one day after another from start.
  • sport · string · optionnel · ride | run
    ride (default) or run.
  • start · string · requis
    When they start, "YYYY-MM-DD HH:MM" local to the route. Ask if they didn't say.
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.
  • points · array · optionnel
    The route as its points: [[lat, lon], …], with elevation in metres as a third number if known. Up to 50,000. Use it for points another app's tool gave, or that you read from an attached file (GPX, FIT, TCX) with code.
  • starts · array · optionnel
    Each day's own local start, "YYYY-MM-DD HH:MM", when they differ.
  • gpx_file · object · optionnel
    The GPX or route file the user attached (ChatGPT passes it here).
  • polyline · string · optionnel
    The route as an encoded polyline (Google's format, precision 5 or 6), as another app's tool gives it (a route's or an activity's map).
  • gpx_files · array · optionnel
    Several GPX or route files the user attached (ChatGPT passes them here): one per day of a tour, ordered by the numbers in their names, else by the map.
  • rest_days · array · optionnel
    With files: dates with no riding, "YYYY-MM-DD", only if the user named rest days.

  Exemple d'appel

  {"name": "plan_route", "arguments": {"start": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"km": 1, "tz": "texte", "url": "texte", "days": [], "view": "plan_route", "basis": "forecast", "error": "texte", "event": "texte", "files": "texte", "order": "texte", "sport": "texte", "units": "metric"}}

• post_club_ride≈ 1338 tokens

  Post a DRAFT group ride (Windline) or club run (RunFast) on a club or organiser page the signed-in person runs, from a GPX route or link, once or weekly: always for the group, never private. Publish it with publish_event. Confirm the details with the user first. If the signed-in person runs any club or organiser page (list_my_events lists them) and hasn't said who it's for, ask one short question first: is this a private ride or run for you, or a group ride or run for <club name>? Then use post_club_ride for the club, or create_event with visibility private for themselves. A route can also come from another app's tool as its points or an encoded polyline (for example a route or activity map from a fitness app): pass it as polyline or points. Never ask the user to export a GPX if you already have the route's points.

  Paramètres, retour & exemple (12)

  Paramètres

  • tz · string · optionnel
    IANA time zone; else worked out from where the route starts.
  • gpx · string · optionnel
    The GPX file's text (up to 5 MB): if the user pasted it, or attached a file you can read yourself (for example with code).
  • url · string · optionnel
    A link to the route: a Ride with GPS route, ride or collection (a collection gives one day per route), or any public link to a GPX file. Not Strava.
  • name · string · requis
    The ride's or run's name, e.g. "Saturday coffee ride".
  • page · string · requis
    The club or organiser page address (livedot.me/<address>).
  • place · string · optionnel
    RunFast: where it starts, in words.
  • start · string · requis
    A one-off: "YYYY-MM-DD HH:MM" local. Weekly: the first one.
  • points · array · optionnel
    The route as its points: [[lat, lon], …], with elevation in metres as a third number if known. Up to 50,000. Use it for points another app's tool gave, or that you read from an attached file (GPX, FIT, TCX) with code.
  • weekly · object · optionnel
    Weekly: { days: [0-6, Sunday is 0], time: "HH:MM" }.
  • gpx_file · object · optionnel
    The GPX or route file the user attached (ChatGPT passes it here).
  • polyline · string · optionnel
    The route as an encoded polyline (Google's format, precision 5 or 6), as another app's tool gives it (a route's or an activity's map).
  • description · string · optionnel
    What the ride or run is, for the club page.

  Exemple d'appel

  {"name": "post_club_ride", "arguments": {"name": "texte", "page": "texte", "start": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "app": "texte", "url": "texte", "days": "texte", "link": "texte", "note": "texte", "view": "club_ride", "clubs": "texte", "error": "texte", "order": "texte", "pages": "texte", "events": "texte"}}

• publish_event≈ 730 tokens

  Publish one of the signed-in organiser's draft events, so anyone with its link can see it (Windline: at tour., event. or ride.windline.tech/<address>). Private events can't be published. ALWAYS ask the user to confirm first, then call with confirm: true.

  Paramètres, retour & exemple (3)

  Paramètres

  • address · string · optionnel
    Windline: the public address, lowercase letters, numbers and hyphens, e.g. "cape-coast-2027".
  • confirm · boolean · requis
    true only after the user said yes.
  • event_id · string · requis
    The draft's id, from list_my_events or create_event.

  Exemple d'appel

  {"name": "publish_event", "arguments": {"confirm": true, "event_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "app": "texte", "url": "texte", "days": "texte", "link": "texte", "note": "texte", "view": "publish_event", "clubs": "texte", "error": "texte", "order": "texte", "pages": "texte", "events": "texte"}}

• tap_on_the_back≈ 1864 tokens

  Sends a tap on the back: a short buzz on the person's phone, with the sender's name if signed in (or a first name they give). In the day after a finish it arrives as a congratulation. Use it only when the user explicitly asks to give someone a tap on the back; one tap per request. Inputs: person (an id from find_person), or a livedot handle or follow link; or tour (the tap goes to the tour's organiser on its days); or club with event (one tap to each member on the club's live map who accepts taps). Side effects: sends a notification to the person (or to each club member, and it reports how many). Limits: follows each person's own settings; if taps are off, they aren't live, or they only accept taps from people with their link, it sends nothing and says so. Returns the live map.

  Paramètres, retour & exemple (9)

  Paramètres

  • club · string · optionnel
    A club or team, by its name or page address, or the club id a club card gave ("runfast:demo"): one tap to each of its members on the map.
  • code · string · optionnel
    A follow link or its code (windline.tech/f/<code>, runfast.tech/f/<code>).
  • name · string · optionnel
    The first name the user wants on the tap ("Sam"), if they gave one. A signed-in user's tap shows their own public name instead.
  • tour · string · optionnel
    A Windline tour, by its name, address or organiser ("Alistair's Durban tour"): the tap goes to the tour's organiser, who reads them out at night.
  • coach · string · optionnel
    A coach, or the coach id a team card gave ("runfast:coach-nadia-pillay"): one tap to each of their athletes on the map.
  • event · string · optionnel
    With club or coach: the race they are in, if named.
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.
  • handle · string · optionnel
    A livedot handle ("megan") or link (livedot.me/megan).
  • person · string · optionnel
    A person id from find_person, e.g. "runfast:p:pdemo00megan" or "h:megan".

  Exemple d'appel

  {"name": "tap_on_the_back", "arguments": {"club": "texte", "code": "texte", "name": "texte", "tour": "texte", "coach": "texte", "event": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "app": "windline", "eta": {}, "club": {}, "goal": {}, "name": "texte", "pace": {}, "race": "texte", "sent": true, "taps": "texte", "team": "texte", "tour": "texte"}}

• tour_notes≈ 565 tokens

  Beta, cycling tours only: the organiser's own notes for riders on a Windline tour (what to pack, how the tour runs, meeting points), for questions like "What should I pack for the Durban tour?". Answer only from the notes: quote and summarise them as the organiser's words, never invent anything, and say so when they don't cover the question.

  Paramètres, retour & exemple (2)

  Paramètres

  • tour · string · requis
    The tour's name, address or organiser.
  • question · string · optionnel
    The rider's question, if any.

  Exemple d'appel

  {"name": "tour_notes", "arguments": {"tour": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "beta": true, "tour": "texte", "view": "tour_notes", "error": "texte", "notes": "texte", "tours": [], "signup": "texte", "message": "texte", "sponsor_line": "texte", "notes_updated": "texte"}}

• tour_route≈ 911 tokens

  A Windline cycling tour's route, day by day: "What's the Durban Tour 2027 route?", "Give me the GPX files for Alistair's tour", "Where is Alistair's Durban tour?". On the tour's days its card offers a tap on the back for the organiser (tap_on_the_back with tour). To fly over day 3 of a tour ("Give me the flyover for day 3 of TSF 2026"), pass day: 3. Finds a published tour by its name, its address or its organiser's or club's name, and returns each day (from and to, distance, climbing, start time), a map of every day, and the weather (the live forecast within 10 days, 10 years of weather on the date beyond). Route files (GPX, Garmin .fit) only when the organiser lets riders download them; otherwise say "The organiser hasn't made the route files available." Never make up a file link. If several tours match, ask which.

  Paramètres, retour & exemple (3)

  Paramètres

  • day · integer · optionnel
    One day of the tour to fly over (1 for day 1), when the user asks for a day: the flyover of that day and its Fly it in 3D link.
  • tour · string · requis
    The tour's name, address or organiser, e.g. "ProLend 2027 Durban Tour", "AllyCat".
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.

  Exemple d'appel

  {"name": "tour_route", "arguments": {"tour": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"day": 1, "gpx": [], "url": "texte", "days": [], "slug": "texte", "tour": "texte", "view": "tour_route", "error": "texte", "tours": [], "signup": "texte", "can_tap": true, "day_url": "texte"}}

• update_event≈ 842 tokens

  Change one of the signed-in organiser's events: its name, description or notes, or start dates and times. Never a finished event (finished events stay as they were). Tell the user exactly what will change and get a yes first.

  Paramètres, retour & exemple (8)

  Paramètres

  • date · string · optionnel
    A one-off ride or run: its new date, YYYY-MM-DD.
  • days · array · optionnel
    Windline tours and races: [{ day: 2, date?: "YYYY-MM-DD", time?: "HH:MM" }].
  • name · string · optionnel
    A new name.
  • time · string · optionnel
    A ride or run: its new start time, HH:MM.
  • notes · string · optionnel
    RunFast runs only (tours: add_tour_notes).
  • place · string · optionnel
    RunFast: where it starts, in words.
  • event_id · string · requis
    From list_my_events.
  • description · string · optionnel
    A new description for its public page.

  Exemple d'appel

  {"name": "update_event", "arguments": {"event_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "app": "texte", "url": "texte", "days": "texte", "link": "texte", "note": "texte", "view": "update_event", "clubs": "texte", "error": "texte", "order": "texte", "pages": "texte", "events": "texte"}}

• where_is≈ 1358 tokens

  Where someone is right now, in a live race or on a ride or run of their own (Ride live, Run live), and the weather they're in: km and mile on the course, time against their goal, pace, the finish time it points to, the temperature and wind there (headwind, tailwind or side-on) with the Windline forecast engine's rating, the wind and heat over the next few km, and a live map with a Follow live button. Use it with the person id find_person returned, or straight away with a livedot handle or follow link the user gave. It answers only what the public live page shows: if they're paused, stopped, near the start or finish, or not sharing, it says it can't share where they are; say so plainly.

  Paramètres, retour & exemple (4)

  Paramètres

  • code · string · optionnel
    A follow link or its code (windline.tech/f/<code>, runfast.tech/f/<code>). "demo" with app gives the demo.
  • units · string · optionnel · metric | imperial
    Pass the asker's units: imperial for users in the US, UK road distances, Liberia or Myanmar, or when they ask in miles/°F; otherwise metric.
  • handle · string · optionnel
    A livedot handle ("megan") or link (livedot.me/megan).
  • person · string · optionnel
    A person id from find_person, e.g. "runfast:p:pdemo00megan" or "h:megan".

  Exemple d'appel

  {"name": "where_is", "arguments": {"code": "texte", "units": "metric", "handle": "texte", "person": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"id": "texte", "app": "windline", "eta": {}, "goal": {}, "name": "texte", "pace": {}, "race": "texte", "team": "texte", "view": "person", "ahead": [], "error": "texte", "photo": "texte"}}

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://livedot.me/mcp