com.pickyourmatch/stays

Est-ce que com.pickyourmatch/stays est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.pickyourmatch/stays » 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 4 outils

• list_destinations≈ 327 tokens

  List all destinations served by pickyourmatch with unit counts, dog-friendly counts and a photo — USE THIS to inspire a guest who has not decided where to travel yet. ALWAYS pass the party (adults/children/pets) and dates (check_in/check_out) already known from the conversation — they stay visible above the results and keep the search context.

  Paramètres, retour & exemple (7)

  Paramètres

  • dogs · integer · optionnel
    Alias for pets.
  • lang · string · optionnel · en | de | fr | es | it | nl | ar
  • pets · integer · optionnel
    Pets/dogs already mentioned — always pass along; destinations are then ranked by dog-friendly units.
  • adults · integer · optionnel
    Adults already mentioned in the conversation — always pass along.
  • check_in · string · optionnel
    Arrival YYYY-MM-DD if already known — always pass along.
  • children · integer · optionnel
    Children already mentioned — always pass along.
  • check_out · string · optionnel
    Departure YYYY-MM-DD if already known — always pass along.

  Exemple d'appel

  {"name": "list_destinations", "arguments": {"dogs": 1, "lang": "en", "pets": 1, "adults": 1, "check_in": "texte", "children": 1}}

  Exemple de retour

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

