xyz.urbanplayground/events
REMOTE · EVENTCHAT-EVENTS-MCP-PRODUCTION.UP.RAILWAY.APP · 2 COMPONENTS · SCANNED AUG 3
Live event discovery: concerts, club nights, art, comedy, and festivals across 14 cities.
Available components
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 →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (delete_event_preferences). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability54
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage86
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 52% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · eventchat-events-mcp-production.up.railway.app
claude mcp add --transport http xyz-urbanplayground-events https://eventchat-events-mcp-production.up.railway.app/mcp
[mcp_servers.xyz-urbanplayground-events] url = "https://eventchat-events-mcp-production.up.railway.app/mcp"
{
"$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 mcp add xyz-urbanplayground-events --url https://eventchat-events-mcp-production.up.railway.app/mcp --transport streamable-http
mcp_servers:
xyz-urbanplayground-events:
url: "https://eventchat-events-mcp-production.up.railway.app/mcp" {
"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.
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.
- 3 Aug 26 0
- 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 functional
- 2 Aug 26 +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.
- 1 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
- 31 Jul 26 +10
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 −8
- Schema quality: good → unverified ▼ functional
- 27 Jul 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
- 26 Jul 26 56
First indexed and scored.
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 3 Aug 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 |
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 |
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 |
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.
create_event_calendar_file Create Event Calendar File ~77
Use this when a user wants to add a Dizko event to their calendar after choosing or buying tickets.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event id returned by search, recommendations, plan_night, get_event, or a ticket quote. |
| status | string | — | Calendar status, for example CONFIRMED or TENTATIVE. |
Structured output declared, but exposes no named fields.
No examples provided.
create_event_preference_profile Create Event Preference Profile ~58
Use this when a user explicitly agrees to save event preferences and does not already have a Dizko preference profile.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | yes | Must be true only after the user agreed to save preferences. |
| preferences | object | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
delete_event_preferences Delete Event Preferences ~82
Use this only when a user asks to delete their Dizko saved event preferences and feedback history.
| Name | Type | Req | Description |
|---|---|---|---|
| confirm_delete | boolean | yes | Must be true only after the user confirms deletion of Dizko connector preferences and feedback history. |
| profile_id | string | yes | Stable user/profile id. |
| profile_secret | string | yes | Private profile secret returned when the profile was created. |
Structured output declared, but exposes no named fields.
No examples provided.
get_artist_events Get Artist Events ~203
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
get_city_pulse Get City Pulse ~133
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.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
get_daily_roundup Get Daily Roundup ~297
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.
| Name | Type | Req | Description |
|---|---|---|---|
| avoid | array | — | Terms to penalize in the ranking. |
| city | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
get_event Get Event ~43
Use this when a user asks for details about a specific Dizko event id returned by search, recommendations, or a night plan.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Event id. |
Structured output declared, but exposes no named fields.
No examples provided.
get_event_feedback_prompt Get Event Feedback Prompt ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attended_at | string | — | Optional ISO date/time or YYYY-MM-DD the user attended or planned to attend. |
| event_id | string | yes | — |
Structured output declared, but exposes no named fields.
No examples provided.
get_event_preferences Get Event Preferences ~59
Use this when a user with a Dizko profile wants to view saved event preferences or learned recommendation signals.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_id | string | yes | Stable user/profile id. |
| profile_secret | string | yes | Private profile secret returned when the profile was created. |
Structured output declared, but exposes no named fields.
No examples provided.
get_event_search_followups Get Event Search Followups ~344
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
get_preference_onboarding Get Preference Onboarding ~47
Use this when a user wants personalized event recommendations and Dizko needs consent-first questions before saving event preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| profile_id | string | — | Stable user/profile id if already known. |
Structured output declared, but exposes no named fields.
No examples provided.
get_ticket_offers Get Ticket Offers ~52
Use this when a user wants ticket options for a specific Dizko event before quoting or buying.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | Event id returned by search, recommendations, plan_night, or get_event. |
Structured output declared, but exposes no named fields.
No examples provided.
get_ticket_purchase_policy Get Ticket Purchase Policy ~42
Use this when a user asks whether agents can buy tickets autonomously or what purchase modes Dizko, Hermes, OpenClaw, or other providers can support.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
plan_night Plan Night ~369
Use this when a user wants a compact night-out plan with a primary live event option and fallback options from Dizko inventory.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
purchase_ticket_order Purchase Ticket Order ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| confirmation_text | string | yes | 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 | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
quote_ticket_order Quote Ticket Order ~169
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.
| Name | Type | Req | Description |
|---|---|---|---|
| currency | string | — | Preferred currency for max_total, for example USD. |
| event_id | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
recommend_events Recommend Events ~330
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.
recommend_events_for_user Recommend Events For User ~197
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | — |
| profile_secret | string | yes | Private profile secret returned when the profile was created. |
| query | string | — | — |
| result_limit | number | — | — |
| venue | string | — | — |
| vibe | array | — | — |
| when | string | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
record_event_feedback Record Event Feedback ~112
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.
| Name | Type | Req | Description |
|---|---|---|---|
| attended_at | string | — | ISO date/time or YYYY-MM-DD. |
| event_id | string | yes | — |
| liked | boolean | — | — |
| notes | string | — | — |
| profile_id | string | yes | — |
| profile_secret | string | yes | Private profile secret returned when the profile was created. |
| rating | number | — | — |
Structured output declared, but exposes no named fields.
No examples provided.
save_event_preferences Save Event Preferences ~97
Use this when a consenting user already has a Dizko profile and wants to add, update, merge, or replace saved event preferences.
| Name | Type | Req | Description |
|---|---|---|---|
| consent | boolean | yes | Must be true only after the user agreed to save preferences. |
| mode | string | — | — |
| preferences | object | yes | — |
| profile_id | string | yes | Stable user/profile id. |
| profile_secret | string | yes | Private profile secret returned when the profile was created. |
Structured output declared, but exposes no named fields.
No examples provided.
search_events Search Events ~334
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
Structured output declared, but exposes no named fields.
No examples provided.