Skip to content

XP Tickets MCP server

tickets.xp/xp-ticketsxp.ticketsstreamable-httpv4.0.9Scanned

Live-event ticket exchange for agents: quote, buy, make offers, bid, and sell, with escrow.

36 tools: 8 can delete or cancel things, 2 change things and 26 only read.

Tools: 8 delete, 0 irreversible, 2 write, 26 read.
  • Reads private data · 1
  • Reads text others write · 15
  • Can send data out · 0
  • 4 findings

Tools listed without sign-in. Remote posture

With Anlyon

8 tools here can delete or cancel things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the XP Tickets MCP server can do

The XP Tickets MCP server is published by xp.tickets, a domain the MCP Registry verified. It has 36 tools. It can delete or cancel things (8 tools: buy_tickets, accept_offer, reject_offer, cancel_my_offer and 4 more) and create or change data (2 tools: check_listing and mute_listing). 26 tools only read.

1 tool reads private data (get_user_account); 15 tools bring in text other people can write (get_ticket_listings, resolve_intent, search_market and 12 more).

The fixed checks matched 4 findings (credentials-mention, tool-shadowing and long-description). Each one comes with the text it matched.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 19, 2026, version 4.0.9.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

36 tools

Deletes or cancels 8Claude Code: deny
  • accept_offerAccepts one buyer's offer on the caller's own listing on XP -- 'accept the $200 offer on my tickets'.No findings

    Why it is in this group

    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Accepts one buyer's offer on the caller's own listing on XP -- 'accept the $200 offer on my tickets'. The offer comes from a buyer, not from XP. Accepting is a sale and cannot be undone: the seller then transfers the tickets through XP to that buyer by a deadline XP sets at acceptance, and missing it can cancel the sale and forfeit the payout. The deadline is per sale, not a fixed window; the result carries it, or says XP has not set it yet. confirm=false returns a preview of the offer; confirm=true accepts it, and only that call returns success=true. identifier and offer_uuid come from get_my_listing_status. Requires sign-in and the write:listings scope.

    Annotations the server declares

    • destructiveHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • buy_listing_nowBuys a fan listing on XP outright at the seller's asking price, without an offer -- 'buy it now', 'take it at the ask'.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Buys a fan listing on XP outright at the seller's asking price, without an offer -- 'buy it now', 'take it at the ask'. Only listings with an asking price can be bought this way, and the purchase is refused if the ask changed since the preview. confirm=false returns a preview of the total; confirm=true completes the sale at once, paid from the caller's XP USDC balance, and commits the seller. The x402 rail is for buy_tickets and does not apply here. identifier comes from list_open_listings or get_open_listing. Requires sign-in.

    Annotations the server declares

    • destructiveHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • buy_ticketsBuy tickets from a get_ticket_listings listing (event_id, uvid, quantity) on XP.2 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it destructive (destructiveHint: true).

    Findings

    • Info

      The description mentions "credential".

      Matched text

      description: "..., sent in params._meta['org.paymentauth/credential'] or as payment_credential. Requires si..."

      What this check looks for
    • Info

      The input schema at properties.payment_credential.description mentions "credential".

      Matched text

      inputSchema.properties.payment_credential.description: "rail='mpp' only. JSON MPP credential, as a fallback for clients that cannot..."

      What this check looks for
    Description, as the server wrote it
    Buy tickets from a get_ticket_listings listing (event_id, uvid, quantity) on XP. Two calls: confirm=false returns a preview with the all-in total; confirm=true, once the person approves, completes the order and returns its order_uuid. Four payment rails, chosen with rail: 'stripe_link' (the default) pays by card on a Stripe-hosted checkout page, where the preview returns payment_link and checkout_session_id and confirm=true takes that checkout_session_id; 'privy' pays USDC from the person's XP wallet, signed by the server; 'x402' takes a Solana USDC payment the caller signs, passed as payment_proof; 'mpp' pays by card with a Stripe Shared Payment Token over the Machine Payments Protocol, sent in params._meta['org.paymentauth/credential'] or as payment_credential. Requires sign-in and the write:tickets scope, plus read:account for the balance check on 'privy'.

    Annotations the server declares

    • destructiveHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • cancel_my_listingTakes down one of the caller's own listings on XP -- 'take my listing down', 'I sold them elsewhere'.No findings

    Why it is in this group

    • The name "cancel_my_listing" says "cancel": a word for removing or ending something.
    • The description says "cannot be undone".
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Takes down one of the caller's own listings on XP -- 'take my listing down', 'I sold them elsewhere'. Buyers can no longer make an offer on it, every open offer on it is rejected, and those buyers are notified that it was removed. A listing with an accepted offer is an agreed sale and cannot be taken down here; XP support handles it. confirm=false returns a preview; confirm=true removes the listing, which cannot be undone. Relisting is a new create_listing. Requires sign-in.

    Annotations the server declares

    • destructiveHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • cancel_my_offerCancels one of the caller's offers on a single XP listing -- 'pull my offer', 'cancel my bid'.No findings

    Why it is in this group

    • The name "cancel_my_offer" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Cancels one of the caller's offers on a single XP listing -- 'pull my offer', 'cancel my bid'. An open offer resting across events is cancelled with cancel_my_open_offer. offer_uuid is the offer's bid_uuid or its buyer swap id. confirm=false returns a preview; confirm=true cancels it, and only that call returns success=true. Requires sign-in and the write:bids scope.

    Annotations the server declares

    • destructiveHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • cancel_my_open_offerCloses one of the caller's open offers on XP to new fills -- 'cancel that open offer', 'stop waiting on those'.No findings

    Why it is in this group

    • The name "cancel_my_open_offer" says "cancel": a word for removing or ending something.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Closes one of the caller's open offers on XP to new fills -- 'cancel that open offer', 'stop waiting on those'. Fills it already took are completed purchases and stay. An offer on a single listing is cancelled with cancel_my_offer. confirm=false returns a preview; confirm=true cancels it. Requires sign-in.

    Annotations the server declares

    • destructiveHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • create_listingLists tickets the seller holds for sale on XP -- 'sell my two seats for Friday', 'list section 104 row C'.No findings

    Why it is in this group

    • The name "create_listing" says "create": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Lists tickets the seller holds for sale on XP -- 'sell my two seats for Friday', 'list section 104 row C'. Buyers then make an offer on the listing, and the seller answers with accept_offer or reject_offer; the tickets transfer only after an offer is accepted. is_ada, is_obstructed_view and is_sro are required inputs with no default. confirm=false returns a preview of the section, row, seats and those three flags; confirm=true creates the listing. A new listing is reviewed before it goes live: listing_state in the result is live, in_review or not_accepted, and only a live listing is visible to buyers. Requires sign-in.

    Annotations the server declares

    • destructiveHint: true
    • openWorldHint: false
    • readOnlyHint: false
  • reject_offerRejects one buyer's offer on the caller's own listing on XP -- 'reject the lowball offer on my tickets'.No findings

    Why it is in this group

    • The name "reject_offer" says "reject": a word for a change.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    Rejects one buyer's offer on the caller's own listing on XP -- 'reject the lowball offer on my tickets'. confirm=false returns a preview of the offer; confirm=true rejects it, and only that call returns success=true. identifier and offer_uuid come from get_my_listing_status. Requires sign-in and the write:listings scope.

    Annotations the server declares

    • destructiveHint: true
    • openWorldHint: false
    • readOnlyHint: false
