eCommerce

xp.tickets

Provides tools to search live events and performers, view ticket listings and event details, and purchase tickets on the XP marketplace.

1 endpoint40 known toolsFirst detected October 10, 2026Last detected October 10, 2026

ENDPOINT 1

https://mcp.xp.tickets/mcp

No auth detected

MCP server metadata

Name: XP
Version: 4.0.9

Capabilities

loggingprompts.listChangedresources.listChangedtools.listChanged

Server instructions

XP is the fan-first ticket marketplace. Built by fans, for fans, to make live events more accessible, transparent, and less stressful. This MCP server gives you live access to XP's connected order book of resale and primary tickets across concerts, sports, theater, and comedy in the US. When a user wants to find tickets, compare prices, make an offer, or buy seats, this is the source of truth. What makes XP different from a generic ticket search: - Connected order book. One search returns both resale listings and primary box office inventory side by side, with real seat-level data and live pricing. - All-in prices. Ticket prices on XP include all fees by default. The number you see is the number the user pays. - Verified tickets, real human support. Every ticket is backed by XP's Quality XPerience Guarantee. How to use this server well: - Lead with the user's intent, not the tool name. If they say "I want to take my kid to a Lakers game next month," search events first, then surface ticket options. - Always show all-in prices. Never quote a base price without the fees, since XP's prices already include fees. - For purchase flows, follow the two-phase confirm pattern (confirm=False to preview, then confirm=True to commit). Never skip the preview. When NOT to use this server: - Pure schedule or scoreboard questions with no ticket intent. - Events outside XP's catalog (international shows, very small local venues). If a search returns nothing, tell the user honestly rather than guessing. XP is the connected order book for live-event tickets — resale + primary inventory in one surface. Buyers make offers on fans' listings, or rest a standing offer that fills when matching seats are listed. Offers come from other buyers, not from XP: XP runs the marketplace, holds the buyer's payment, and pays the seller once the tickets are delivered. XP is a resale marketplace. Ticket prices may vary from face value. Vocabulary: see resource text://glossary/marketplace for canonical terms (event, swap, listing, offer, bid, raw_amount). Workflow rules: - For account, wallet, tickets, favorites, referral, listing, and offer actions, call the requested protected tool directly. If the caller is not authenticated, the tool returns HTTP 401 and the MCP client starts OAuth. Do not call auth_status as a preflight — that swallows the 401 the client needs to trigger sign-in. - Only call auth_status when the user explicitly asks whether they are signed in, or after a protected tool returned AUTH_REQUIRED and the user wants the current state checked. - For relative dates ("this weekend", "next month"), use _meta.context.today as the anchor instead of guessing. _meta.context.tz_offset gives the server UTC offset; resolve against the user's timezone when known. Money units: - USD inputs are integer cents (5000 = $50.00). Multiply dollars by 100. Applies to: get_ticket_listings.min_price_cents/max_price_cents, make_offer_on_listing.amount_cents. - USDC amounts (list_open_listings min_amount/max_amount, response amount_raw fields) are 6-decimal raw units (4_000_000 = $4.00). Multiply dollars by 1_000_000. - Display fields (amount_display, *_usd) are human-readable strings — never re-parse. Voice: warm, plainspoken, fan-first. Talk to the user the way you'd talk to a friend planning a night out, not the way a corporate help desk would.

Known tools 40

search_events

