Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

xyz.urbanplayground/events

REMOTE · EVENTCHAT-EVENTS-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS

Live event discovery: concerts, club nights, art, comedy, and festivals across 14 cities.

0 this week 77 Trust /100

Last scanned (2 hours ago)

Scores higher than 69% of remote servers

Unreachable for 1 day in a row. Last reached 4 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
  • Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 5 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: fail → unverified ▼ security
    • Authorization: fail → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
  • 22 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “get_dizko_onboarding” functional
  • 15 Oct 26 +1
    • Stability: pass → fail ▼ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_artist_events” rewrote its description, which is the text the model reads security
    • Tool “get_city_pulse” rewrote its description, which is the text the model reads security
    • Tool “get_daily_roundup” rewrote its description, which is the text the model reads security
    • Tool “get_event” rewrote its description, which is the text the model reads security
    • Tool “get_event_preferences” rewrote its description, which is the text the model reads security
    • Tool “get_ticket_offers” rewrote its description, which is the text the model reads security
    • Tool “get_ticket_purchase_policy” rewrote its description, which is the text the model reads security
    • Tool “list_cities” rewrote its description, which is the text the model reads security
    • Tool “plan_night” rewrote its description, which is the text the model reads security
    • Tool “purchase_ticket_order” rewrote its description, which is the text the model reads security
    • Tool “quote_ticket_order” rewrote its description, which is the text the model reads security
    • Tool “recommend_events” rewrote its description, which is the text the model reads security
    • Tool “recommend_events_for_user” rewrote its description, which is the text the model reads security
    • Tool “record_event_feedback” rewrote its description, which is the text the model reads security
    • Tool “save_event_preferences” rewrote its description, which is the text the model reads security
    • Tool “search_events” rewrote its description, which is the text the model reads security
    • Tool “create_event_calendar_file” rewrote its description, which is the text the model reads security
    • Tool “create_event_preference_profile” rewrote its description, which is the text the model reads security
    • Tool “delete_event_preferences” rewrote its description, which is the text the model reads security
    • Tool “save_event_preferences” is now declared destructive security
    • Schema quality: pass → fail ▼ functional
    • “get_artist_events” changed the type of “limit_per_artist”: number → integer ▼ functional
    • “get_city_pulse” changed the type of “days”: number → integer ▼ functional
    • “get_daily_roundup” changed the type of “limit”: number → integer ▼ functional
    • “get_daily_roundup” changed the type of “section_limit”: number → integer ▼ functional
    • “get_daily_roundup” changed the type of “top_limit”: number → integer ▼ functional
    • “plan_night” changed the type of “result_limit”: number → integer ▼ functional
    • “quote_ticket_order” changed the type of “quantity”: number → integer ▼ functional
    • “recommend_events” changed the type of “limit”: number → integer ▼ functional
    • “recommend_events” changed the type of “result_limit”: number → integer ▼ functional
    • “recommend_events_for_user” changed the type of “limit”: number → integer ▼ functional
    • “recommend_events_for_user” changed the type of “result_limit”: number → integer ▼ functional
    • “search_events” changed the type of “limit”: number → integer ▼ functional
    • “search_events” changed the type of “offset”: number → integer ▼ functional
    • Tool coverage: 0% → 56% ▲ functional
    • The server now declares the “prompts” capability functional
    • First check of Schema quality: 100 functional
    • New prompt “dizko_onboarding” functional
    • New prompt “dizko_post_event_feedback” functional
    • New prompt “dizko_search_followups” functional
    • New prompt “dizko_ticket_policy” functional
    • Server version: 0.8.0 → 0.9.0 functional
    • “get_artist_events” added an optional parameter “fields” cosmetic
    • “get_daily_roundup” added an optional parameter “compact” cosmetic
    • “get_daily_roundup” added an optional parameter “fields” cosmetic
    • “plan_night” added an optional parameter “fields” cosmetic
    • “purchase_ticket_order” added an optional parameter “add_to_calendar” cosmetic
    • “purchase_ticket_order” added an optional parameter “delivery_email” cosmetic
    • “quote_ticket_order” added an optional parameter “add_to_calendar” cosmetic
    • “quote_ticket_order” added an optional parameter “delivery_email” cosmetic
    • “recommend_events” added an optional parameter “fields” cosmetic
    • “recommend_events” added an optional parameter “origin_lat” cosmetic
    • “recommend_events” added an optional parameter “origin_lng” cosmetic
    • “recommend_events” added an optional parameter “profile_id” cosmetic
    • “recommend_events” added an optional parameter “profile_secret” cosmetic
    • “recommend_events” added an optional parameter “sort_by” cosmetic
    • “search_events” added an optional parameter “fields” cosmetic
    • “search_events” added an optional parameter “origin_lat” cosmetic
    • “search_events” added an optional parameter “origin_lng” cosmetic
    • “search_events” added an optional parameter “profile_id” cosmetic
    • “search_events” added an optional parameter “profile_secret” cosmetic
    • “search_events” added an optional parameter “rank” cosmetic
    • “search_events” added an optional parameter “sort_by” cosmetic
    • “get_artist_events” reworded the description of “artists” cosmetic
    • “get_artist_events” reworded the description of “city” cosmetic
    • “get_artist_events” reworded the description of “date_from” cosmetic
    • “get_artist_events” reworded the description of “date_to” cosmetic
    • “get_artist_events” reworded the description of “profile_id” cosmetic
    • “get_city_pulse” reworded the description of “city” cosmetic
    • “get_city_pulse” reworded the description of “date_from” cosmetic
    • “get_city_pulse” reworded the description of “days” cosmetic
    • “get_city_pulse” reworded the description of “event_types” cosmetic
    • “get_daily_roundup” reworded the description of “avoid” cosmetic
    • “get_daily_roundup” reworded the description of “city” cosmetic
    • “get_daily_roundup” reworded the description of “date” cosmetic
    • “get_daily_roundup” reworded the description of “event_types” cosmetic
    • “get_daily_roundup” reworded the description of “genres” cosmetic
    • “get_daily_roundup” reworded the description of “limit” cosmetic
    • “get_daily_roundup” reworded the description of “profile_id” cosmetic
    • “get_daily_roundup” reworded the description of “vibe” cosmetic
    • “get_daily_roundup” reworded the description of “when” cosmetic
    • “get_event” reworded the description of “id” cosmetic
    • “get_event_preferences” reworded the description of “profile_id” cosmetic
    • “get_event_preferences” reworded the description of “profile_secret” cosmetic
    • “get_preference_onboarding” reworded the description of “profile_id” cosmetic
    • “get_ticket_offers” reworded the description of “event_id” cosmetic
    • “get_venue” reworded the description of “id” cosmetic
    • “get_venue” reworded the description of “query” cosmetic
    • “plan_night” reworded the description of “avoid” cosmetic
    • “plan_night” reworded the description of “city” cosmetic
    • “plan_night” reworded the description of “date_from” cosmetic
    • “plan_night” reworded the description of “date_to” cosmetic
    • “plan_night” reworded the description of “max_price” cosmetic
    • “plan_night” reworded the description of “price_max” cosmetic
    • “plan_night” reworded the description of “price_min” cosmetic
    • “plan_night” reworded the description of “pride” cosmetic
    • “plan_night” reworded the description of “profile_id” cosmetic
    • “plan_night” reworded the description of “promoter” cosmetic
    • “plan_night” reworded the description of “query” cosmetic
    • “plan_night” reworded the description of “result_limit” cosmetic
    • “plan_night” reworded the description of “when” cosmetic
    • “purchase_ticket_order” reworded the description of “confirmation_text” cosmetic
    • “purchase_ticket_order” reworded the description of “quote_token” cosmetic
    • “purchase_ticket_order” reworded the description of “user_payment_profile_id” cosmetic
    • “quote_ticket_order” reworded the description of “currency” cosmetic
    • “quote_ticket_order” reworded the description of “max_total” cosmetic
    • “quote_ticket_order” reworded the description of “offer_id” cosmetic
    • “quote_ticket_order” reworded the description of “refund_terms” cosmetic
    • “quote_ticket_order” reworded the description of “ticket_type” cosmetic
    • “recommend_events” reworded the description of “avoid” cosmetic
    • “recommend_events” reworded the description of “city” cosmetic
    • “recommend_events” reworded the description of “date_from” cosmetic
    • “recommend_events” reworded the description of “date_to” cosmetic
    • “recommend_events” reworded the description of “event_types” cosmetic
    • “recommend_events” reworded the description of “featuring” cosmetic
    • “recommend_events” reworded the description of “free” cosmetic
    • “recommend_events” reworded the description of “genres” cosmetic
    • “recommend_events” reworded the description of “limit” cosmetic
    • “recommend_events” reworded the description of “max_price” cosmetic
    • “recommend_events” reworded the description of “neighborhoods” cosmetic
    • “recommend_events” reworded the description of “price_max” cosmetic
    • “recommend_events” reworded the description of “price_min” cosmetic
    • “recommend_events” reworded the description of “pride” cosmetic
    • “recommend_events” reworded the description of “promoter” cosmetic
    • “recommend_events” reworded the description of “query” cosmetic
    • “recommend_events” reworded the description of “result_limit” cosmetic
    • “recommend_events” reworded the description of “venue” cosmetic
    • “recommend_events” reworded the description of “vibe” cosmetic
    • “recommend_events” reworded the description of “when” cosmetic
    • “recommend_events_for_user” reworded the description of “limit” cosmetic
    • “recommend_events_for_user” reworded the description of “profile_secret” cosmetic
    • “recommend_events_for_user” reworded the description of “result_limit” cosmetic
    • “record_event_feedback” reworded the description of “attended_at” cosmetic
    • “record_event_feedback” reworded the description of “event_id” cosmetic
    • “record_event_feedback” reworded the description of “notes” cosmetic
    • “save_event_preferences” reworded the description of “consent” cosmetic
    • “save_event_preferences” reworded the description of “mode” cosmetic
    • “search_events” reworded the description of “avoid” cosmetic
    • “search_events” reworded the description of “city” cosmetic
    • “search_events” reworded the description of “cursor” cosmetic
    • “search_events” reworded the description of “date_from” cosmetic
    • “search_events” reworded the description of “date_to” cosmetic
    • “search_events” reworded the description of “event_types” cosmetic
    • “search_events” reworded the description of “featuring” cosmetic
    • “search_events” reworded the description of “free” cosmetic
    • “search_events” reworded the description of “genres” cosmetic
    • “search_events” reworded the description of “limit” cosmetic
    • “search_events” reworded the description of “max_price” cosmetic
    • “search_events” reworded the description of “neighborhoods” cosmetic
    • “search_events” reworded the description of “offset” cosmetic
    • “search_events” reworded the description of “price_max” cosmetic
    • “search_events” reworded the description of “price_min” cosmetic
    • “search_events” reworded the description of “pride” cosmetic
    • “search_events” reworded the description of “promoter” cosmetic
    • “search_events” reworded the description of “query” cosmetic
    • “search_events” reworded the description of “venue” cosmetic
    • “search_events” reworded the description of “vibe” cosmetic
    • “search_events” reworded the description of “when” cosmetic
    • “get_event_feedback_prompt” reworded the description of “attended_at” cosmetic
    • “create_event_preference_profile” reworded the description of “consent” cosmetic
    • “create_event_preference_profile” reworded the description of “preferences” cosmetic
    • “delete_event_preferences” reworded the description of “confirm_delete” cosmetic
    • “get_artist” reworded the description of “id” cosmetic
    • “get_artist” reworded the description of “query” cosmetic
    • “plan_night” dropped the optional parameter “cursor” cosmetic
    • “plan_night” dropped the optional parameter “limit” cosmetic
    • “plan_night” dropped the optional parameter “offset” cosmetic
    • “purchase_ticket_order” dropped the optional parameter “idempotency_key” cosmetic
    • “recommend_events” dropped the optional parameter “cursor” cosmetic
    • “recommend_events” dropped the optional parameter “offset” cosmetic
    • “search_events” dropped the optional parameter “result_limit” cosmetic
  • 30 Sept 26 0
    • Stability: fail → pass ▲ security
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 21 Sept 26 0
    • HSTS header: fail → pass ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “bin_event”, which the server declares destructive security
    • New tool “get_taste_profile” functional
  • 20 Sept 26 0

    First indexed and scored.

    • Schema quality: 2493 → 2809 ▼ functional
    • “plan_night” added an optional parameter “cursor” cosmetic
    • “recommend_events” added an optional parameter “cursor” cosmetic
    • “search_events” added an optional parameter “cursor” cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://eventchat-events-mcp-production.up.railway.app/mcp