• list_events≈ 650 tokens

  List upcoming events (concerts, festivals, trade fairs, sports, conferences) near pickyourmatch properties — each with a "where to stay" page whose booking links open the property’s own calendar with the event dates preselected. USE THIS whenever a guest asks for accommodation during/for a specific event or asks what is happening at a destination — e.g. "where should I stay for the Frankfurt Book Fair?", "hotel for Oktoberfest that allows my dog", "apartment for the ski race in Schladming". Combine with search_stays to add room features: event + exact room + direct booking in one answer.

  Paramètres, retour & exemple (5)

  Paramètres

  • to · string · optionnel
    Only events starting on/before this date YYYY-MM-DD
  • city · string · optionnel
    Filter by destination city (umlaut-tolerant)
  • from · string · optionnel
    Only events ending on/after this date YYYY-MM-DD
  • limit · integer · optionnel
    Max results (default 20, max 50)
  • query · string · optionnel
    Match against the event name, e.g. "Oktoberfest"

  Exemple d'appel

  {"name": "list_events", "arguments": {"to": "texte", "city": "texte", "from": "texte", "limit": 1, "query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"city": "texte", "lang": "texte", "query": "texte", "total": 1, "events": [], "guidance": "texte"}}

• list_packages≈ 447 tokens

  Theme-driven, AFTER the units: when the brief carries a package theme (romantic, wellness, dog, culinary) or the guest asks for deals, call this AFTER search_stays in the same turn - the packages appear as their own section BELOW the unit results and enrich the selection. Never call it first, never instead of the unit search. List themed holiday packages (promotional bundles) across properties — dog holidays, romance, wellness, culinary — each with included extras (e.g. dinner, treatments) and a direct booking link. Use for emotional/experience queries like "romantic getaway package" or "dog holiday with meals included".

  Paramètres, retour & exemple (9)

  Paramètres

  • city · string · optionnel
    Filter by destination city (umlaut-tolerant)
  • dogs · integer · optionnel
    Alias for pets.
  • lang · string · optionnel · en | de | fr | es | it | nl | ar
  • pets · integer · optionnel
    Pets/dogs known from the conversation — always pass along.
  • theme · string · optionnel · dog | romance | wellness | family | ski | culinary
    Filter by package theme
  • adults · integer · optionnel
    Adults known from the conversation — always pass along (kept visible above results).
  • check_in · string · optionnel
    Arrival YYYY-MM-DD if known — always pass along.
  • children · integer · optionnel
    Children known from the conversation — always pass along.
  • check_out · string · optionnel
    Departure YYYY-MM-DD if known — always pass along.

  Exemple d'appel

  {"name": "list_packages", "arguments": {"city": "texte", "dogs": 1, "lang": "en", "pets": 1, "theme": "dog", "adults": 1}}

  Exemple de retour

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

• search_stays≈ 1427 tokens

  Search accommodation at participating properties — hotel rooms, apartments and holiday homes. Search criteria: destination (a town, a landmark or venue, or coordinates, with a radius), travel dates, the party (adults, children and their ages, pets), a maximum nightly price, free cancellation, unit features (view, balcony, terrace, quiet location, floor, workspace, sauna, kitchen, accessibility), the name of a unit or property, the response language and the number of results. Each result is one specific unit, described with its floor, view and beds, and guaranteed at booking — what the product states is what the guest is assigned. Without dates the results carry from-prices; with check_in and check_out they are the units available for those dates, with the price for the stay and a link to the property's booking page. All parameters are optional; query may state the same criteria as free text. Each result carries match_score, matched_features and not_confirmed_features.

  Paramètres, retour & exemple (22)

  Paramètres

  • lat · number · optionnel
    Latitude of the place to search around (a landmark or venue) — an alternative to near.
  • lng · number · optionnel
    Longitude of the place to search around (a landmark or venue) — an alternative to near.
  • city · string · optionnel
    The destination to search in — the town or city where the guest wants to stay, e.g. Schladming (umlaut-tolerant).
  • dogs · integer · optionnel
    Alias for pets.
  • lang · string · optionnel · en | de | fr | es | it | nl | ar
    Language for names/features/links (default en)
  • name · string · optionnel
    A specific unit or property the guest named ("Villa Albatros No. 1", "Kaiser Karl", "City Hotel Meckenheim"). Use it when the guest asks for a unit or property by name — it matches unit and property names directly, so a named unit is found even when it is not free for the requested dates. A named unit is never filtered out by availability: it comes back with its status and a link to the property's own calendar.
  • near · string · optionnel
    A landmark, venue, trade fair, station or address to stay close to ("Messe Frankfurt", "Allianz Arena", "Frankfurt airport"). The server geocodes it and returns results nearest first, each with approx_km. Combine freely with dates, party, price and features.
  • pets · integer · optionnel
    Number of pets/dogs. Filters to units that allow at least this many pets, and is passed to the booking link.
  • limit · integer · optionnel
    Max results (default 10, max 30)
  • query · string · optionnel
    Optional: the same search criteria as free text, in any language — for example "apartment in Schladming for 2 adults and a dog, 16–19 August, with sauna". Destination, dates (a month alone gets a proposed window), party, budget and features are read from it; explicit parameters override.
  • adults · integer · optionnel
    Number of adults. Combined with children it filters to units that actually fit the whole party (occupancy), and is passed to the booking link.
  • cursor · integer · optionnel
    Dated searches live-check up to 20 properties per call. When the response carries next_cursor, repeat the SAME search with cursor=next_cursor to check the remaining properties — a page without next_cursor has covered everything. Never conclude "sold out" from a page whose coverage.complete is false.
  • sleeps · integer · optionnel
    Minimum total guests the unit must sleep (use adults+children instead when you know the split).
  • check_in · string · optionnel
    Arrival date YYYY-MM-DD. With check_in and check_out, results are the units available for those dates, with the nightly price for that stay and a booking link with the dates filled in.
  • children · integer · optionnel
    Number of children. Filters to units whose child capacity fits, and is passed to the booking link.
  • features · array · optionnel
    Required features (matched against localized feature names), e.g. ["Sauna", "Balkon"]. Also what a property sells as a bookable extra: "Airport transfer", "Parking", "Baby cot", "Late check-out" — a card then carries the extra with its price in wish_note.
  • check_out · string · optionnel
    Departure date YYYY-MM-DD (must be after check_in, max 30 nights).
  • max_price · number · optionnel
    Maximum nightly price. Dated quotes above this appear only as labeled alternatives when exact matches are insufficient.
  • radius_km · number · optionnel
    Maximum straight-line distance for near (or lat/lng), default 30, max 200. If nothing lies within, the nearest options are returned with their distances.
  • radius_miles · number · optionnel
    The same radius in miles, for guests who think in miles; results then also carry approx_mi.
  • children_ages · array · optionnel
    Ages of the children (0-17), if known, e.g. [16]. Child prices and capacity depend on age.
  • free_cancellation · boolean · optionnel
    The guest wants to be able to cancel for free. With dates, each card quotes the refundable rate and its price; a unit with no refundable rate on those dates is shown only as a labelled alternative.

  Exemple d'appel

  {"name": "search_stays", "arguments": {"lat": 1, "lng": 1, "city": "texte", "dogs": 1, "lang": "en", "name": "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é ».

Créer un compte / revendiquer →

Source

https://pym-mcp.gauvendi.workers.dev/mcp