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 · SCANNED SEP 20

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

0 this week 67 Trust /100
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 Security57
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2809 tokens (~100/item across 28 items; 28 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 21 breaking changes, 0 auth/transport breaks, 7 additions. See how to fix → Fail
Tool Coverage67
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
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'
// .cursor/mcp.json
{
  "mcpServers": {
    "xyz-urbanplayground-events": {
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "xyz-urbanplayground-events": {
      "type": "http",
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.xyz-urbanplayground-events]
url = "https://eventchat-events-mcp-production.up.railway.app/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "xyz-urbanplayground-events": {
      "type": "remote",
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add xyz-urbanplayground-events --url 'https://eventchat-events-mcp-production.up.railway.app/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  xyz-urbanplayground-events:
    url: "https://eventchat-events-mcp-production.up.railway.app/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "xyz-urbanplayground-events": {
      "Transport": "http",
      "Url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}
# add to Vellum
assistant mcp add xyz-urbanplayground-events -t streamable-http -u 'https://eventchat-events-mcp-production.up.railway.app/mcp'
// mcp.json
{
  "mcpServers": {
    "xyz-urbanplayground-events": {
      "type": "http",
      "url": "https://eventchat-events-mcp-production.up.railway.app/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 20 Sept 26 0
    • Schema quality: 2493 → 2809 functional
    • Server version: 0.7.6 → 0.8.0 functional
    • New tool “add_to_dizko_plan” functional
    • New tool “get_artist” functional
    • New tool “get_venue” functional
    • New tool “save_event” 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
  • 3 Sept 26 0
    • Schema quality: fail → pass functional
    • Server version: 0.7.4 → 0.7.6 functional
    • New tool “get_artist_page” functional
  • 2 Sept 26 0
    • Server version: 0.7.3 → 0.7.4 functional
  • 31 Aug 26 −8
    • Stability: pass → fail security
    • The server rewrote its instructions, which are the text every model session reads security
    • The server changed its declared name: eventchat-events → dizko 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_feedback_prompt” 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_event_search_followups” rewrote its description, which is the text the model reads security
    • Tool “get_preference_onboarding” 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 “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_preference_profile” rewrote its description, which is the text the model reads security
    • Tool coverage: 52% → 0% functional
    • Tool “get_artist_events” dropped its output schema functional
    • Tool “get_city_pulse” dropped its output schema functional
    • Tool “get_daily_roundup” dropped its output schema functional
    • Tool “get_event” dropped its output schema functional
    • Tool “get_event_feedback_prompt” dropped its output schema functional
    • Tool “get_event_preferences” dropped its output schema functional
    • Tool “get_event_search_followups” dropped its output schema functional
    • Tool “get_preference_onboarding” dropped its output schema functional
    • Tool “get_ticket_offers” dropped its output schema functional
    • Tool “get_ticket_purchase_policy” dropped its output schema functional
    • Tool “plan_night” dropped its output schema functional
    • Tool “purchase_ticket_order” dropped its output schema functional
    • Tool “quote_ticket_order” dropped its output schema functional
    • Tool “recommend_events” dropped its output schema functional
    • Tool “recommend_events_for_user” dropped its output schema functional
    • Tool “record_event_feedback” dropped its output schema functional
    • Tool “save_event_preferences” dropped its output schema functional
    • Tool “search_events” dropped its output schema functional
    • Tool “create_event_calendar_file” dropped its output schema functional
    • Tool “create_event_preference_profile” dropped its output schema functional
    • Tool “delete_event_preferences” dropped its output schema functional
    • Schema quality: 182 → 106 functional
    • Server version: 0.7.0 → 0.7.3 functional
    • New tool “find_scene_entities” functional
    • New tool “list_cities” functional
    • “plan_night” added an optional parameter “promoter” cosmetic
    • “recommend_events” added an optional parameter “promoter” cosmetic
    • “search_events” added an optional parameter “promoter” cosmetic
    • “delete_event_preferences” reworded the description of “profile_secret” 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_event” reworded the description of “id” cosmetic
    • “get_artist_events” reworded the description of “date_to” cosmetic
    • “get_artist_events” reworded the description of “limit_per_artist” cosmetic
    • “get_artist_events” reworded the description of “profile_id” cosmetic
    • “get_artist_events” reworded the description of “profile_secret” 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 “limit” cosmetic
    • “get_daily_roundup” reworded the description of “profile_id” cosmetic
    • “get_daily_roundup” reworded the description of “profile_secret” cosmetic
    • “get_daily_roundup” reworded the description of “top_limit” cosmetic
    • “get_daily_roundup” reworded the description of “when” cosmetic
    • “get_event_feedback_prompt” reworded the description of “attended_at” cosmetic
    • “get_event_preferences” reworded the description of “profile_id” cosmetic
    • “get_event_preferences” reworded the description of “profile_secret” cosmetic
    • “get_event_search_followups” reworded the description of “avoid” cosmetic
    • “get_event_search_followups” reworded the description of “city” cosmetic
    • “get_event_search_followups” reworded the description of “date_from” cosmetic
    • “get_event_search_followups” reworded the description of “max_price” cosmetic
    • “get_event_search_followups” reworded the description of “query” cosmetic
    • “get_event_search_followups” reworded the description of “when” cosmetic
    • “get_preference_onboarding” reworded the description of “profile_id” cosmetic
    • “get_ticket_offers” reworded the description of “event_id” 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 “featuring” cosmetic
    • “plan_night” reworded the description of “limit” cosmetic
    • “plan_night” reworded the description of “max_price” cosmetic
    • “plan_night” reworded the description of “profile_id” cosmetic
    • “plan_night” reworded the description of “profile_secret” cosmetic
    • “plan_night” reworded the description of “query” 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 “idempotency_key” 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 “event_id” 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 “featuring” cosmetic
    • “recommend_events” reworded the description of “limit” cosmetic
    • “recommend_events” reworded the description of “max_price” cosmetic
    • “recommend_events” reworded the description of “query” cosmetic
    • “recommend_events” reworded the description of “when” cosmetic
    • “recommend_events_for_user” reworded the description of “profile_secret” cosmetic
    • “record_event_feedback” reworded the description of “attended_at” cosmetic
    • “record_event_feedback” reworded the description of “profile_secret” cosmetic
    • “save_event_preferences” reworded the description of “consent” cosmetic
    • “save_event_preferences” reworded the description of “profile_id” cosmetic
    • “save_event_preferences” reworded the description of “profile_secret” cosmetic
    • “search_events” reworded the description of “avoid” cosmetic
    • “search_events” reworded the description of “city” 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 “featuring” cosmetic
    • “search_events” reworded the description of “limit” cosmetic
    • “search_events” reworded the description of “max_price” cosmetic
    • “search_events” reworded the description of “query” cosmetic
    • “search_events” reworded the description of “when” cosmetic
    • “get_daily_roundup” reworded the description of “section_limit” cosmetic
    • “create_event_calendar_file” reworded the description of “event_id” cosmetic
    • “create_event_calendar_file” reworded the description of “status” cosmetic
    • “create_event_preference_profile” reworded the description of “consent” cosmetic
    • “delete_event_preferences” reworded the description of “confirm_delete” cosmetic
    • “delete_event_preferences” reworded the description of “profile_id” cosmetic
    • “get_event_search_followups” dropped the optional parameter “date_to” cosmetic
    • “get_event_search_followups” dropped the optional parameter “featuring” cosmetic
    • “get_event_search_followups” dropped the optional parameter “limit” cosmetic
    • “get_event_search_followups” dropped the optional parameter “offset” cosmetic
    • “get_event_search_followups” dropped the optional parameter “price_min” cosmetic
    • “get_event_search_followups” dropped the optional parameter “pride” cosmetic
    • “get_event_search_followups” dropped the optional parameter “result_limit” cosmetic
  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 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
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 20 Sept 2026 · Probed https://eventchat-events-mcp-production.up.railway.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.up.railway.app CN=YE1,O=Let's Encrypt,C=US 29 Jul 2026 27 Oct 2026 ECDSA 256 ECDSA-SHA384 6da79bb561da3efeb0e751ca21abd3999fe
SANs: *.up.railway.app, up.railway.app
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

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 No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
content-security-policy default-src 'none'; base-uri 'none'; connect-src 'self' https://api.dizko.app https://www.dizko.app; frame-ancestors https://chatgpt.com https://chat.openai.com; img-src 'self' https://www.dizko.app data:; style-src 'unsafe-inline'
x-content-type-options nosniff
referrer-policy no-referrer

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 Verified 200
http (plaintext) http://eventchat-events-mcp-production.up.railway.app/mcp HTTPS enforced 301 https://eventchat-events-mcp-production.up.railway.app/mcp
MCP tools · 28 exposed · ~2,204 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.

create_event_calendar_file ~46

Use this when a user wants to add a Dizko event to their calendar after choosing or buying tickets.

NameTypeReqDescription
event_idstringyes
statusstring

No output schema declared.

No examples provided.

create_event_preference_profile ~38

Use this when a user agrees to create a saved Dizko preference profile.

NameTypeReqDescription
consentbooleanyes
preferences

No output schema declared.

No examples provided.

delete_event_preferences ~52

Use this only when a user asks to delete their Dizko saved event preferences and feedback history.

NameTypeReqDescription
confirm_deletebooleanyes
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 ~89

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
limitnumber
querystring

No output schema declared.

No examples provided.

get_artist_events ~84

Use this when a user wants upcoming events for named artists or artists saved in a Dizko profile.

NameTypeReqDescription
artistsarray
citystring
date_fromstring
date_tostring
limit_per_artistnumber
profile_idstring
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 ~61

Use this when a user wants a city's busiest nights, top venues, genre mix, and headline events.

NameTypeReqDescription
citystringyes
date_fromstring
daysnumber
event_typesarray

No output schema declared.

No examples provided.

get_daily_roundup ~133

Use this when a user wants a daily city event digest.

NameTypeReqDescription
avoidarray
citystringyes
datestring
event_typesarray
freeboolean
genresarray
limitnumber
neighborhoodsarray
price_maxnumber
profile_idstring
profile_secretstring
section_limitnumber
top_limitnumber
vibearray
whenstring

No output schema declared.

No examples provided.

get_event ~30

Use this when a user asks for details about a Dizko event id.

NameTypeReqDescription
idstringyes

No output schema declared.

No examples provided.

get_event_feedback_prompt ~39

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

NameTypeReqDescription
attended_atstring
event_idstringyes

No output schema declared.

No examples provided.

get_event_preferences ~39

Use this when a user wants to view saved and learned event preferences.

NameTypeReqDescription
profile_idstringyes
profile_secretstringyes

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 ~33

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

NameTypeReqDescription
profile_idstring

No output schema declared.

No examples provided.

get_ticket_offers ~37

Use this when a user wants ticket options for a specific Dizko event before quoting or buying.

NameTypeReqDescription
event_idstringyes

No output schema declared.

No examples provided.

get_ticket_purchase_policy ~24

Use this when a user asks how Dizko agents can buy tickets.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_venue ~87

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
limitnumber
querystring

No output schema declared.

No examples provided.

list_cities ~23

Use this when a user asks about Dizko city coverage or freshness.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_night ~201

Use this when a user wants a primary night-out plan with fallback events.

NameTypeReqDescription
avoidarray
citystring
cursorstring
date_fromstring
date_tostring
event_typesarray
featuringstring
freeboolean
genresarray
limitnumber
max_pricenumber
neighborhoodsarray
offsetnumber
price_maxnumber
price_minnumber
prideboolean
profile_idstring
profile_secretstring
promoterstring
querystring
result_limitnumber
venuestring
vibearray
whenstring

No output schema declared.

No examples provided.

purchase_ticket_order ~61

Use this when a user confirms a locked quote for purchase or checkout handoff.

NameTypeReqDescription
confirmation_textstringyes
idempotency_keystring
quote_tokenstringyes
user_payment_profile_idstring

No output schema declared.

No examples provided.

quote_ticket_order ~76

Use this when a user wants a locked ticket quote before purchase.

NameTypeReqDescription
currencystring
event_idstringyes
max_totalnumber
offer_idstring
quantitynumber
refund_termsstring
ticket_typestring

No output schema declared.

No examples provided.

recommend_events ~188

Use this when a user wants live events ranked by taste, vibe, price, and exclusions.

NameTypeReqDescription
avoidarray
citystring
cursorstring
date_fromstring
date_tostring
event_typesarray
featuringstring
freeboolean
genresarray
limitnumber
max_pricenumber
neighborhoodsarray
offsetnumber
price_maxnumber
price_minnumber
prideboolean
promoterstring
querystring
result_limitnumber
venuestring
vibearray
whenstring

No output schema declared.

No examples provided.

recommend_events_for_user ~173

Use this when a user wants recommendations personalized with a saved Dizko profile.

NameTypeReqDescription
avoidarray
citystring
date_fromstring
date_tostring
event_typesarray
featuringstring
freeboolean
genresarray
limitnumber
max_pricenumber
neighborhoodsarray
nightlifeboolean
price_maxnumber
profile_idstringyes
profile_secretstringyes
querystring
result_limitnumber
venuestring
vibearray
whenstring

No output schema declared.

No examples provided.

record_event_feedback ~81

Use this when a user wants Dizko to learn from their rating or notes about an event.

NameTypeReqDescription
attended_atstring
event_idstringyes
likedboolean
notesstring
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 ~59

Use this when a user wants to update a saved Dizko preference profile.

NameTypeReqDescription
consentbooleanyes
modestring
preferencesyes
profile_idstringyes
profile_secretstringyes

No output schema declared.

No examples provided.

search_events ~179

Use this when a user wants filtered live events.

NameTypeReqDescription
avoidarray
citystring
cursorstring
date_fromstring
date_tostring
event_typesarray
featuringstring
freeboolean
genresarray
limitnumber
max_pricenumber
neighborhoodsarray
offsetnumber
price_maxnumber
price_minnumber
prideboolean
promoterstring
querystring
result_limitnumber
venuestring
vibearray
whenstring

No output schema declared.

No examples provided.

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 67 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 28 tools: get_preference_onboarding, create_event_preference_profile, save_event_preferences, get_event_preferences, delete_event_preferences, and 23 more. Their descriptions and schemas cost roughly 2,204 tokens of context every time the server is loaded.

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

No. We connected to xyz.urbanplayground/events without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

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

xyz.urbanplayground/events is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.