Changes things 2Claude Code: ask
  • check_listingPoll the current status and action feed for the listing tied to this call's correlation id.2 findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Warn

      The description contains "every other tool", wording about other tools or servers.

      Matched text

      description: "...r on every MCP request, exactly like on every other tool call for this job. A missing/invalid he..."

      What this check looks for
    • Info

      The description is 3,938 characters long, over the 2,000 this check looks for.

      Matched text

      description ends: "...r": "status_unavailable"} - backend down/slow/non-200"

      What this check looks for
    Description, as the server wrote it
    Poll the current status and action feed for the listing tied to this call's correlation id. IDENTITY: the correlation id is never a tool argument. It must ride the ``X-XP-Correlation-Id`` HTTP header on every MCP request, exactly like on every other tool call for this job. A missing/invalid header returns a structured error (below) instead of failing the call -- this tool is open-world (no bearer/OAuth needed); holding the correlation id (an unguessable v4 uuid) is itself the access control. ARGS since: the ``cursor`` value returned by the previous call for this same correlation id. Omit (or pass null) on the first call to fetch the full action feed from the beginning. Must be >= 0; a negative value returns ``{"error": "invalid_since"}``. POLL LOOP: store ``cursor`` per correlation id in your own cache/store, send it back as ``since`` on the next call, and render only the new ``actions`` entries onto your own timeline -- the array already excludes anything at or before ``since`` and is empty when nothing changed. ``listing`` is a snapshot for cheap "current state" display only (quantity, bid count, bucket, ...); do not diff it yourself for history -- ``actions`` is the exact, ordered record (a bid placed and rescinded between two polls still yields both events). RESULT SCHEMA (``found: false`` -> every other field is null/absent; an unrecognized correlation id is not an error, just an empty result):: { "correlation_id": "<uuid>", "found": true, "verified": true, # identity confirmed when the listing was created "event_id": 406, # last event this correlation looked at "listing": { # null until a listing exists for this id "swap": "d5b03i1rbqqa", # public listing identifier (sell/checkout URLs) "created_at": "2026-08-12T14:00:00+00:00", "status_bucket": "open", # see BUCKETS below "event_id": 406, "quantity": 2, "bid_count": 3, "top_bid_amount": 12000, # cents, open bids, null if none "accepted_bid_amount": null, # cents, set once a bid is accepted "sold": false, "last_activity_at": "2026-08-12T14:05:00+00:00" }, "actions": [ # everything after `since`, oldest first, [] if nothing new {"id": 91234, "event": "listing_created", "at": "2026-08-12T14:00:00+00:00"}, {"id": 91288, "event": "bid_placed", "at": "2026-08-12T14:03:10+00:00", "amount": 12000} ], "cursor": 91301, # send back as `since` on the next call "actions_truncated": true # present+true only when 50+ new rows; call again with `cursor` to page } BUCKETS (listing.status_bucket) open - accepting bids, none accepted yet awaiting_tickets - a bid was accepted; seller hasn't transferred tickets yet buyer_has_tickets - tickets transferred; seller payout not yet finalized seller_payout - funds are ready to release to the seller zombies - stalled, no forward progress -- needs attention closed - terminal: cancelled, expired, or fully settled EVENT VOCABULARY (actions[].event; only bid/sale events carry `amount`, in cents) listing_created, bid_placed, bid_rescinded, bid_accepted, bid_rejected, tickets_transferred, funds_claimed, listing_cancelled, listing_expired, sale_completed NOTE: no separate payout-completion signal exists -- the agent-forward payout rail is retired; sellers claim funds normally (funds_claimed). FAILURES: this tool never raises and never returns an auth error (401). {"error": "missing_correlation_header", "message": "..."} - header missing/invalid {"error": "invalid_since"} - since < 0 {"error": "status_unavailable"} - backend down/slow/non-200

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • mute_listingMutes or unmutes one listing for the caller on XP -- 'hide this one', 'stop showing me that', 'unmute that listing'.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    Mutes or unmutes one listing for the caller on XP -- 'hide this one', 'stop showing me that', 'unmute that listing'. Muting changes only the caller's view: the listing stays open, offers on it stand, and the seller and other buyers see no change. Muted listings are left out of list_open_listings. Sets the state passed rather than toggling, so repeating a call is safe. Requires sign-in.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: false
Only reads 26Show 26 read-only tools
  • auth_statusWhether the user is signed in to the XP marketplace, for 'am I logged in?' or 'can you see my tickets?'.Reads text others writeNo findings

    Why it is in this group

    • The name "auth_status" says "status": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    Whether the user is signed in to the XP marketplace, for 'am I logged in?' or 'can you see my tickets?'. When they are, returns the account email, granted scopes, tier roles and whether a wallet is connected. When they are not, the call is refused with the same sign-in challenge as the account tools.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_event_detailsThe full card for one event on XP: venue, performers, date, images and an all-in price preview.No findings

    Why it is in this group

    • The name "get_event_details" says "get": a word for reading.
    Description, as the server wrote it
    The full card for one event on XP: venue, performers, date, images and an all-in price preview. event_id comes from search_events or search_market. The tickets themselves are in get_ticket_listings.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_market_readWhat one event is trading at on XP -- 'how much are tickets?'.Reads text others writeNo findings

    Why it is in this group

    • The name "get_market_read" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    What one event is trading at on XP -- 'how much are tickets?'. By seat level, floor first: each level's get-in, then each section's rows front to back, a row shown only when it is cheaper than every row in front of it. Prices are all-in per ticket at the party size (quantity). fan_listings counts the fan listings open to offers on the event; their asks are not included. Clubs, suites, obstructed-view and standing-only seats are left out and named in left_out; get_ticket_listings includes them. event_id comes from search_events or search_market.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_my_listing_statusOne of the caller's own listings on XP, seen as the seller -- 'any new offers on my tickets?'.Reads text others writeNo findings

    Why it is in this group

    • The name "get_my_listing_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One of the caller's own listings on XP, seen as the seller -- 'any new offers on my tickets?'. Returns the state, seats, disclosures, visible_to_buyers and the open offers on it, with amounts in dollars (amount_usd). visible_to_buyers, not the state, says whether buyers can see the listing. When is_seller is true, each open offer carries actions for accept_offer and reject_offer. When the listing has sold and awaits the seller's transfer, the result carries the transfer instructions and the remaining obligation. identifier comes from create_listing, list_my_listings or list_open_listings. Requires sign-in and the read:bids scope.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_my_offersThe offers the caller has placed on XP listings, as open or completed -- 'show my bids', 'did any of my offers settle?'.No findings

    Why it is in this group

    • The name "get_my_offers" says "get": a word for reading.
    Description, as the server wrote it
    The offers the caller has placed on XP listings, as open or completed -- 'show my bids', 'did any of my offers settle?'. Rejected, lapsed and refunded offers are left out. Paged: 25 by default, up to 200 with limit, and offset to continue; pagination.total counts only the offers shown, and has_more marks further pages. Open offers resting across events are in list_my_open_offers. Requires sign-in.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_my_ordersThe caller's orders on XP, newest first: status, fulfilment status, delivery method, in-hand date, event, seats and the all-in total in dollars -- 'where is my order?', 'when do my…Reads text others writeNo findings

    Why it is in this group

    • The name "get_my_orders" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    The caller's orders on XP, newest first: status, fulfilment status, delivery method, in-hand date, event, seats and the all-in total in dollars -- 'where is my order?', 'when do my tickets arrive?'. get_order_status reads one order by its order_uuid and get_my_tickets lists tickets already delivered; offers the caller placed are in get_my_offers and listings they are selling in list_my_listings. Requires sign-in.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_my_ticketsTickets already delivered to the caller's XP account, paged -- 'my tickets', 'pull up my seats for tonight'.Reads text others writeNo findings

    Why it is in this group

    • The name "get_my_tickets" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_my_tickets" says "get" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    Tickets already delivered to the caller's XP account, paged -- 'my tickets', 'pull up my seats for tonight'. Orders not yet delivered are in get_my_orders; tickets the caller is selling are in list_my_listings. Requires sign-in.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_my_walletThe caller's XP wallet: its address, whether one is connected (wallet_connected) and the USDC balance -- 'how much USDC do I have?'.No findings

    Why it is in this group

    • The name "get_my_wallet" says "get": a word for reading.
    Description, as the server wrote it
    The caller's XP wallet: its address, whether one is connected (wallet_connected) and the USDC balance -- 'how much USDC do I have?'. That balance funds offers, buy_listing_now and buy_tickets with rail 'privy'. Requires sign-in and the read:account scope.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_open_listingOne fan listing on XP open to offers, by the identifier from list_open_listings -- 'tell me more about those tickets'.Reads text others writeNo findings

    Why it is in this group

    • The name "get_open_listing" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One fan listing on XP open to offers, by the identifier from list_open_listings -- 'tell me more about those tickets'. Returns the full listing record; buy_listing_now buys it at its asking price. Requires sign-in and the read:bids scope.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_open_offerOne of the caller's open offers on XP by id, at any status, with the fills it has taken -- 'did that offer get my tickets?'.Reads text others writeNo findings

    Why it is in this group

    • The name "get_open_offer" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One of the caller's open offers on XP by id, at any status, with the fills it has taken -- 'did that offer get my tickets?'. Covers the filled and rescinded offers that list_my_open_offers leaves out. Requires sign-in.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_order_statusOne of the caller's orders on XP by order_uuid (from buy_tickets or get_my_orders) -- 'did that go through?'.Reads text others writeNo findings

    Why it is in this group

    • The name "get_order_status" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One of the caller's orders on XP by order_uuid (from buy_tickets or get_my_orders) -- 'did that go through?'. Returns status, fulfilment status, delivery method, in-hand date, event, seats and the all-in total in dollars. The recent list is in get_my_orders. Requires sign-in.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_price_historyOne event's daily closing get-in on XP: the lowest all-in asking price per ticket in dollars, one point per day, oldest first, over 1 to 90 days (default 30) -- 'are prices going u…Reads text others writeNo findings

    Why it is in this group

    • The name "get_price_history" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    One event's daily closing get-in on XP: the lowest all-in asking price per ticket in dollars, one point per day, oldest first, over 1 to 90 days (default 30) -- 'are prices going up?', 'should I wait for a price drop?'. This is the asking side over time; what tickets sold for is in get_recent_sales. History is recorded only for events someone is tracking, so an empty result is common and means no record, not a flat price. event_id comes from search_events or search_market.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_recent_salesRecent completed sales for one event on XP: the per-ticket price and how long ago each sale cleared -- 'what did tickets actually sell for?'.Reads text others writeNo findings

    Why it is in this group

    • The name "get_recent_sales" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    Recent completed sales for one event on XP: the per-ticket price and how long ago each sale cleared -- 'what did tickets actually sell for?'. An empty result means no verified sales in the window. Asking prices over time are in get_price_history. event_id comes from search_events or search_market.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_seat_mapThe venue seating chart for one event, as an image -- 'where is section 104?', 'show me the map'.No findings

    Why it is in this group

    • The name "get_seat_map" says "get": a word for reading.
    Description, as the server wrote it
    The venue seating chart for one event, as an image -- 'where is section 104?', 'show me the map'. It is the venue layout, showing where each section sits in the building, and not a photograph of the view from a seat. Some venues have no chart; the section and row from get_ticket_listings still identify the seats. event_id comes from search_events, search_market or get_event_details. No sign-in needed.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_ticket_listingsThe tickets on sale for one event on XP: section, row, quantity and the all-in price per ticket in dollars (per_ticket_usd), filterable by quantity, price, section, general admissi…Reads text others writeNo findings

    Why it is in this group

    • The name "get_ticket_listings" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe name "get_ticket_listings" says "get" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    The tickets on sale for one event on XP: section, row, quantity and the all-in price per ticket in dollars (per_ticket_usd), filterable by quantity, price, section, general admission and parking -- 'cheap seats', 'parking for the game'. event_id comes from search_events, search_market or get_event_details; each listing's uvid is what buy_tickets takes. error_code NO_INVENTORY: the event has nothing listed right now, and retrying will not change that. NO_MATCHING_TICKETS: tickets exist but none fit the filters. EVENT_NOT_FOUND: the event_id is wrong.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_user_accountThe caller's XP account as shown on the XP account page: name, email, wallet, order history and referral stats -- 'my account', 'my referral link', 'how much have I spent?'.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_user_account" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    The caller's XP account as shown on the XP account page: name, email, wallet, order history and referral stats -- 'my account', 'my referral link', 'how much have I spent?'. Order status is in get_my_orders; delivered tickets are in get_my_tickets. Requires sign-in.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • get_venue_detailsOne venue on XP and its upcoming events with all-in prices -- 'what's playing at the Garden this month?'.No findings

    Why it is in this group

    • The name "get_venue_details" says "get": a word for reading.
    Description, as the server wrote it
    One venue on XP and its upcoming events with all-in prices -- 'what's playing at the Garden this month?'. venue_id comes from search_venues. Tickets to one of those events are in get_ticket_listings.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • list_muted_listingsThe listing identifiers the caller has muted on XP -- 'what have I hidden?'.No findings

    Why it is in this group

    • The name "list_muted_listings" says "list": a word for reading.
    Description, as the server wrote it
    The listing identifiers the caller has muted on XP -- 'what have I hidden?'. Muting is a per-user view setting and does not change the listing itself. Muted listings are left out of list_open_listings and hidden on xp.tickets; get_market_read counts every fan listing, muted or not. Requires sign-in.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • list_my_listingsThe caller's own listings on XP, grouped by lifecycle category (active, pending, has_open_bids, awaiting_seller_transfer_proof and more) -- 'show the tickets I'm selling'.Reads text others writeNo findings

    Why it is in this group

    • The name "list_my_listings" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    The caller's own listings on XP, grouped by lifecycle category (active, pending, has_open_bids, awaiting_seller_transfer_proof and more) -- 'show the tickets I'm selling'. Paged per category: each category returns one page with its own pagination totals, has_more marks a further page, and offset pages on or state_category narrows to one category. Requires sign-in and the read:bids scope.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • list_my_open_offersThe caller's open offers on XP that are still live -- 'what offers do I have out?'.No findings

    Why it is in this group

    • The name "list_my_open_offers" says "list": a word for reading.
    Description, as the server wrote it
    The caller's open offers on XP that are still live -- 'what offers do I have out?'. An open offer buys at the caller's price whenever a matching fan listing appears. Filled offers show up as tickets in get_my_tickets; filled and rescinded offers are read by id with get_open_offer. Requires sign-in.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • list_open_listingsFan listings on XP open to offers, filterable by event, performer and whole-listing amount -- 'what's open near me this weekend?'.No findings

    Why it is in this group

    • The name "list_open_listings" says "list": a word for reading.
    Description, as the server wrote it
    Fan listings on XP open to offers, filterable by event, performer and whole-listing amount -- 'what's open near me this weekend?'. Listings the caller muted are left out. Each listing's identifier is what get_open_listing and buy_listing_now take; buy_listing_now buys a listing outright at its asking price. Event inventory at listed prices is in get_ticket_listings. Requires sign-in and the read:bids scope.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • resolve_intentFind the XP event a post means, from the words it uses.Reads text others writeNo findings

    Why it is in this group

    • The name "resolve_intent" says "resolve": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "find" and "post": it reads posts, which other people can write.
    Description, as the server wrote it
    Find the XP event a post means, from the words it uses. XP decides the match, not the reader. Returns ranked candidates [{event_id, name, venue, city, date_utc, score (0-1), why, facts: {country, hours_until (null when the date or time is TBD), date_tbd, started, same_day}}], `ambiguous` (why no single event wins, e.g. "3 nights at Sphere", else null), `match` (matched, ambiguous or not_in_catalog: only whether XP found the event). A postponed event or a date more than two years out counts as TBD. Parking listings and cancelled events never match, and a tribute, themed or inspired show or a season-ticket package matches only when the post says so. An upcoming, certain show beats a past or if-necessary one unless the post names that date. same_day means within 24 hours, or today at the venue when only the time is TBD. Duplicate listings resolve to one event.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • search_eventsFind events in XP's catalog (concerts, sports, theater, comedy) by performer, team, venue, city or keyword, with optional date, metro and genre filters -- 'shows near me this weeke…No findings

    Why it is in this group

    • The name "search_events" says "search": a word for reading.
    Description, as the server wrote it
    Find events in XP's catalog (concerts, sports, theater, comedy) by performer, team, venue, city or keyword, with optional date, metro and genre filters -- 'shows near me this weekend', 'Taylor Swift tour dates'. Returns event cards with an all-in price preview. search_market runs the same search and adds what each event is trading at; search_performers and search_venues find a performer or venue on its own.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • search_marketThe same event search as search_events, plus what each event is trading at on XP: its all-in get-in price per ticket and how many fan listings are open to offers on it -- 'tickets …Reads text others writeNo findings

    Why it is in this group

    • The name "search_market" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    The same event search as search_events, plus what each event is trading at on XP: its all-in get-in price per ticket and how many fan listings are open to offers on it -- 'tickets to the season opener', 'seats near me under $100'. Suits questions where price is part of the ask; search_events suits finding an event. The fan listings themselves are in list_open_listings.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • search_performersFind a performer (artist, team or comedian) on XP by name, with optional genre or sport filters -- 'Phish', 'the Lakers'.No findings

    Why it is in this group

    • The name "search_performers" says "search": a word for reading.
    Description, as the server wrote it
    Find a performer (artist, team or comedian) on XP by name, with optional genre or sport filters -- 'Phish', 'the Lakers'. Returns performer cards, not events; search_events with the performer's name returns their upcoming events.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true
  • search_venuesFind a venue on XP by name, city, state or metro -- 'arenas in Brooklyn', 'venues near me'.No findings

    Why it is in this group

    • The name "search_venues" says "search": a word for reading.
    Description, as the server wrote it
    Find a venue on XP by name, city, state or metro -- 'arenas in Brooklyn', 'venues near me'. Returns venue records, not events; get_venue_details returns a venue's upcoming events.

    Annotations the server declares

    • destructiveHint: false
    • openWorldHint: false
    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write15
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:19 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
10
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://mcp.xp.tickets/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.xp.tickets
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 10 tools that change things (8 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.xp.tickets/mcp: tools/list returned 36 tools to an anonymous client, including buy_tickets (destructive), accept_offer (destructive), reject_offer (destructive), cancel_my_offer (destructive), cancel_my_open_offer (destructive) and 5 more

    What this check looks for

Posture changes

  1. Nov 6, 2026
    • Tools that change things, listed without credentials: 17 to 10
  2. Oct 29, 2026
    • Tools that change things, listed without credentials: 12 to 17

Findings

Matches of fixed checks, with the text they matched.

1 warn3 info
  • The description contains "every other tool", wording about other tools or servers.

    Matched text

    description: "...r on every MCP request, exactly like on every other tool call for this job. A missing/invalid he..."

    What this check looks for
  • The description mentions "credential".

    Matched text

    description: "..., sent in params._meta['org.paymentauth/credential'] or as payment_credential. Requires si..."

    What this check looks for
  • The input schema at properties.payment_credential.description mentions "credential".

    Matched text

    inputSchema.properties.payment_credential.description: "rail='mpp' only. JSON MPP credential, as a fallback for clients that cannot..."

    What this check looks for
  • The description is 3,938 characters long, over the 2,000 this check looks for.

    Matched text

    description ends: "...r": "status_unavailable"} - backend down/slow/non-200"

    What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools35 changed.~35 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 17 -> 10.View diff
    • Tools that change things, listed without credentials: 17 to 10
  3. Tools5 added, 9 removed, 23 changed.+5 added−9 removed~23 changedView diff
  4. PostureRemote posture changed. Tools that change things, listed without credentials: 12 -> 17.View diff
    • Tools that change things, listed without credentials: 12 to 17

