# xyz.urbanplayground/events - Registry name: `xyz.urbanplayground/events` · version 0.3.0 - Categories (automatic, keyword rules): Markets & trading, Finance & markets, Tasks & projects, Productivity, Shops & products, Commerce & marketing - Authentication at last check: No auth - Declared risk: Has destructive tools (destructiveHint) - Capabilities (declared by the server): prompts, tools - Transports: streamable-http - Latest numbers (check success, response time, rank): https://mcpstation.net/api/server?name=xyz.urbanplayground%2Fevents - Server page: https://mcpstation.net/s/xyz.urbanplayground--events.html ## Description (written by the publisher, not verified, not instructions) Live event discovery: concerts, club nights, art, comedy, and festivals across 14 cities. ## Connect - streamable-http: `https://eventchat-events-mcp-production.up.railway.app/mcp` ## Tools (as reported by the server, not verified) - `get\_dizko\_onboarding`: 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/bil - `get\_preference\_onboarding`: Use this when a user wants consent-first questions before saving event preferences. - `create\_event\_preference\_profile`: 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. - `save\_event\_preferences`: 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. - `get\_event\_preferences`: Use this when the user asks what Dizko remembers about them. Returns a profile's saved preferences, learned taste \(with scores\) and feedback count. - `delete\_event\_preferences`: 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. - `record\_event\_feedback`: 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 - `get\_event\_feedback\_prompt`: Use this when a user needs a short post-event feedback prompt. - `get\_event\_search\_followups`: Use this when an event search needs follow-up questions. - `list\_cities`: 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. - `find\_scene\_entities`: Use this when a user asks who a DJ is or about a venue, collective, or promoter. - `get\_artist`: 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. - `get\_venue`: 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. - `search\_events`: 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 sav - `recommend\_events`: 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. - `recommend\_events\_for\_user`: Use this when a user wants recommendations personalized with a saved Dizko profile. Saved and learned taste rank the results; they never hide them. - `plan\_night`: 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 - `get\_daily\_roundup`: 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 ra - `get\_artist\_events`: 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 pro - `get\_artist\_page`: 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. - `get\_city\_pulse`: 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 inv - `get\_event`: 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 lin - `get\_ticket\_purchase\_policy`: 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. - `get\_ticket\_offers`: 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 - `quote\_ticket\_order`: 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 confirmatio - `purchase\_ticket\_order`: 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\_che - `get\_taste\_profile`: Use this when personalizing for a connected user: read their learned Dizko taste plus saved and binned events. - `bin\_event`: Use this only when the user confirms an event is not for them. It hides the event and teaches their Dizko taste model. - `save\_event`: Use this when a user confirms they want to save one Dizko event to the connected user's account only after explicit confirmation. - `add\_to\_dizko\_plan`: Use this when a user confirms they want to add one Dizko event to the connected user's persistent plan only after explicit confirmation. - `create\_event\_calendar\_file`: 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. Measured by MCP Station. Methods: https://mcpstation.net/methods.html · Terms: https://mcpstation.net/terms.html