TLS unreached
DNSSEC insecure

Validation of eventchat-events-mcp-production.up.railway.app. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
app. present 23684 8 Verified
railway.app. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://eventchat-events-mcp-production.up.railway.app/mcp Unreachable
http (plaintext) http://eventchat-events-mcp-production.up.railway.app/mcp HTTPS enforced
MCP tools · 31 exposed · ~5,248 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
add_to_dizko_plan ~62

Use this when a user confirms they want to add one Dizko event to the connected user's persistent plan only after explicit confirmation.

NameTypeReqDescription
confirmedbooleanyes–
event_idstringyes–
idempotency_keystringyes–

No output schema declared.

No examples provided.

bin_event ~59

Use this only when the user confirms an event is not for them. It hides the event and teaches their Dizko taste model.

NameTypeReqDescription
confirmedbooleanyes–
event_idstringyes–
idempotency_keystringyes–

No output schema declared.

No examples provided.

create_event_calendar_file ~77

Use this when the user wants one event in Apple Calendar, Google Calendar or Outlook as a file. Builds an importable .ics entry (local time, venue address, lineup, set times, links); the per-event calendar_url is the one-click alternative.

NameTypeReqDescription
event_idstringyes–
statusstring––

No output schema declared.

No examples provided.

create_event_preference_profile ~122