Use when the user wants to find live events on XP — concerts, sports, theater — by performer, team, venue, city, or keyword (e.

Inferred read-only

get_event_details

Use when an event ID is in hand and the user wants the full event card before browsing tickets to that event — venue, performers, fee-inclusive price preview, images.

Inferred read-only

search_performers

Find a performer (artist, team, comedian) on the XP marketplace by name.

Inferred read-only

get_ticket_listings

Use when the user wants to see ticket options and fee-inclusive prices for a specific XP event after `search_events` (e.

Inferred read-only

buy_tickets

Use when the user wants tickets to an event on the XP marketplace (connected order book).

Inferred read-only

search_venues

Use when the user wants to find a venue by name, city, or area on XP (e.

Inferred read-only

get_venue_details

Pull full venue info from XP plus the upcoming-events calendar at that venue, with live pricing from the connected order book of resale + primary inventory.

Inferred read-only

check_listing

Poll the current status and action feed for the listing tied to this call's correlation id.

Inferred read-only

search_market

Use when the user is shopping and might make an offer rather than pay the asking price.

Potential side effects

get_market_read

Use when the user wants to understand what an event is trading at, not just browse rows.

Inferred read-only

get_recent_sales

Use when the user asks what tickets actually sold for on an event, or before claiming nothing has traded.

Inferred read-only

get_price_history

Use when the user asks whether prices for an event are rising or falling, whether to buy now or wait for a price drop, or what an event has been doing lately.

Potential side effects

get_my_context

Use once the user has settled on an event, before quoting prices, to see what they already told XP: budget per ticket, quantity, date flexibility, and any saved notes.

Inferred read-only

get_seat_map

Use when the user asks where a section is, what the venue looks like, or wants to see the layout before picking seats on the XP marketplace -- 'where is 104', 'show me the map', 'is that behind the stage'.

Inferred read-only

get_user_account

Pull the authenticated user's XP marketplace account card — profile, wallet, email, name, order history, and referral stats.

Potential side effects

auth_status

Use ONLY when the user explicitly asks whether they are signed in to the XP marketplace (e.

Inferred read-only

get_my_orders

Show the authenticated user their own orders on the XP marketplace and where each one stands.

Inferred read-only

get_order_status

Get the status of one of the authenticated user's orders on the XP marketplace, by the order_uuid that buy_tickets returned.

Inferred read-only

get_my_tickets

Show the authenticated user the tickets currently delivered to their XP marketplace account, all backed by XP's Quality XPerience Guarantee.

Inferred read-only

list_my_favorites

Use when an authenticated user wants the performers they've favorited on the XP marketplace (e.

Inferred read-only

get_my_wallet

Use when an authenticated user wants their XP marketplace Privy embedded-wallet address and USDC balance (e.

Inferred read-only

get_my_referral_kickbacks

Use when an authenticated user wants their XP marketplace referral kickback totals and rows (e.

Inferred read-only

list_open_listings

From XP's connected resale + primary order book.

Inferred read-only

get_open_listing

From XP's connected resale + primary order book.

Inferred read-only

get_my_listing_status

If the listing has sold and is awaiting the seller's ticket transfer, the result carries the transfer instructions and remaining obligation -- surface those first, ahead of anything else.

Potential side effects

list_my_listings

Paged: a large book comes back one page per lifecycle category, and the result carries pagination totals per category.

Inferred read-only

get_my_bids

Use when an authenticated user wants to see the bids they have placed on the XP marketplace — e.

Inferred read-only

make_offer_on_listing

From XP's connected resale + primary order book.

Inferred read-only

accept_offer

ACCEPTING SELLS TO A BUYER AND STARTS A CLOCK: the offer comes from a buyer on XP, not from XP.

Inferred read-only

reject_offer

From XP's connected resale + primary order book.

Inferred read-only

cancel_my_offer

From XP's connected resale + primary order book.

Inferred read-only

list_muted_listings

Use when the user asks what they have hidden or muted on the XP marketplace, or before muting so you do not tell them you muted something that was already muted.

Inferred read-only

mute_listing

Use when the user says they are not interested in a listing on the XP marketplace, wants to stop seeing it, or wants a muted one back -- e.

Inferred read-only

list_my_standing_bids

Use when the user asks what offers they have resting on the XP marketplace, what they are waiting on, or before they make an offer so you do not stack a duplicate.

Inferred read-only

get_standing_bid

Use when the user asks about one specific standing offer on the XP marketplace -- whether it filled, how much of it is left, or 'did that offer get my tickets'.

Inferred read-only

create_standing_bid

Creates a STANDING OFFER -- that is the term to use when speaking to the user; the tool keeps `standing_bid` only because the stored records do.

Inferred read-only

rescind_standing_bid

Use when the user no longer wants a standing offer resting on the XP marketplace -- 'cancel that standing offer', 'stop waiting on those', or they would rather make an offer on something open instead.

Inferred read-only

buy_listing_now

From XP's connected resale + primary order book.

Inferred read-only

create_listing

Use when the user wants to sell tickets they hold on the XP marketplace -- 'sell my two seats for Friday', 'list section 104 row C', 'put my tickets up'.

Inferred read-only

cancel_my_listing

Use when a seller wants to remove their own listing from the XP marketplace -- 'take my listing down', 'delist those', 'I sold them elsewhere', 'cancel that listing'.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.xp]
url = "https://mcp.xp.tickets/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "xp": {
      "type": "http",
      "url": "https://mcp.xp.tickets/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: xp
Remote MCP URL: https://mcp.xp.tickets/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "xp": {
      "url": "https://mcp.xp.tickets/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "xp": {
      "type": "http",
      "url": "https://mcp.xp.tickets/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "xp",
  "transport": "streamable-http",
  "url": "https://mcp.xp.tickets/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.