com.atly/places

Est-ce que com.atly/places est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.atly/places » 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

• get_api_key≈ 343 tokens

  Show my key, tier and remaining quota Who am I and how much quota is left. Works without a key too (then it describes the anonymous allowance for your IP).

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_api_key", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"tier": "texte", "label": "texte", "quota": "texte", "key_id": "texte", "call_id": "texte", "doc_notes": "texte", "email_verified": true}}

• get_docs≈ 134 tokens

  Read the documentation Returns the API guide as Markdown: what each operation is for, how to turn a user's request into category ids and a location, request and response shapes, how to read scores. Call this once per session.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_docs", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_place≈ 1032 tokens

  Everything about one place Full detail for a place id from `search_places`: profile, hours, all category scores, up to eight quotable statements, good-to-know facts, gluten-free identity when known, and the canonical Atly URL to cite.

  Paramètres, retour & exemple (1)

  Paramètres

  • id · string · requis

  Exemple d'appel

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

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"place": "texte", "call_id": "texte", "doc_notes": "texte"}}

• list_areas≈ 576 tokens

  List supported areas Cities, neighborhoods and states Atly covers — densest in the United States, with pockets in Mexico, Israel and Thailand — each with an `id` you can pass to search, a center, a bounding box when known, and how many places it holds. Filter with `q` (substring of the name) and `level` (city, neighborhood, state). Results are ordered by place count.

  Paramètres, retour & exemple (3)

  Paramètres

  • q · string · optionnel
    Area name or common abbreviation, e.g. "san diego", "midtown", "nyc". Exact and prefix matches rank first.
  • level · string · optionnel · city | neighborhood | state
    Restrict to one level.
  • limit · integer · optionnel

  Exemple d'appel

  {"name": "list_areas", "arguments": {"q": "texte", "level": "city", "limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"areas": "texte", "total": "texte", "call_id": "texte", "doc_notes": "texte"}}

• list_categories≈ 443 tokens

  List intent categories The intent taxonomy: cuisines, dishes, features ("Wifi", "Outdoor Seating"), vibes ("Cozy", "Lively"), occasions ("First Date", "Group Dinner"), diets ("Gluten Free", "Keto") and more. Map the user's words to category ids before searching. Filter with `q`, one concept per call — exact and prefix matches rank first, then substrings and keywords; plurals, hyphens and small typos are tolerated — or fetch once without `q` and cache the full list.

  Paramètres, retour & exemple (2)

  Paramètres

  • q · string · optionnel
    Words to match against category names and keywords, e.g. "coffee", "dog friendly", "gluten-free". Ranked; tolerant of plurals and small typos.
  • limit · integer · optionnel
    Maximum categories to return.

  Exemple d'appel

  {"name": "list_categories", "arguments": {"q": "texte", "limit": 1}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"total": "texte", "call_id": "texte", "doc_notes": "texte", "categories": "texte"}}

• search_places≈ 1344 tokens

  Find places for an intent near a location The core call. Give one or more category ids (from `list_categories`; all must match) and a location — either an `area_id` from `list_areas` or coordinates with a radius — and get places ranked by Atly's score for those categories, each with quotable reasons from real reviews, a link to cite, and freshness. Scores are 0–10 and relative to the area; a place with no score is unmeasured, not bad. If no place matches every category, trailing categories are dropped until something does (the first is never dropped), and `dropped_categories` says which. Ranking considers the strongest 100 candidates by Atly's base score. Scores are relative to other places in the same country.

  Paramètres, retour & exemple (6)

  Paramètres

  • lat · number · optionnel
  • lon · number · optionnel
  • limit · integer · optionnel
  • area_id · string · optionnel
    An id from `list_areas`; the search covers that area's viewport. Give this or lat/lon, not both.
  • radius_km · number · optionnel
    Used with lat/lon.
  • categories · array · requis
    Category ids, most important first. Every result matches all of them (after any relaxation).

  Exemple d'appel

  {"name": "search_places", "arguments": {"categories": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"area": "texte", "places": "texte", "call_id": "texte", "doc_notes": "texte", "total_matched": "texte", "dropped_categories": "texte"}}

• submit_feedback≈ 308 tokens

  Tell us how a call went Reference the `call_id` of any earlier response and say whether it helped, and optionally why, in a sentence about the result — what was right, missing or wrong. Do not include the user's words, the conversation, or anything about the person. One row per caller per call; lightly rate-limited.

  Paramètres, retour & exemple (3)

  Paramètres

  • notes · string · optionnel
    About the result only — never the conversation or the user.
  • call_id · string · requis
  • outcome · string · requis · helpful | partly_helpful | not_helpful | wrong

  Exemple d'appel

  {"name": "submit_feedback", "arguments": {"call_id": "texte", "outcome": "helpful"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"call_id": "texte", "recorded": true, "doc_notes": "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://agentic-api.atly.com/mcp