LeashIndex Get the report

Index / calendar

xyz.urbanplayground/events

xyz-urbanplayground-events declares 31 capabilities across 31 tools, with 3 critical issues.

79/100 exposureHigh exposure

Manifest recorded 2026-10-21 from tools/list on https://eventchat-events-mcp-production.up.railway.app/mcp, published in the official MCP registry as xyz.urbanplayground/events 0.3.0. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 31 tools

31 of 31 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 5 of 31 tools

5 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 1 of 31 tools

1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 31 tools

31 of 31 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 31 tools

31 of 31 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 3 of 31 tools

3 tools can modify data and declare no limit.

low · uncapped-read · 23 of 31 tools

23 tools can read data and declare no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

ToolRead asBasis
get_dizko_onboardingread declared
get_preference_onboardingread declared
create_event_preference_profilewrite inferred
save_event_preferencesdestructive declared
get_event_preferencesread declared
delete_event_preferencesdestructive declared
record_event_feedbacksend inferred
get_event_feedback_promptread declared
get_event_search_followupsread declared
list_citiesread declared
find_scene_entitiesread declared
get_artistread declared
get_venueread declared
search_eventsread declared
recommend_eventsread declared
recommend_events_for_userread declared
plan_nightread declared
get_daily_roundupread declared
get_artist_eventsread declared
get_artist_pageread declared
get_city_pulseread declared
get_eventread declared
get_ticket_purchase_policyread declared
get_ticket_offersread declared
quote_ticket_orderread declared
purchase_ticket_orderpay inferred
get_taste_profileread declared
bin_eventdestructive declared
save_eventwrite assumed
add_to_dizko_planwrite inferred
create_event_calendar_fileread declared

Record history

Earlier records for this server. A correction is added here, never written over the record it corrects.

RecordedExposureSource
2026-10-1679 tools/list on https://eventchat-events-mcp-production.up.railway.app/mcp, published in the official MCP registry as xyz.urbanplayground/events 0.3.0
2026-10-1174 tools/list on https://eventchat-events-mcp-production.up.railway.app/mcp, published in the official MCP registry as xyz.urbanplayground/events 0.3.0
Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.
Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.