Events is an MCP server with 30 tools an agent can call, among them add_to_dizko_plan, bin_event, create_event_calendar_file. It answers at https://eventchat-events-mcp-production.up.railway.app/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 12 September 2026; the last check, on 24 October 2026, succeeded.
Live event discovery: concerts, club nights, art, comedy, and festivals across 14 cities.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
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. Inputs: event_id, confirmed, idempotency_key |
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. Inputs: event_id, confirmed, idempotency_key |
create_event_calendar_file | Use this when a user wants to add a Dizko event to their calendar after choosing or buying tickets. Inputs: event_id, status |
create_event_preference_profile | Use this when a user agrees to create a saved Dizko preference profile. Inputs: consent, preferences |
delete_event_preferences | Use this only when a user asks to delete their Dizko saved event preferences and feedback history. Inputs: profile_id, profile_secret, confirm_delete |
find_scene_entities | Use this when a user asks who a DJ is or about a venue, collective, or promoter. Inputs: kind, id, query, city, genre, date_from |
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. Inputs: id, query, city, date_from, date_to, limit |
get_artist_events | Use this when a user wants upcoming events for named artists or artists saved in a Dizko profile. Inputs: artists, city, date_from, date_to, limit_per_artist, profile_id |
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. Inputs: handle |
get_city_pulse | Use this when a user wants a city's busiest nights, top venues, genre mix, and headline events. Inputs: city, days, date_from, event_types |
get_daily_roundup | Use this when a user wants a daily city event digest. Inputs: city, date, when, profile_id, profile_secret, event_types |
get_event | Use this when a user asks for details about a Dizko event id. Inputs: id |
get_event_feedback_prompt | Use this when a user needs a short post-event feedback prompt. Inputs: event_id, attended_at |
get_event_preferences | Use this when a user wants to view saved and learned event preferences. Inputs: profile_id, profile_secret |
get_event_search_followups | Use this when an event search needs follow-up questions. Inputs: city, when, date_from, query, event_types, genres |
get_preference_onboarding | Use this when a user wants consent-first questions before saving event preferences. Inputs: profile_id |
get_taste_profile | Use this when personalizing for a connected user: read their learned Dizko taste plus saved and binned events. |
get_ticket_offers | Use this when a user wants ticket options for a specific Dizko event before quoting or buying. Inputs: event_id |
get_ticket_purchase_policy | Use this when a user asks how Dizko agents can buy tickets. |
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. Inputs: id, query, city, date_from, date_to, limit |
list_cities | Use this when a user asks about Dizko city coverage or freshness. |
plan_night | Use this when a user wants a primary night-out plan with fallback events. Inputs: city, when, date_from, date_to, query, event_types |
purchase_ticket_order | Use this when a user confirms a locked quote for purchase or checkout handoff. Inputs: quote_token, confirmation_text, user_payment_profile_id, idempotency_key |
quote_ticket_order | Use this when a user wants a locked ticket quote before purchase. Inputs: event_id, offer_id, quantity, ticket_type, max_total, currency |
recommend_events | Use this when a user wants live events ranked by taste, vibe, price, and exclusions. Inputs: city, when, date_from, date_to, query, event_types |
recommend_events_for_user | Use this when a user wants recommendations personalized with a saved Dizko profile. Inputs: profile_id, profile_secret, city, when, date_from, date_to |
record_event_feedback | Use this when a user wants Dizko to learn from their rating or notes about an event. Inputs: profile_id, profile_secret, event_id, liked, rating, notes |
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. Inputs: event_id, confirmed, idempotency_key |
save_event_preferences | Use this when a user wants to update a saved Dizko preference profile. Inputs: profile_id, profile_secret, consent, mode, preferences |
search_events | Use this when a user wants filtered live events. Inputs: city, when, date_from, date_to, query, event_types |
Every block below points at https://eventchat-events-mcp-production.up.railway.app/mcp. Pick your client and copy.
claude mcp add --transport http events https://eventchat-events-mcp-production.up.railway.app/mcp
{
"mcpServers": {
"events": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://eventchat-events-mcp-production.up.railway.app/mcp"]
}
}
}{
"mcpServers": {
"events": {
"url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
}
}
}{
"servers": {
"events": {
"type": "http",
"url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
}
}
}{
"context_servers": {
"events": {
"url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
}
}
}{
"mcpServers": {
"events": {
"serverUrl": "https://eventchat-events-mcp-production.up.railway.app/mcp"
}
}
}{
"mcpServers": {
"events": {
"url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
}
}
}name: Events
version: 0.0.1
schema: v1
mcpServers:
- name: Events
type: streamable-http
url: https://eventchat-events-mcp-production.up.railway.app/mcp{
"mcpServers": {
"events": {
"httpUrl": "https://eventchat-events-mcp-production.up.railway.app/mcp"
}
}
}{
"mcpServers": {
"events": {
"type": "http",
"url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
}
}
}{
"mcpServers": {
"events": {
"url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
}
}
}goose://extension?url=https%3A%2F%2Feventchat-events-mcp-production.up.railway.app%2Fmcp&type=streamable_http&id=events&name=Events
It answered our last check on 24 October 2026 in 266 ms. Over 6 checks since 12 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
30, as returned by the server's own tools/list on 23 September 2026: add_to_dizko_plan, bin_event, create_event_calendar_file, create_event_preference_profile, delete_event_preferences, find_scene_entities, get_artist, get_artist_events, and 22 more.
It answered our last check on 24 October 2026 in 266 ms. Over 6 checks since 12 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://eventchat-events-mcp-production.up.railway.app/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: xyz.urbanplayground. Endpoint host: eventchat-events-mcp-production.up.railway.app. ARD identifier: urn:air:xyz.urbanplayground:mcp:events.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.