Use this only when the user has explicitly agreed to let Dizko save their taste. Creates a private preference profile and returns profile_id and a one-time profile_secret to keep for future personalized calls. Ask the onboarding questions (get_preference_onboarding) first; consent must be true.

NameTypeReqDescription
consentbooleanyesMust be true only after the user agreed to save preferences.
preferences––Initial taste: cities, event_types, genres, vibe, neighborhoods, venues, promoters, featuring, avoid, max_price, free, nightlife, day_filters.

No output schema declared.

No examples provided.

delete_event_preferences ~80

Use this only when the user confirms they want their Dizko connector data deleted. Deletes a profile's saved preferences and feedback history; confirm_delete must be true. Scoped to Dizko only.

NameTypeReqDescription
confirm_deletebooleanyesMust be true only after the user confirms deletion.
profile_idstringyes–
profile_secretstringyes–

No output schema declared.

No examples provided.

find_scene_entities ~87

Use this when a user asks who a DJ is or about a venue, collective, or promoter.

NameTypeReqDescription
citystring––
date_fromstring––
date_tostring––
genrestring––
idstring––
kindstringyes–
limitnumber––
querystring––

No output schema declared.

No examples provided.

get_artist ~104

Use this when a user wants a canonical artist profile, graph context, published links, and upcoming events. Pass an id or a name query; this does not enumerate the artist catalog.

