# xyz.urbanplayground/events (remote · eventchat-events-mcp-production.up.railway.app)

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

- Trust score: 61/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `eventchat-events-mcp-production.up.railway.app`: 61/100 (this document), [markdown](https://verifymcp.io/servers/xyz-urbanplayground-events/eventchat-events-mcp-production.md), [page](https://verifymcp.io/servers/xyz-urbanplayground-events/eventchat-events-mcp-production)
- npm · `uplayground-events`: 27/100, [markdown](https://verifymcp.io/servers/xyz-urbanplayground-events/uplayground-events.md), [page](https://verifymcp.io/servers/xyz-urbanplayground-events/uplayground-events)

## Channel facts

- Endpoint: `https://eventchat-events-mcp-production.up.railway.app/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 57/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_event_preferences).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 54/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3840 tokens (~182/item across 21 items; 21 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 52% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### Claude

```bash
claude mcp add --transport http xyz-urbanplayground-events https://eventchat-events-mcp-production.up.railway.app/mcp
```

### Codex

```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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add xyz-urbanplayground-events --url https://eventchat-events-mcp-production.up.railway.app/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  xyz-urbanplayground-events:
    url: "https://eventchat-events-mcp-production.up.railway.app/mcp"
```

### Other

```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 recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 61, 0)

- [functional] MCP protocol: Implements a current MCP spec version (2026-07-28).
- [functional] MCP protocol version: 2025-11-25 → 2026-07-28
- [functional] Server version: 0.6.0 → 0.7.0

### 2026-08-02 (score 61, +1)

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

### 2026-08-01 (score 60, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 59, +10)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 49, −8)

- [functional regression] Schema quality: good → unverified

### 2026-07-27 (score 57, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 56)

First indexed and scored.

## MCP tools (21)

### `get_preference_onboarding` (~47 tokens)

Get Preference Onboarding

Use this when a user wants personalized event recommendations and Dizko needs consent-first questions before saving event preferences.

Input parameters:

- `profile_id` (string): Stable user/profile id if already known.

### `create_event_preference_profile` (~58 tokens)

Create Event Preference Profile

Use this when a user explicitly agrees to save event preferences and does not already have a Dizko preference profile.

Input parameters:

- `consent` (boolean, required): Must be true only after the user agreed to save preferences.
- `preferences` (object)

### `save_event_preferences` (~97 tokens)

Save Event Preferences

Use this when a consenting user already has a Dizko profile and wants to add, update, merge, or replace saved event preferences.

Input parameters:

- `consent` (boolean, required): Must be true only after the user agreed to save preferences.
- `mode` (string)
- `preferences` (object, required)
- `profile_id` (string, required): Stable user/profile id.
- `profile_secret` (string, required): Private profile secret returned when the profile was created.

### `get_event_preferences` (~59 tokens)

Get Event Preferences

Use this when a user with a Dizko profile wants to view saved event preferences or learned recommendation signals.

Input parameters:

- `profile_id` (string, required): Stable user/profile id.
- `profile_secret` (string, required): Private profile secret returned when the profile was created.

### `delete_event_preferences` (~82 tokens)

Delete Event Preferences

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

Input parameters:

- `confirm_delete` (boolean, required): Must be true only after the user confirms deletion of Dizko connector preferences and feedback history.
- `profile_id` (string, required): Stable user/profile id.
- `profile_secret` (string, required): Private profile secret returned when the profile was created.

### `record_event_feedback` (~112 tokens)

Record Event Feedback

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.

Input parameters:

- `attended_at` (string): ISO date/time or YYYY-MM-DD.
- `event_id` (string, required)
- `liked` (boolean)
- `notes` (string)
- `profile_id` (string, required)
- `profile_secret` (string, required): Private profile secret returned when the profile was created.
- `rating` (number)

### `get_event_feedback_prompt` (~69 tokens)

Get Event Feedback Prompt

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.

Input parameters:

- `attended_at` (string): Optional ISO date/time or YYYY-MM-DD the user attended or planned to attend.
- `event_id` (string, required)

### `get_event_search_followups` (~344 tokens)

Get Event Search Followups

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.

Input parameters:

- `avoid` (array): Terms to penalize in recommendations.
- `city` (string): City name, for example berlin or new york.
- `date_from` (string): Inclusive start date in YYYY-MM-DD format.
- `date_to` (string): Inclusive end date in YYYY-MM-DD format.
- `event_types` (array)
- `featuring` (string): Artist or performer name.
- `free` (boolean)
- `genres` (array)
- `limit` (number): Results per page (default 12). The response's count field is the TOTAL matching events. Raise limit or use offset to page through more.
- `max_price` (number): Preference hint used by recommend_events and plan_night.
- `neighborhoods` (array)
- `offset` (number)
- `price_max` (number)
- `price_min` (number)
- `pride` (boolean)
- `query` (string): Free-text search, hybrid-ranked by the live API: exact prefix > substring > fuzzy > semantic similarity over event embeddings. Handles soft natural-language intent ('dark queer warehouse rave', 'ambi…
- `result_limit` (number)
- `venue` (string)
- `vibe` (array)
- `when` (string): Date preset: today, tonight, tomorrow, weekend, week, this week, any, or YYYY-MM-DD.

### `search_events` (~334 tokens)

Search Events

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.

Input parameters:

- `avoid` (array): Terms to penalize in recommendations.
- `city` (string): City name, for example berlin or new york.
- `date_from` (string): Inclusive start date in YYYY-MM-DD format.
- `date_to` (string): Inclusive end date in YYYY-MM-DD format.
- `event_types` (array)
- `featuring` (string): Artist or performer name.
- `free` (boolean)
- `genres` (array)
- `limit` (number): Results per page (default 12). The response's count field is the TOTAL matching events. Raise limit or use offset to page through more.
- `max_price` (number): Preference hint used by recommend_events and plan_night.
- `neighborhoods` (array)
- `offset` (number)
- `price_max` (number)
- `price_min` (number)
- `pride` (boolean)
- `query` (string): Free-text search, hybrid-ranked by the live API: exact prefix > substring > fuzzy > semantic similarity over event embeddings. Handles soft natural-language intent ('dark queer warehouse rave', 'ambi…
- `result_limit` (number)
- `venue` (string)
- `vibe` (array)
- `when` (string): Date preset: today, tonight, tomorrow, weekend, week, this week, any, or YYYY-MM-DD.

### `recommend_events` (~330 tokens)

Recommend Events

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.

Input parameters:

- `avoid` (array): Terms to penalize in recommendations.
- `city` (string): City name, for example berlin or new york.
- `date_from` (string): Inclusive start date in YYYY-MM-DD format.
- `date_to` (string): Inclusive end date in YYYY-MM-DD format.
- `event_types` (array)
- `featuring` (string): Artist or performer name.
- `free` (boolean)
- `genres` (array)
- `limit` (number): Results per page (default 12). The response's count field is the TOTAL matching events. Raise limit or use offset to page through more.
- `max_price` (number): Preference hint used by recommend_events and plan_night.
- `neighborhoods` (array)
- `offset` (number)
- `price_max` (number)
- `price_min` (number)
- `pride` (boolean)
- `query` (string): Free-text search, hybrid-ranked by the live API: exact prefix > substring > fuzzy > semantic similarity over event embeddings. Handles soft natural-language intent ('dark queer warehouse rave', 'ambi…
- `result_limit` (number)
- `venue` (string)
- `vibe` (array)
- `when` (string): Date preset: today, tonight, tomorrow, weekend, week, this week, any, or YYYY-MM-DD.

### `recommend_events_for_user` (~197 tokens)

Recommend Events For User

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.

Input parameters:

- `avoid` (array)
- `city` (string)
- `date_from` (string)
- `date_to` (string)
- `event_types` (array)
- `featuring` (string)
- `free` (boolean)
- `genres` (array)
- `limit` (number)
- `max_price` (number)
- `neighborhoods` (array)
- `nightlife` (boolean)
- `price_max` (number)
- `profile_id` (string, required)
- `profile_secret` (string, required): Private profile secret returned when the profile was created.
- `query` (string)
- `result_limit` (number)
- `venue` (string)
- `vibe` (array)
- `when` (string)

### `plan_night` (~369 tokens)

Plan Night

Use this when a user wants a compact night-out plan with a primary live event option and fallback options from Dizko inventory.

Input parameters:

- `avoid` (array): Terms to penalize in recommendations.
- `city` (string): City name, for example berlin or new york.
- `date_from` (string): Inclusive start date in YYYY-MM-DD format.
- `date_to` (string): Inclusive end date in YYYY-MM-DD format.
- `event_types` (array)
- `featuring` (string): Artist or performer name.
- `free` (boolean)
- `genres` (array)
- `limit` (number): Results per page (default 12). The response's count field is the TOTAL matching events. Raise limit or use offset to page through more.
- `max_price` (number): Preference hint used by recommend_events and plan_night.
- `neighborhoods` (array)
- `offset` (number)
- `price_max` (number)
- `price_min` (number)
- `pride` (boolean)
- `profile_id` (string): Optional Dizko preference profile id. Supply it with profile_secret to apply saved and learned taste.
- `profile_secret` (string): Private profile secret returned when the profile was created.
- `query` (string): Free-text search, hybrid-ranked by the live API: exact prefix > substring > fuzzy > semantic similarity over event embeddings. Handles soft natural-language intent ('dark queer warehouse rave', 'ambi…
- `result_limit` (number)
- `venue` (string)
- `vibe` (array)
- `when` (string): Date preset: today, tonight, tomorrow, weekend, week, this week, any, or YYYY-MM-DD.

### `get_daily_roundup` (~297 tokens)

Get Daily Roundup

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.

Input parameters:

- `avoid` (array): Terms to penalize in the ranking.
- `city` (string, required): City name, for example berlin or new york.
- `date` (string): Target day in YYYY-MM-DD format. Defaults to today.
- `event_types` (array)
- `free` (boolean)
- `genres` (array)
- `limit` (number): How many of the day's events to fetch and rank.
- `neighborhoods` (array)
- `price_max` (number)
- `profile_id` (string): Optional Dizko preference profile id. Supply it with profile_secret to personalize the picks with saved, learned, and per-day preferences.
- `profile_secret` (string): Private profile secret returned when the profile was created.
- `section_limit` (number): Events per category section (max 10).
- `top_limit` (number): Top picks to feature (max 10).
- `vibe` (array)
- `when` (string): Alternative date preset: today, tonight, or tomorrow.

### `get_artist_events` (~203 tokens)

Get Artist Events

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.

Input parameters:

- `artists` (array): Artist, DJ, performer, or comedian names to look up (max 8 per call).
- `city` (string): Optional city to scope the search; omit to search all cities.
- `date_from` (string): Inclusive start date in YYYY-MM-DD format. Defaults to today.
- `date_to` (string): Optional inclusive end date in YYYY-MM-DD format.
- `limit_per_artist` (number): Upcoming events per artist (max 10).
- `profile_id` (string): Optional Dizko preference profile id. When artists is omitted, the profile's saved featuring list is used.
- `profile_secret` (string): Private profile secret returned when the profile was created.

### `get_city_pulse` (~133 tokens)

Get City Pulse

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.

Input parameters:

- `city` (string, required): City name, for example berlin or new york.
- `date_from` (string): Inclusive start date in YYYY-MM-DD format. Defaults to today.
- `days` (number): Window length in days starting from date_from (max 14).
- `event_types` (array): Optional event-type filter, for example party.

### `get_event` (~43 tokens)

Get Event

Use this when a user asks for details about a specific Dizko event id returned by search, recommendations, or a night plan.

Input parameters:

- `id` (string, required): Event id.

### `get_ticket_purchase_policy` (~42 tokens)

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.

### `get_ticket_offers` (~52 tokens)

Get Ticket Offers

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

Input parameters:

- `event_id` (string, required): Event id returned by search, recommendations, plan_night, or get_event.

### `quote_ticket_order` (~169 tokens)

Quote Ticket Order

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.

Input parameters:

- `currency` (string): Preferred currency for max_total, for example USD.
- `event_id` (string, required): Event id returned by search, recommendations, plan_night, or get_event.
- `max_total` (number): Maximum all-in total the user authorizes before the agent must stop and ask again.
- `offer_id` (string): Optional offer_id returned by get_ticket_offers.
- `quantity` (number)
- `refund_terms` (string): Minimum refund/transfer terms the user accepts.
- `ticket_type` (string): Requested ticket type, for example GA, balcony, seated, VIP, or best available.

### `purchase_ticket_order` (~129 tokens)

Purchase Ticket Order

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.

Input parameters:

- `confirmation_text` (string, required): User's explicit written confirmation, including buy/purchase, quantity, and max_total when present.
- `idempotency_key` (string): Optional idempotency key for integrated purchase providers.
- `quote_token` (string, required): Opaque quote token returned by quote_ticket_order.
- `user_payment_profile_id` (string): Provider-specific saved payment profile id, when an integrated provider supports autonomous purchase.

### `create_event_calendar_file` (~77 tokens)

Create Event Calendar File

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

Input parameters:

- `event_id` (string, required): Event id returned by search, recommendations, plan_night, get_event, or a ticket quote.
- `status` (string): Calendar status, for example CONFIRMED or TENTATIVE.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/xyz-urbanplayground-events/eventchat-events-mcp-production#diagnostics

## Score history

- 2026-08-03: 61
- 2026-08-02: 61
- 2026-08-01: 60
- 2026-07-31: 59
- 2026-07-30: 49
- 2026-07-28: 57
- 2026-07-27: 57
- 2026-07-26: 56

## Links

- Remote endpoint: https://eventchat-events-mcp-production.up.railway.app/mcp
- Website: https://urbanplayground.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/xyz-urbanplayground-events/eventchat-events-mcp-production/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/xyz-urbanplayground-events/eventchat-events-mcp-production/changelog.json
- HTML version of this page: https://verifymcp.io/servers/xyz-urbanplayground-events/eventchat-events-mcp-production