Install

Pinned to version 4.0.9. Values in angle brackets are yours to fill in.

claude mcp add --transport http xp-tickets https://mcp.xp.tickets/mcp
claude mcp add --transport http xp-tickets https://mcp.xp.tickets/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__xp-tickets__search_events",
      "mcp__xp-tickets__get_event_details",
      "mcp__xp-tickets__search_performers",
      "mcp__xp-tickets__get_ticket_listings",
      "mcp__xp-tickets__search_venues",
      "mcp__xp-tickets__get_venue_details",
      "mcp__xp-tickets__resolve_intent",
      "mcp__xp-tickets__search_market",
      "mcp__xp-tickets__get_market_read",
      "mcp__xp-tickets__get_recent_sales",
      "mcp__xp-tickets__get_price_history",
      "mcp__xp-tickets__get_seat_map",
      "mcp__xp-tickets__get_user_account",
      "mcp__xp-tickets__auth_status",
      "mcp__xp-tickets__get_my_orders",
      "mcp__xp-tickets__get_order_status",
      "mcp__xp-tickets__get_my_tickets",
      "mcp__xp-tickets__get_my_wallet",
      "mcp__xp-tickets__list_open_listings",
      "mcp__xp-tickets__get_open_listing",
      "mcp__xp-tickets__get_my_listing_status",
      "mcp__xp-tickets__list_my_listings",
      "mcp__xp-tickets__get_my_offers",
      "mcp__xp-tickets__list_muted_listings",
      "mcp__xp-tickets__list_my_open_offers",
      "mcp__xp-tickets__get_open_offer"
    ],
    "ask": [
      "mcp__xp-tickets__check_listing",
      "mcp__xp-tickets__mute_listing"
    ],
    "deny": [
      "mcp__xp-tickets__buy_tickets",
      "mcp__xp-tickets__accept_offer",
      "mcp__xp-tickets__reject_offer",
      "mcp__xp-tickets__cancel_my_offer",
      "mcp__xp-tickets__cancel_my_open_offer",
      "mcp__xp-tickets__buy_listing_now",
      "mcp__xp-tickets__create_listing",
      "mcp__xp-tickets__cancel_my_listing"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as xp-tickets. Review it before you use it.

Capability tags behind 15 rules
  • mcp__xp-tickets__get_ticket_listings untrusted-input
  • mcp__xp-tickets__resolve_intent untrusted-input
  • mcp__xp-tickets__search_market untrusted-input
  • mcp__xp-tickets__get_market_read untrusted-input
  • mcp__xp-tickets__get_recent_sales untrusted-input
  • mcp__xp-tickets__get_price_history untrusted-input
  • mcp__xp-tickets__get_user_account private-data, untrusted-input
  • mcp__xp-tickets__auth_status untrusted-input
  • mcp__xp-tickets__get_my_orders untrusted-input
  • mcp__xp-tickets__get_order_status untrusted-input
  • mcp__xp-tickets__get_my_tickets untrusted-input
  • mcp__xp-tickets__get_open_listing untrusted-input
  • mcp__xp-tickets__get_my_listing_status untrusted-input
  • mcp__xp-tickets__list_my_listings untrusted-input
  • mcp__xp-tickets__get_open_offer untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/tickets.xp/xp-tickets/verify?hash=be1bb6f6350f1591c496135ba09460671d93aea52ad1f1a0b38e6b765bc2a119" | jq -e '.changed == false'

Pinned hash be1bb6f6350f, from Nov 19, 2026, 06:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/tickets.xp/xp-tickets/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for tickets.xp/xp-tickets
[![Anlyon Radar](https://radar.anlyon.com/badge/tickets.xp/xp-tickets.svg)](https://radar.anlyon.com/servers/tickets.xp/xp-tickets)

Source: MCP Registry. Synced Oct 21, 2026, 18:55 UTC.

XP Tickets MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the XP Tickets MCP server safe?

No scan can promise that. What its definitions show: 36 tools, 10 of which can change, send or delete something, and 4 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the XP Tickets MCP server delete data?

Yes. 8 tools can delete, cancel or revoke something: buy_tickets, accept_offer, reject_offer, cancel_my_offer, cancel_my_open_offer, buy_listing_now and 2 more.

Can the XP Tickets MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the XP Tickets MCP server have?

36 tools: 8 destructive, 2 write, 26 read. buy_tickets, accept_offer, reject_offer, cancel_my_offer, cancel_my_open_offer, buy_listing_now, create_listing, cancel_my_listing and 28 more.

Does the XP Tickets MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the XP Tickets MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the XP Tickets MCP server changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 19, 2026. Every change is on this page and in its Atom feed.