accueil / serveurs / Finance & Paiement / run.cityheart/heart-routes
run.cityheart/heart-routes
serveur MCP (Model Context Protocol) · cityheart 1.0.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 run.cityheart/heart-routes est sûr ?
Au dernier audit MCP Hub, le serveur MCP « run.cityheart/heart-routes » 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 7 outils
- add_cause≈ 180 tokens
Compose a builder URL with a fundraising link pre-filled — the URL is embedded into the GPX metadata (description, filename) so it surfaces in the runner's Strava activity after they sync. CityHeart never collects the donation; the runner's donors click straight through to JustGiving / GoFundMe / Leetchi / etc.
Paramètres, retour & exemple (2)
Paramètrescity· string · optionnel
Optional city to also pre-fill.fundraising_url· string · requis
Fully-qualified donation URL (https://www.justgiving.com/... / https://gofundme.com/... / https://leetchi.com/... / https://www.helloasso.com/...).
Exemple d'appel{"name": "add_cause", "arguments": {"fundraising_url": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - add_dedication≈ 187 tokens
Compose a builder URL with a dedication pre-filled — the name shows on the runner's GPS watch and in the Strava activity title. Use after the user picks a route (find/generate) and decides who the heart is for. Pure URL builder, no server-side state.
Paramètres, retour & exemple (3)
Paramètrescity· string · optionnel
Optional city to also pre-fill in the builder (skips the "pick a city" step in the chat-to-product handoff).name· string · requis
Dedication name (e.g. "Marie", "Dad", "Cancer Research UK").in_memory· boolean · optionnel
If true, framed as "In memory of [name]". Default false.
Exemple d'appel{"name": "add_dedication", "arguments": {"name": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - export_gpx≈ 125 tokens
Return the GPX download / checkout URL for a specific public route. The download itself happens on cityheart.run after a one-time €7.99 payment (Stripe — CityHeart never charges through the chat). Use after the user has picked a final route (find / get_details) and confirms they want it.
Paramètres, retour & exemple (1)
Paramètresslug· string · requis
Route slug, e.g. "paris-7-2-km-heart-for-marie".
Exemple d'appel{"name": "export_gpx", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - find_heart_route_in_city≈ 226 tokens
Find an existing heart-shaped running route in a given city. Returns up to 5 AI-validated routes matching the city (and optionally a target distance). Use this when a user mentions a city and wants a heart route — e.g. "find me a heart-shaped route in Paris" or "I want to run a heart in Tokyo for my mum's birthday".
Paramètres, retour & exemple (3)
Paramètrescity· string · requis
City name, e.g. "Paris", "Tokyo", "New York". Case-insensitive.prefer_gold· boolean · optionnel
If true, return only the highest AI-quality "gold" tier routes (ai_score >= 80). Default true.max_distance_km· number · optionnel
Optional max route length in kilometres. Filter to routes ≤ this distance. Common: 5, 10, 15, 21 (half-marathon).
Exemple d'appel{"name": "find_heart_route_in_city", "arguments": {"city": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - generate_heart_route≈ 328 tokens
Start a new heart-shaped route for a given city. Returns existing AI-validated matches from inventory PLUS a deep-link to the live builder for an on-demand fresh generation with the user's exact dedication and cause. Use when the user explicitly wants a NEW heart, or when an existing match is "close enough but not personal yet". Optional dedication / cause_url pre-fill the builder fields, so the URL deep-link arrives configured.
Paramètres, retour & exemple (5)
Paramètrescity· string · requis
City name, e.g. "Paris", "Tokyo".cause_url· string · optionnel
Optional JustGiving / GoFundMe / Leetchi URL to embed in the GPX metadata. CityHeart never touches the money — the link is for the runner's Strava description to surface to donors.in_memory· boolean · optionnel
If true, the dedication is framed as a memorial ("In memory of [name]"). Default false.dedication· string · optionnel
Optional person/cause name to bake into the heart (appears in the GPX, on Garmin Connect, and as the Strava activity title prefix).distance_km· number · optionnel
Target route length in km (3–25). Default 7.
Exemple d'appel{"name": "generate_heart_route", "arguments": {"city": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - get_route_details≈ 108 tokens
Get full details for a specific heart route by its slug. Use after find_heart_route_in_city when the user picks one. Returns: city, distance, image URL, share URL, dedication (if any), and the GPX download deep-link.
Paramètres, retour & exemple (1)
Paramètresslug· string · requis
Route slug, e.g. "paris-7-2-km-heart-for-marie".
Exemple d'appel{"name": "get_route_details", "arguments": {"slug": "texte"}}Exemple de retour{"content": [{"type": "text", "text": "…"}]} - list_supported_cities≈ 104 tokens
List cities that have at least one heart route available. Use when the user asks "where can I run a heart?" or hasn't picked a city yet. Returns city names + route counts, sorted by inventory size.
Paramètres, retour & exemple (1)
Paramètreslimit· number · optionnel
Max number of cities to return. Default 25, max 100.
Exemple d'appel{"name": "list_supported_cities", "arguments": {"limit": 1}}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é ».