mcp server
events
Live event discovery: concerts, club nights, art, comedy, and festivals across 14 cities.
Description as published by the maintainer. Source
- version 0.3.0
- active
active — Registry entry last updated 2026-06-11.
What this server can do
21 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
create_event_calendar_file(status, event_id)- Use this when a user wants to add a Dizko event to their calendar after choosing or buying tickets. Required: event_id.
create_event_preference_profile(consent, preferences)- Use this when a user explicitly agrees to save event preferences and does not already have a Dizko preference profile. Required: consent.
delete_event_preferences(profile_id, confirm_delete, profile_secret)- Use this only when a user asks to delete their Dizko saved event preferences and feedback history. Required: profile_id, profile_secret, confirm_delete.
get_artist_events(city, artists, date_to, date_from, profile_id, profile_secret, limit_per_artist)- Use this when a user asks when specific DJs, performers, or comedians play next, or wants upcoming shows for the artists they follow. Pass artists explicitly, or pass only profile_id and profile_secret to use the artists saved in the profile's featuring list.
get_city_pulse(city, days, date_from, event_types)- Use this when a user asks what is hot, where the momentum is, or how busy a city's event scene looks over the coming days. Returns busiest nights, top venues, genre mix, and headline events from aggregate public inventory, every stat with evidence counts. Required: city.
get_daily_roundup(city, date, free, vibe, when, avoid, limit, genres, price_max, top_limit, profile_id, event_types, neighborhoods, section_limit, profile_secret)- Use this when a user wants a daily digest of what is happening in a city today, tomorrow, or on a specific date: top picks plus parties, live music, art, comedy, talks, and food sections from live Dizko inventory. Ideal for recurring morning briefings; pass profile_id and profile_secret so saved, learned, and per-day (day_filters) preferences shape the picks. Required: city.
get_event(id)- Use this when a user asks for details about a specific Dizko event id returned by search, recommendations, or a night plan. Required: id.
get_event_feedback_prompt(event_id, attended_at)- Use this when a user previously picked or attended a Dizko event and the assistant should ask a short post-event follow-up before recording feedback. Required: event_id.
get_event_preferences(profile_id, profile_secret)- Use this when a user with a Dizko profile wants to view saved event preferences or learned recommendation signals. Required: profile_id, profile_secret.
get_event_search_followups(city, free, vibe, when, avoid, limit, pride, query, venue, genres, offset, date_to, date_from, featuring, max_price, price_max, price_min, event_types, result_limit, neighborhoods)- Use this when a user asks for events tonight, this week, or this weekend and the assistant should ask only the missing event type, vibe, budget, area, or avoid-preference questions before searching.
get_preference_onboarding(profile_id)- Use this when a user wants personalized event recommendations and Dizko needs consent-first questions before saving event preferences.
get_ticket_offers(event_id)- Use this when a user wants ticket options for a specific Dizko event before quoting or buying. Required: event_id.
get_ticket_purchase_policy- Use this when a user asks whether agents can buy tickets autonomously or what purchase modes Dizko, Hermes, OpenClaw, or other providers can support.
plan_night(city, free, vibe, when, avoid, limit, pride, query, venue, genres, offset, date_to, date_from, featuring, max_price, price_max, price_min, profile_id, event_types, result_limit, neighborhoods, profile_secret)- Use this when a user wants a compact night-out plan with a primary live event option and fallback options from Dizko inventory.
purchase_ticket_order(quote_token, idempotency_key, confirmation_text, user_payment_profile_id)- Use this when the user has given explicit written confirmation for a locked ticket quote and the agent should either execute an integrated provider purchase or return the required external checkout handoff. Required: quote_token, confirmation_text.
quote_ticket_order(currency, event_id, offer_id, quantity, max_total, ticket_type, refund_terms)- Use this when a user has chosen an event and wants a locked ticket quote with quantity, max price, ticket type, and stop conditions before any purchase attempt. Required: event_id.
recommend_events(city, free, vibe, when, avoid, limit, pride, query, venue, genres, offset, date_to, date_from, featuring, max_price, price_max, price_min, event_types, result_limit, neighborhoods)- Use this when a user wants ranked event suggestions from live Dizko inventory based on the current request's taste, vibe, price, and avoid signals.
recommend_events_for_user(city, free, vibe, when, avoid, limit, query, venue, genres, date_to, date_from, featuring, max_price, nightlife, price_max, profile_id, event_types, result_limit, neighborhoods, profile_secret)- Use this when a user has a Dizko preference profile and wants personalized event recommendations for tonight, this week, this weekend, or another date range. Required: profile_id, profile_secret.
record_event_feedback(liked, notes, rating, event_id, profile_id, attended_at, profile_secret)- Use this when a user says whether they liked or disliked a specific event, provides a rating, or shares notes, so future Dizko recommendations can learn from that feedback. Required: profile_id, profile_secret, event_id.
save_event_preferences(mode, consent, profile_id, preferences, profile_secret)- Use this when a consenting user already has a Dizko profile and wants to add, update, merge, or replace saved event preferences. Required: profile_id, profile_secret, consent, preferences.
search_events(city, free, vibe, when, avoid, limit, pride, query, venue, genres, offset, date_to, date_from, featuring, max_price, price_max, price_min, event_types, result_limit, neighborhoods)- Use this when a user wants current events from live Dizko inventory using filters such as city, date, genre, vibe, venue, artist, neighborhood, or price.
Last successful function declaration observed on . Source: https://eventchat-events-mcp-production.up.railway.app/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://eventchat-events-mcp-production.up.railway.app/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 0.3.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-06-11 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-06-11 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 21 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | eventchat-events-mcp-production.up.railway.app | |
| mcp endpoint status | ok | The server listed 21 functions when asked. | as of probe | eventchat-events-mcp-production.up.railway.app |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json