NameTypeReqDescription
citystring––
date_fromstring––
date_tostring––
idstring–Canonical Dizko entity id.
limitnumber––
querystring–Artist or venue name when the id is unknown.

No output schema declared.

No examples provided.

get_artist_events ~198

Use this when a user asks when a DJ, performer or comedian plays next, or whether they play in a city this month. Returns upcoming shows grouped by artist for up to 8 names, deduplicated across sources and date-ordered, optionally scoped to a city. With a profile and no artists named, tracks the profile's saved featuring list.

NameTypeReqDescription
artistsarray–Artist names to look up (max 8 per call).
citystring–Optional city to scope the search; omit for all cities.
date_fromstring–Inclusive start date, YYYY-MM-DD. Defaults to today.
date_tostring–Optional inclusive end date, YYYY-MM-DD.
fieldsarray––
limit_per_artistinteger––
profile_idstring–Optional profile id; with no artists given, the saved featuring list is used.
profile_secretstring––

No output schema declared.

No examples provided.

get_artist_page ~48

Use this when a user wants an artist's Dizko page or a specific published mix or set. Returns the page embeds with stable block ids for deep links.

NameTypeReqDescription
handlestringyes–

No output schema declared.

No examples provided.

get_city_pulse ~142

Use this when a user asks what's hot, how busy a city is this week, or about scene trends. Returns an aggregate read over the coming days: busiest nights (city-local dates), top venues (attendance-weighted), genre mix, headline events and free-event count, every stat with evidence counts. Public inventory only.

NameTypeReqDescription
citystringyesCity name or slug.
date_fromstring–Inclusive start date, YYYY-MM-DD. Defaults to today in the city.
daysinteger–Window length in days from date_from (1-14).
event_typesarray–Optional event-type filter, for example party.

No output schema declared.

No examples provided.

get_daily_roundup ~311

Use this when a user asks what's happening today or tomorrow, or for a morning briefing or scheduled check-in. Returns a one-day digest for a city: top picks plus sections for parties, live music, art, comedy and theatre, talks, food, and more. With a profile, saved, learned and per-weekday taste rank the picks. Pass compact=true for a short push-style digest.

