events-search MCP server
pl.biletyna/events-searchbiletyna.plstreamable-httpv2.0.0Scanned
Event search at Biletyna.pl - Poland's top-rated ticket distributor, widest offer in all cities.
4 tools: 4 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the events-search MCP server can do
The events-search MCP server is published by biletyna.pl, a domain the MCP Registry verified. It has 4 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
1 tool brings in text other people can write (get_event_details).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 2.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Only reads 4Show 4 read-only tools
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.Reads text others writeNo findings
Why it is in this group
- The name "get_event_details" says "get": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "return" and "url": it reads web pages, which anyone can write.
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:17 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-11-25
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/mcpclaude mcp add --transport http events-search https://biletyna.pl/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as events-search. Review it before you use it.
Capability tags behind 1 rule
- mcp__events-search__get_event_details untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/pl.biletyna/events-search/verify?hash=cc47ba8c08b2d93248a818bf788f978f2fa4468be46388d314f269101827cade" | jq -e '.changed == false'Pinned hash cc47ba8c08b2, from Nov 19, 2026, 01:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/pl.biletyna/events-search/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/pl.biletyna/events-search)Source: MCP Registry. Synced Oct 21, 2026, 18:54 UTC.
events-search MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the events-search MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the events-search MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the events-search MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the events-search MCP server have?
- 4 tools: 4 read. list_performances, search_events, get_event_details and get_title_details.
Does the events-search MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the events-search MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the events-search MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.