Skip to content

pl.biletyna/events-search

by biletyna.pl · remote · no sign-in to list tools · v2.0.0 · published by pl.biletyna

Event search at Biletyna.pl - Poland's top-rated ticket distributor, widest offer in all cities.

Read only
CompareRegistry entry

4 tools: 4 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http events-search https://biletyna.pl/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

4 tools

Only reads 4Claude Code: allow
  • get_event_detailsReturns 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.No findings

    Why it is in this group

    • The name "get_event_details" says "get": a word for reading.
    Description, as the server wrote it
    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".
  • get_title_detailsReturns a single title currently on sale on Biletyna.pl, identified by artist_id (as returned by search_events).No findings

    Why it is in this group

    • The name "get_title_details" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_performancesLists every performance of a single title, ordered by date, optionally narrowed to one city and a date range.No findings

    Why it is in this group

    • The name "list_performances" says "list": a word for reading.
    Description, as the server wrote it
    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.
  • search_eventsSearches performances (concerts, theatre plays, festivals, stand-up shows and more) currently on sale on Biletyna.pl, a Polish ticketing platform.No findings

    Why it is in this group

    • The name "search_events" says "search": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 2.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http events-search https://biletyna.pl/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__events-search__list_performances",
      "mcp__events-search__search_events",
      "mcp__events-search__get_event_details",
      "mcp__events-search__get_title_details"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as events-search. Review it before you use it.