NameTypeReqDescription
avoidarray–Ranking penalties.
citystringyesCity name or slug.
compactboolean–Short digest: title, when, venue, price and link only; 3 picks, up to 4 sections of 3.
datestring–Target day, YYYY-MM-DD (city-local). Defaults to today.
event_typesarray–Hard filter.
fieldsarray––
freeboolean––
genresarray–Hard filter.
limitinteger–How many of the day's events to fetch and rank.
neighborhoodsarray––
price_maxnumber––
profile_idstring–Optional profile id; pass with profile_secret to personalize.
profile_secretstring––
section_limitinteger––
top_limitinteger––
vibearray–Hard filter.
whenstring–Single-day preset: today, tonight, tomorrow, or a weekday name. Ranges are rejected; use search_events for those.

No output schema declared.

No examples provided.

get_dizko_onboarding ~166

Use this when someone wants optional Dizko setup for event discovery or for DJs, artists, musicians, venues, collectives and promoters. With SoundCloud, checks exact database matches and returns claim/create guidance, real published page examples, site-builder benefits and website pricing/signup/billing links. Read-only: never claims, publishes or charges. Use once at setup or when the user asks about their own page; do not interrupt event searches.

NameTypeReqDescription
audiencestring––
citystring–City for a venue, collective or promoter search.
namestring–Artist or organization name when there is no SoundCloud; returns candidates to confirm.
soundcloudstring–User-provided SoundCloud profile URL or handle for an exact database lookup.

No output schema declared.

No examples provided.

get_event ~88

Use this only when the user gives an event id, or wants extra detail on an event not in the current results; search results already contain what the template needs. Returns full detail for one event: local times, venue and address, price, lineup, set times, artist socials, image, coordinates and links.

NameTypeReqDescription
idstringyesEvent id (UUID) from any Dizko result.

No output schema declared.

No examples provided.

get_event_feedback_prompt ~54

Use this when a user needs a short post-event feedback prompt.

NameTypeReqDescription
attended_atstring–Optional ISO date/time or YYYY-MM-DD the user attended or planned to attend.
event_idstringyes–

No output schema declared.

No examples provided.

get_event_preferences ~73

Use this when the user asks what Dizko remembers about them. Returns a profile's saved preferences, learned taste (with scores) and feedback count.

NameTypeReqDescription
profile_idstringyesProfile id returned by create_event_preference_profile.
profile_secretstringyesPrivate profile secret returned when the profile was created.

No output schema declared.

No examples provided.

get_event_search_followups ~117

Use this when an event search needs follow-up questions.

NameTypeReqDescription
avoidarray––
citystring––
date_fromstring––
event_typesarray––
freeboolean––
genresarray––
max_pricenumber––
neighborhoodsarray––
price_maxnumber––
querystring––
venuestring––
vibearray––
whenstring––

No output schema declared.

No examples provided.

get_preference_onboarding ~40

Use this when a user wants consent-first questions before saving event preferences.

NameTypeReqDescription
profile_idstring–Stable user/profile id if already known.

No output schema declared.

No examples provided.

get_taste_profile ~33

Use this when personalizing for a connected user: read their learned Dizko taste plus saved and binned events.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_ticket_offers ~89

Use this when the user wants tickets for one event, before quoting. Returns ticket options: provider, checkout link, estimated price, whether entry is free, whether autonomous purchase is supported, next_step, and the purchase policy. On the hosted connector Dizko does not buy tickets: next_step is hand_off_to_checkout.

NameTypeReqDescription
event_idstringyesEvent id from any Dizko result.

No output schema declared.

No examples provided.

get_ticket_purchase_policy ~42

Use this when a user asks how Dizko agents can buy tickets: signed quote, written confirmation, then a hand off to checkout unless a provider is integrated.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_venue ~102

Use this when a user wants a canonical venue profile, graph context, and upcoming events. Pass an id or a name query; this does not enumerate the venue catalog.

NameTypeReqDescription
citystring––
date_fromstring––
date_tostring––
idstring–Canonical Dizko entity id.
limitnumber––
querystring–Artist or venue name when the id is unknown.

No output schema declared.

No examples provided.

list_cities ~62

Use this when a user asks where Dizko works, whether a city is covered, or how fresh the data is. Returns every city with status (live, unlocking, early), event count, timezone and freshness. Unlocking and early cities are searchable but thin.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_night ~394

