mcpbeat

Events Search MCP Server

pl.biletyna/events-search
answering

Events Search is answering right now. Last checked 5 min ago. It exposes 4 tools.

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

Uptime history 40 hours of history
40 hours agonow
100.0%
Uptime 24h
91 of 91 checks
4
Tools
read from the server
506 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 5 min ago.

run in your terminal
claude mcp add events-search --transport http https://biletyna.pl/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "events-search": {
      "url": "https://biletyna.pl/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.events-search]
url = "https://biletyna.pl/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "events-search": {
      "url": "https://biletyna.pl/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "events-search": {
      "url": "https://biletyna.pl/mcp"
    }
  }
}

Available tools 4

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

event
get_event_details
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".
events
search_events
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.
performances
list_performances
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.
title
get_title_details
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.

Endpoints

URLTransportStateLatencyChecked
https://biletyna.pl/mcp streamable-http answering 483 ms 5 min ago

Events Search — questions

Answers built from our own checks of this server.

What can Events Search do?
It exposes 4 tools, read directly from the server on our last check. Among them: get_event_details, get_title_details, list_performances, search_events. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Events Search working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 506 ms. The bar chart above shows every period we have measured.
How do I connect Events Search?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Events Search need an API key?
No. Events Search completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 4 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Events Search?
It answers our handshake in 506 ms on average, which is faster than 22% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.