LeashIndex Get the report

Index / calendar

XP Tickets

tickets-xp-xp-tickets declares 40 capabilities across 40 tools, with 3 critical issues.

91/100 exposureHigh exposure

Manifest recorded 2026-10-21 from tools/list on https://mcp.xp.tickets/mcp, published in the official MCP registry as tickets.xp/xp-tickets 4.0.9. 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 40 tools

40 of 40 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 · 9 of 40 tools

9 tools are classified as irreversible and declare no limit.

critical · uncapped-spend · 2 of 40 tools

2 tools are classified as moving money and declare no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 40 tools

40 of 40 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 40 tools

40 of 40 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.

low · uncapped-read · 31 of 40 tools

31 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
search_eventsread declared
get_event_detailsread declared
search_performersread declared
get_ticket_listingsread declared
buy_ticketspay inferred
search_venuesread declared
get_venue_detailsread declared
check_listingread declared
search_marketread declared
get_market_readread declared
get_recent_salesread declared
get_price_historyread declared
get_my_contextread declared
get_seat_mapread declared
get_user_accountread declared
auth_statusread declared
get_my_ordersread declared
get_order_statusread declared
get_my_ticketsread declared
list_my_favoritesread declared
get_my_walletread declared
get_my_referral_kickbacksread declared
list_open_listingsread declared
get_open_listingread declared
get_my_listing_statusread declared
list_my_listingsread declared
get_my_bidsread declared
make_offer_on_listingdestructive declared
accept_offerdestructive declared
reject_offerdestructive declared
cancel_my_offerdestructive declared
list_muted_listingsread declared
mute_listingread inferred
list_my_standing_bidsread declared
get_standing_bidread declared
create_standing_biddestructive declared
rescind_standing_biddestructive declared
buy_listing_nowpay inferred
create_listingread inferred
cancel_my_listingdestructive declared

Record history

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

RecordedExposureSource
2026-10-1691 tools/list on https://mcp.xp.tickets/mcp, published in the official MCP registry as tickets.xp/xp-tickets 4.0.9
2026-10-1191 tools/list on https://mcp.xp.tickets/mcp, published in the official MCP registry as tickets.xp/xp-tickets 4.0.9
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.