Use this when the user wants a night plan with backups rather than a list. Returns, for one city and date, a primary event plus a nearby fallback (best taste fit within 6 km), a later-starting fallback, and alternates. Accepts the same filters as search_events and an optional profile for saved taste. An empty plan carries the same `no_results` guidance as search.

NameTypeReqDescription
avoidarray–Ranking penalties.
citystring–City name or slug.
date_fromstring–Inclusive start date, YYYY-MM-DD.
date_tostring–Inclusive end date, YYYY-MM-DD.
event_typesarray––
featuringstring––
fieldsarray––
freeboolean––
genresarray––
max_pricenumber–Soft budget for ranking.
neighborhoodsarray––
price_maxnumber–Hard price cap.
price_minnumber–Hard filter: minimum ticket price.
prideboolean–Only Pride / LGBTQ+ flagged events.
profile_idstring–Optional profile id; pass with profile_secret.
profile_secretstring––
promoterstring–Promoter slug or display name.
querystring–Free-text intent, for example 'concert first then a late party'.
result_limitinteger–Plan size including the primary (1-6).
venuestring––
vibearray––
whenstring–Timeframe preset resolved in the city's local timezone: today, tonight, tomorrow, weekend, next weekend, week, next week, month, monday, tuesday, wednesday, thursday, friday, saturday, sunday, any, o…

No output schema declared.

No examples provided.

purchase_ticket_order ~195

Use this only when the user has confirmed a quote in writing (the confirmation must say buy or purchase and repeat the quantity and max total; the server rejects it otherwise). Without an integrated purchase provider this buys nothing: it hands off to checkout, returning status requires_external_checkout and the checkout_url where the user pays on the provider's site. Never claim a purchase unless status is purchased. Each quote_token can be submitted once: a repeat returns status quote_already_used and must never be retried.

NameTypeReqDescription
add_to_calendarboolean––
confirmation_textstringyesThe user's own words confirming the purchase, including buy/purchase, the quantity and the max total.
delivery_emailstring––
quote_tokenstringyesThe signed quote_token from quote_ticket_order, unchanged.
user_payment_profile_idstring–Provider-specific saved payment profile id, when an integrated provider supports autonomous purchase.

No output schema declared.

No examples provided.

quote_ticket_order ~215

Use this when the user has chosen a ticket offer, quantity and constraints. Creates a signed, time-limited quote (quantity, ticket type, max total, currency, refund terms, delivery email, stop conditions) and returns a quote_token to pass unchanged to purchase_ticket_order plus the exact confirmation text to ask the user for. Without an integrated provider it only prepares a hand off to checkout.

NameTypeReqDescription
add_to_calendarboolean––
currencystring–Currency for max_total, for example EUR.
delivery_emailstring–Where tickets should be delivered, when a provider supports it.
event_idstringyes–
max_totalnumber–Maximum all-in total the user authorizes.
offer_idstring–Optional offer_id from get_ticket_offers.
quantityinteger––
refund_termsstring–Minimum refund/transfer terms the user accepts.
ticket_typestring–For example GA, balcony, seated, VIP, or best available.

No output schema declared.

No examples provided.

recommend_events ~765

Use this when a user wants live events ranked by taste, vibe, price, and exclusions. Every result carries recommendation_reasons. Request filters (genres, vibe, event_types, price_max, venue, featuring) are hard filters; avoid and max_price only rank.

