pl.biletyna/events-search

Est-ce que pl.biletyna/events-search est sûr ?

Au dernier audit MCP Hub, le serveur MCP « pl.biletyna/events-search » 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

• get_event_details≈ 125 tokens

  Returns a single performance identified by event_id (as returned by search_events or list_performances), with its title, venue, date, price, free places and buy_url. Free places and price are a snapshot taken at "_meta.indexed_at".

  Paramètres, retour & exemple (1)

  Paramètres

  • event_id · integer · requis
    Performance identifier - an event_id value from search_events or list_performances results.

  Exemple d'appel

  {"name": "get_event_details", "arguments": {"event_id": 1}}

  Exemple de retour

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

• get_title_details≈ 168 tokens

  Returns a single title currently on sale on Biletyna.pl, identified by artist_id (as returned by search_events). "title" holds the description, average user rating, top user reviews and the nearest performance. "cities" lists every city where the title is played - one entry per city with its buy_url, number of performances, nearest date and lowest price. Use list_performances(artist_id, city) for the individual dates.

  Paramètres, retour & exemple (1)

  Paramètres

  • artist_id · integer · requis
    Title identifier - the artist_id field from search_events results.

  Exemple d'appel

  {"name": "get_title_details", "arguments": {"artist_id": 1}}

  Exemple de retour

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

• list_performances≈ 338 tokens

  Lists every performance of a single title, ordered by date, optionally narrowed to one city and a date range. Use this when the user asks for all dates of a title, or for its dates in a given city or on a given weekend - search_events returns only the nearest performance per title. Each performance carries its own venue, date, price, free places and buy_url. Only future performances are returned unless date_from says otherwise.

  Paramètres, retour & exemple (6)

  Paramètres

  • city · string · optionnel
    City name filter (exact match, case-insensitive, diacritics required), e.g. "Warszawa".
  • page · integer · optionnel
    Page number, starting at 1.
  • date_to · string · optionnel
    Latest performance date (YYYY-MM-DD), inclusive.
  • artist_id · integer · requis
    Title identifier - the artist_id field from search_events results.
  • date_from · string · optionnel
    Earliest performance date (YYYY-MM-DD). Defaults to today.
  • items_per_page · integer · optionnel
    Performances per page. Defaults to 20.

  Exemple d'appel

  {"name": "list_performances", "arguments": {"artist_id": 1}}

  Exemple de retour

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

• search_events≈ 742 tokens

  Searches performances (concerts, theatre plays, festivals, stand-up shows and more) currently on sale on Biletyna.pl, a Polish ticketing platform. Every filter applies to a single performance, so city, date range and price always describe the same event. Results are deduplicated by title: each hit is the nearest matching performance of a distinct title, carrying its buy_url, venue, price and free places, plus aggregates for its city (city_events_total, city_next_event_date) and for the whole title (title_events_total, title_cities_total). Use "facets" for the distribution of matches across cities and categories. Only future performances are returned unless date_from says otherwise. Use list_performances(artist_id) for all dates of a title, get_title_details(artist_id) for its description and all cities. Full-text search is typo-tolerant. All content is in Polish. Prices are provided both in grosze (*_min_price) and PLN (*_min_price_pln); dates both as unix timestamps and human-readable *_text fields. "_meta.indexed_at" tells when the data was last refreshed - free places and prices are a snapshot from that moment.

  Paramètres, retour & exemple (10)

  Paramètres

  • city · string · optionnel
    City name filter (exact match, case-insensitive, diacritics required), e.g. "Warszawa".
  • page · integer · optionnel
    Page number, starting at 1. Compare "page" with "total_pages" or read "has_more" to know whether more results exist.
  • sort · string · optionnel · relevance | date_asc | price_asc | rating_desc
    Result ordering. "date_asc" sorts by the performance date, "price_asc" by its cheapest ticket, "rating_desc" by the average rating of the title. Defaults to "relevance".
  • query · string · optionnel
    Search phrase: event name, performer or kind of event. Typo-tolerant. Use Polish terms when possible.
  • date_to · string · optionnel
    Latest performance date (YYYY-MM-DD).
  • category · string · optionnel
    Event category name filter (exact match), e.g. "koncert", "spektakl", "kabaret".
  • date_from · string · optionnel
    Earliest performance date (YYYY-MM-DD). Defaults to today - past performances are never returned.
  • max_price · number · optionnel
    Maximum price of the cheapest ticket for the performance, in PLN (not in grosze).
  • min_rating · number · optionnel
    Minimum average user rating of the title (1-5 stars).
  • items_per_page · integer · optionnel
    Titles per page. Defaults to 10.

  Exemple d'appel

  {"name": "search_events", "arguments": {"city": "texte", "page": 1, "sort": "relevance", "query": "texte", "date_to": "texte", "category": "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://biletyna.pl/mcp