io.aventuro/mcp

Est-ce que io.aventuro/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.aventuro/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 2 outils

• find_places≈ 2364 tokens

  Use this when the user asks for places, parks, sights, museums, beaches or things to visit in a city, region or near a point. Finds interesting places (sights, museums, parks, nature, beaches and more), ordered by popularity. Returns name, category, city, country, coordinates, distance, a link to the place page (url), a popularity score, a stored travel description and one verified photo with its credit (image, or null). For more about one place, call get_place with the last part of its url. Give q (a place, city or country name, optionally with a category, e.g. "valencia" or "zoo valencia"), or lat/lng of the area the user asks about, or both (q narrowed to radius_km around lat/lng). Optional filters: categories, needs, tastes, parking, setting; tags only rank matching places higher. Write each place name as a markdown link [name](url) when url is present, and show each place's url as the source link. When image is present, show image.url as a markdown image with the author credit. visit_minutes is the typical time visitors spend there, not the time to see everything. attributes gives the five needs as true (known yes) or null (unknown, never a no), and matched_needs lists which of the requested needs the place has. setting (indoor, outdoor, both or null) and parking ({free, paid}, each true or null) follow the same rule. matched_tastes and matched_tags list which of the requested tastes and tags the place hit. content_status is no_description when no travel description is stored; fallback_reason is translation_unavailable when lang differs from the requested one. With q, search_area shows the area q was read as. filter_semantics says how the filters combine.

  Paramètres, retour & exemple (13)

  Paramètres

  • q · string · optionnel
    Free text: a city, country or place name, optionally with a category ("zoo valencia"). Required unless lat/lng are given.
  • lat · number · optionnel
    Latitude of the search center, decimal degrees. Required (with lng) unless q is given.
  • lng · number · optionnel
    Longitude of the search center, decimal degrees. Required (with lat) unless q is given.
  • lang · string · optionnel · en | ru | ua | es | de | fr
    Language of names and descriptions. Falls back to English per place.
  • tags · array · optionnel
    Free-text themes (e.g. "castle", "sunset"). They only move matching places up; nothing is excluded.
  • limit · integer · optionnel
    How many places to return (max 20, or 5 with detail=full).
  • needs · array · optionnel
    Practical needs every result must meet.
  • detail · string · optionnel · brief | full
    brief: summary and top tips. full: the whole stored description.
  • tastes · array · optionnel
    Who or what the place should suit.
  • parking · string · optionnel · both | free
    Parking requirement.
  • setting · string · optionnel · indoor | outdoor
    Indoor or outdoor.
  • radius_km · number · optionnel
    Search radius in km around lat/lng. Out-of-range values are clamped. Ignored without lat/lng.
  • categories · array · optionnel
    Only these categories. Empty means all.

  Exemple d'appel

  {"name": "find_places", "arguments": {"q": "texte", "lat": 1, "lng": 1, "lang": "en", "tags": [], "limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"hint": "texte", "count": 1, "error": {}, "notes": [], "places": [], "applied": {}, "truncated": true, "about_score": "texte", "resolved_as": "city", "search_area": {}, "filter_semantics": "texte"}}

• get_place≈ 1208 tokens

  Use this when the user picks a place from find_places or asks to tell more about it: pass slug = the last part of that place's url (or the whole url). Returns the full details of one Aventuro place: name, category, city, country, coordinates, a link to the place page, the popularity score, the typical time visitors spend there in minutes (visit_minutes, not the time to see everything) and the whole stored travel description (facts, tips, best time, etiquette and more), plus up to 3 verified photos with author and licence credits (images, may be empty). Write the place name as a markdown link [name](url) when url is present and show the url as the source link. When images are present, show each images[].url as a markdown image with its author credit. attributes gives the five needs as true (known yes) or null (unknown, never a no); matched_needs, matched_tastes and matched_tags are always empty here. setting and parking follow the same true-or-null rule. content_status is no_description when no travel description is stored; fallback_reason is translation_unavailable when lang differs from the requested one.

  Paramètres, retour & exemple (3)

  Paramètres

  • lang · string · optionnel · en | ru | ua | es | de | fr
    Language of the name and description. Falls back to English.
  • slug · string · requis
    The place: the last part of a find_places url (e.g. "old-fortress"), or that whole url.
  • detail · string · optionnel · brief | full
    full (default): the whole stored description. brief: summary and top tips.

  Exemple d'appel

  {"name": "get_place", "arguments": {"slug": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"url": "texte", "city": "texte", "lang": "texte", "name": "texte", "tips": [], "avoid": "texte", "error": {}, "facts": [], "score": 1, "images": [], "country": "texte", "parking": {}}}

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://mcp.aventuro.io/mcp