NameTypeReqDescription
avoidarray–Ranking penalties, for example mainstream, huge crowds, expensive tickets, or any word to avoid in titles and tags.
citystring–City name or slug, for example berlin, 'new york', NYC, LA, 'São Paulo'. Required unless query, venue, featuring or promoter is given.
date_fromstring–Inclusive start date, YYYY-MM-DD (city-local). Overrides `when`.
date_tostring–Inclusive end date, YYYY-MM-DD (city-local).
event_typesarray–Hard filter. Vocabulary: party, live music, concert, art, museum, comedy, theatre, talk, meetup, food, festival, wellness, sports.
featuringstring–Hard filter on an artist or performer on the lineup.
fieldsarray–Extra per-event fields: description (long form), coordinates, socials, promoters (full objects). Images and source are always included. Omit for the compact default.
freeboolean–Only free-entry events.
genresarray–Hard filter, for example techno, house, jazz, hip hop, ambient.
limitinteger–Same as result_limit; result_limit wins when both are given.
max_pricenumber–Soft budget used for ranking (over-budget events drop, they are not hidden). Use price_max for a hard cap.
neighborhoodsarray–Hard filter on neighborhood names, for example kreuzberg, bushwick.
origin_latnumber–Latitude for sort_by=distance ('near me'). Only pass coordinates the user gave you.
origin_lngnumber–Longitude for sort_by=distance.
price_maxnumber–Hard filter: maximum ticket price. Events without a listed price are excluded when set.
price_minnumber–Hard filter: minimum ticket price.
prideboolean–Only Pride / LGBTQ+ flagged events.
profile_idstring–Optional Dizko preference profile id; pass with profile_secret to rank by saved and learned taste as well. rank then defaults to taste.
profile_secretstring–Private profile secret returned when the profile was created.
promoterstring–Hard filter on promoter slug or display name.
querystring–Free-text search, hybrid-ranked by the live API (exact > substring > fuzzy > semantic). Pass soft intent directly, for example 'dark queer warehouse rave' or 'ambient listening bar', or an artist or…
result_limitinteger–How many ranked events to return (1-50, default 10).
sort_bystring–soonest (chronological), popular (default for multi-day ranges), cost, event_type, or distance (needs origin_lat/origin_lng). Single-day requests default to soonest.
venuestring–Hard filter on venue name (text match), for example Berghain.
vibearray–Hard filter, for example underground, intimate, high-energy, queer-friendly, outdoors, free-entry.
whenstring–Timeframe preset resolved in the city's local timezone: today, tonight, tomorrow, weekend, next weekend, week, next week, month, monday, tuesday, wednesday, thursday, friday, saturday, sunday, any, o…

No output schema declared.

No examples provided.

recommend_events_for_user ~221

Use this when a user wants recommendations personalized with a saved Dizko profile. Saved and learned taste rank the results; they never hide them.

NameTypeReqDescription
avoidarray––
citystring––
date_fromstring––
date_tostring––
event_typesarray––
featuringstring––
freeboolean––
genresarray––
limitinteger–Same as result_limit; result_limit wins when both are given.
max_pricenumber––
neighborhoodsarray––
nightlifeboolean––
price_maxnumber––
profile_idstringyes–
profile_secretstringyesPrivate profile secret returned when the profile was created.
querystring––
result_limitinteger–How many ranked events to return (1-50, default 10).
venuestring––
vibearray––
whenstring––

No output schema declared.

No examples provided.

record_event_feedback ~163

Use this only when the user has answered post-event questions (get_event_feedback_prompt has them). Stores liked, a 1-5 rating or notes for a profile and updates learned taste: a like promotes the event's genres, vibe and venue; a dislike marks the venue and promoter, and only penalizes genres when the notes blame the music.

NameTypeReqDescription
attended_atstring–ISO date/time or YYYY-MM-DD.
event_idstringyesEvent id from any Dizko result.
likedboolean––
notesstring–Free text; mentions of music, crowd, venue, price or timing become learned signals.
profile_idstringyes–
profile_secretstringyes–
ratingnumber––

No output schema declared.

No examples provided.

save_event ~57

Use this when a user confirms they want to save one Dizko event to the connected user's account only after explicit confirmation.

NameTypeReqDescription
confirmedbooleanyes–
event_idstringyes–
idempotency_keystringyes–

No output schema declared.

No examples provided.

save_event_preferences ~122

Use this when the user shares new taste for an existing profile: genres, favorite artists to track (featuring), venues, budget, or per-weekday rules (day_filters). Adds to (mode merge) or replaces saved preferences. Needs profile_id, profile_secret and consent=true.

NameTypeReqDescription
consentbooleanyesMust be true only after the user agreed to save preferences.
modestring–merge adds to existing lists; replace overwrites everything.
preferences–yes–
profile_idstringyes–
profile_secretstringyes–

No output schema declared.

No examples provided.

search_events ~960

Use this when a user asks what's on and names a city, a venue, an artist, or a timeframe. Returns up to `limit` live events with local times (`when`), venue and address, price, genres, vibe, lineup, set times and links; `count` is the total matching. Pass profile_id and profile_secret to rank by saved taste (saved taste ranks results, it never filters them). Filters you pass (genres, vibe, event_types, price_max, venue, featuring) are hard filters; `avoid` and `max_price` are ranking hints. When nothing matches, the result carries `no_results` with how many events exist without the filters and ordered `suggested_relaxations` you can retry directly.

NameTypeReqDescription
avoidarray–Ranking penalties, for example mainstream, huge crowds, expensive tickets, or any word to avoid in titles and tags.
citystring–City name or slug, for example berlin, 'new york', NYC, LA, 'São Paulo'. Required unless query, venue, featuring or promoter is given.
cursorstring–Opaque next_cursor returned by a prior search_events call. Takes precedence over offset.
date_fromstring–Inclusive start date, YYYY-MM-DD (city-local). Overrides `when`.
date_tostring–Inclusive end date, YYYY-MM-DD (city-local).
event_typesarray–Hard filter. Vocabulary: party, live music, concert, art, museum, comedy, theatre, talk, meetup, food, festival, wellness, sports.
featuringstring–Hard filter on an artist or performer on the lineup.
fieldsarray–Extra per-event fields: description (long form), coordinates, socials, promoters (full objects). Images and source are always included. Omit for the compact default.
freeboolean–Only free-entry events.
genresarray–Hard filter, for example techno, house, jazz, hip hop, ambient.
limitinteger–Events to return per page (1-200, default 12; rank: taste returns at most 50). count is the total available; page with next_cursor.
max_pricenumber–Soft budget used for ranking (over-budget events drop, they are not hidden). Use price_max for a hard cap.
neighborhoodsarray–Hard filter on neighborhood names, for example kreuzberg, bushwick.
offsetinteger–Legacy pagination offset; prefer cursor. Pass back next_offset from the previous page, never a number you computed. Applies to relevance ranking only; taste ranking scores one window and ignores it.
origin_latnumber–Latitude for sort_by=distance ('near me'). Only pass coordinates the user gave you.
origin_lngnumber–Longitude for sort_by=distance.
price_maxnumber–Hard filter: maximum ticket price. Events without a listed price are excluded when set.
price_minnumber–Hard filter: minimum ticket price.
prideboolean–Only Pride / LGBTQ+ flagged events.
profile_idstring–Optional Dizko preference profile id; pass with profile_secret to rank by saved and learned taste as well. rank then defaults to taste.
profile_secretstring–Private profile secret returned when the profile was created.
promoterstring–Hard filter on promoter slug or display name.
querystring–Free-text search, hybrid-ranked by the live API (exact > substring > fuzzy > semantic). Pass soft intent directly, for example 'dark queer warehouse rave' or 'ambient listening bar', or an artist or…
rankstring–relevance (default) keeps the API order; taste ranks the page by the genres, vibe, avoid and budget in this request.
sort_bystring–soonest (chronological), popular (default for multi-day ranges), cost, event_type, or distance (needs origin_lat/origin_lng). Single-day requests default to soonest.
venuestring–Hard filter on venue name (text match), for example Berghain.
vibearray–Hard filter, for example underground, intimate, high-energy, queer-friendly, outdoors, free-entry.
whenstring–Timeframe preset resolved in the city's local timezone: today, tonight, tomorrow, weekend, next weekend, week, next week, month, monday, tuesday, wednesday, thursday, friday, saturday, sunday, any, o…

No output schema declared.

No examples provided.

Install

How do I install the xyz.urbanplayground/events MCP server?

xyz.urbanplayground/events is a hosted endpoint at https://eventchat-events-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · eventchat-events-mcp-production.up.railway.app

# add to Claude Code
claude mcp add --transport http xyz-urbanplayground-events 'https://eventchat-events-mcp-production.up.railway.app/mcp'
Common questions

What is the xyz.urbanplayground/events MCP server?

xyz.urbanplayground/events is an MCP server listed in the public MCP registry as xyz.urbanplayground/events. Live event discovery: concerts, club nights, art, comedy, and festivals across 14 cities. This page covers its hosted endpoint (https://eventchat-events-mcp-production.up.railway.app/mcp).

Is the xyz.urbanplayground/events MCP server safe to use?

xyz.urbanplayground/events scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the xyz.urbanplayground/events MCP server expose?

xyz.urbanplayground/events exposes 31 tools: get_dizko_onboarding, get_preference_onboarding, create_event_preference_profile, save_event_preferences, get_event_preferences, and 26 more. Their descriptions and schemas cost roughly 5,248 tokens of context every time the server is loaded.

Does the xyz.urbanplayground/events MCP server require authentication?

Its publisher declares no required credentials for xyz.urbanplayground/events. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the xyz.urbanplayground/events MCP server still maintained?

xyz.urbanplayground/events is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.