MCP servers › tickets.xp › xp-tickets

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

tickets.xp/xp-tickets

Live-event ticket exchange for agents: quote, buy, make offers, bid, and sell, with escrow. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: commerce-and-marketing · AI-classifiedversion 4.0.9streamable HTTP40 tools

Summary

tickets.xp/xp-tickets is a remote MCP server listed in the official MCP registry at version 4.0.9. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 40 tools, 11 resources and 6 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

met: Registry entry is active and says how to run it
not met: Source repository link opens
not applicable: Repository is not archived
not applicable: Code pushed to the repository in the 90 days before our check
not applicable: Repository publishes a security policy (SECURITY.md)
not applicable: Package names its licence with a standard (SPDX) identifier
not applicable: The version the registry lists can be installed and is not withdrawn
not applicable: npm package carries build provenance (attestation)
not applicable: No known critical or high advisory in the package or its dependencies

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs: remote (hosted by the publisher)
Transport: streamable HTTP
Sign-in: none needed to open a session
Tools: 40
Described as changing data: 11 of 40 toolsAI-classified
Mainly works on: accounts and data in outside web servicesAI-classified
Topic: commerce-and-marketingAI-classified
Last tested: 2026-10-23

Add to your client

Observed fact

This server accepted a session without any credential and lists 10 tools whose name or declaration suggests they change data (buy_tickets, make_offer_on_listing, accept_offer, reject_offer, cancel_my_offer and 5 more). That is our reading of the names; we did not call them. Source: our connection, 2026-10-23.

Worth knowing before you connect it

11 tools are described as changing something (buy_tickets, make_offer_on_listing, accept_offer, …): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call them.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested: yes, a real session (not a text-only review)
Last tested: 2026-10-23
Mode: read-only (no tool calls)
Latest version: 4.0.9, published 2026-10-09 (registry, as of the 2026-10-23 snapshot)
First listed version: 2026-10-09 (earliest version still in the registry; older removed versions would be earlier)
Registry data: snapshot 2026-10-23
Package and repository: checked 2026-10-23
Engine: mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 4.0.9 (published 2026-10-09).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory

40tools

11resources

6prompts

What it mainly works on, as our AI model read its tool descriptions: accounts and data in outside web services.

11 of 40 tools are described as changing something (creating, editing, deleting, sending or running).

search_eventson 68 other serversreads or searches
“Use when the user wants to find live events on XP — concerts, sports, theater — by performer, team, venue, city, or keyword (e.g.”
Publisher declares: read-only yes · destructive no · open-world yes
7 inputs, 1 required
- querystringrequired“Natural language event search query.”
- limitinteger“Maximum number of events to return.”
- min_datestring or null“Filter events on or after this date (YYYY-MM-DD).”
- max_datestring or null“Filter events on or before this date (YYYY-MM-DD).”
- cbsastring or null“Metro area filter (synonyms: city, near me, area).”
- genrestring or null“Genre filter.”
- include_scoresboolean“Include similarity scores for debugging.”
get_event_detailson 10 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- event_idintegerrequired“Event ID from search_events or a previous user selection (e.g.”
search_performerson 1 other serverreads or searches
“Find a performer (artist, team, comedian) on the XP marketplace by name.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs, 1 required
- querystringrequired“Natural language performer search query.”
- limitinteger“Max performers to return.”
- min_similaritynumber“Minimum similarity score for the semantic match.”
- genrestring or null“Optional genre filter.”
- sportstring or null“Optional sport filter (NBA, NFL, etc.).”
- include_scoreboolean“Include similarity scores for debugging.”
get_ticket_listingsreads or searches
“Use when the user wants to see ticket options and fee-inclusive prices for a specific XP event after `search_events` (e.g.”
Publisher declares: read-only yes · destructive no · open-world yes
17 inputs
- event_idinteger or null“Event identifier from search_events or get_event_details.”
- quantityinteger“Number of tickets requested.”
- limitinteger“Maximum ticket listings to return.”
- sectionsarray or string or null“Alias for section_ids.”
- tagsarray or string or null“Alias for section_tags.”
- min_price_usdnumber or null“Minimum all-in price per ticket in dollars.”
- max_price_usdnumber or null“Maximum all-in price per ticket in dollars.”
- min_price_centsinteger or null“Deprecated, use min_price_usd.”
- max_price_centsinteger or null“Deprecated, use max_price_usd.”
- order_bystring or null“Price sort order.”
- offsetinteger or null“Pagination offset.”
- api_limitinteger or null“Backend limit (advanced; usually omit).”
- section_idsstring or null“Section IDs filter (list, comma-separated string, or numeric IDs; supports simple ranges like '100-110').”
- section_tagsstring or null“Section tags filter (e.g.”
- is_gaboolean or null“If true, filter for general admission only.”
- parking_onlyboolean or null“If true, return only parking tickets.”
- max_cache_levelinteger or null“Backend cache level override (advanced; usually omit).”
buy_ticketsmoves moneydescribed as changing data
“Use when the user wants tickets to an event on the XP marketplace (connected order book).”
Publisher declares: read-only no · destructive yes · open-world no
9 inputs, 3 required
- event_idintegerrequired“Event identifier from search_events or get_event_details.”
- uvidstringrequired“Ticket group UVID from get_ticket_listings.”
- quantityintegerrequired“Number of tickets to purchase.”
- confirmboolean“Must be true to execute.”
- railstring“Payment rail.”
- payment_proofstring“Required only for rail='x402' when confirm=True.”
- facilitatorstring“rail='x402' only.”
- payment_credentialstring or object“rail='mpp' only.”
- checkout_session_idstring“rail='stripe_link' only, with confirm=true.”
search_venueson 17 other serversreads or searches
“Use when the user wants to find a venue by name, city, or area on XP (e.g.”
Publisher declares: read-only yes · destructive no · open-world yes
5 inputs, 1 required
- querystringrequired“Venue name or search term.”
- citystring or null“Optional city filter (synonyms: near me, area).”
- statestring or null“Optional state abbreviation (e.g.”
- metrostring or null“Optional metro area filter (synonyms: city, near me, area).”
- limitinteger“Maximum venues to return.”
get_venue_detailson 2 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- venue_idintegerrequired“Venue identifier from search_venues.”
check_listingon 12 other serversreads or searches
“Poll the current status and action feed for the listing tied to this call's correlation id.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input
- sinceinteger or null“Cursor from the previous call's `cursor` field.”
search_marketon 3 other serversreads or searches
“Use when the user is shopping and might make an offer rather than pay the asking price.”
Publisher declares: read-only yes · destructive no · open-world yes
6 inputs, 1 required
- querystringrequired“Natural language event search query.”
- limitinteger“Maximum number of events to return.”
- min_datestring or null“Filter events on or after this date (YYYY-MM-DD).”
- max_datestring or null“Filter events on or before this date (YYYY-MM-DD).”
- cbsastring or null“Metro area filter (synonyms: city, near me, area).”
- genrestring or null“Genre filter.”
get_market_readon 1 other serverreads or searches
“Use when the user wants to understand what an event is trading at, not just browse rows.”
Publisher declares: read-only yes · destructive no · open-world yes
3 inputs, 1 required
- event_idintegerrequired“Event identifier from search_market or search_events.”
- quantityinteger“Party size; filters to groups a buyer can actually transact at.”
- sectionsarray or null“Section names the user named, to report on specifically.”
get_recent_saleson 2 other serversreads or searches
“Use when the user asks what tickets actually sold for on an event, or before claiming nothing has traded.”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- event_idintegerrequired“Event identifier from search_market or search_events.”
get_price_historyon 74 other serversreads or searches
“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.”
Publisher declares: read-only yes · destructive no · open-world yes
2 inputs, 1 required
- event_idintegerrequired“Event identifier from search_market or search_events.”
- daysinteger“Window in days, 1-90.”

Show 28 more tools

get_my_contexton 1 other serverreads or searches
“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.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- event_idsarrayrequired“Event IDs the user has settled on.”
get_seat_mapreads or searches
“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 s…”
Publisher declares: read-only yes · destructive no · open-world yes
1 input, 1 required
- event_idintegerrequired“Event identifier from search_market, search_events or get_event_details.”
get_user_accountreads or searches
“Pull the authenticated user's XP marketplace account card — profile, wallet, email, name, order history, and referral stats.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
auth_statuson 36 other serversreads or searches
“Use ONLY when the user explicitly asks whether they are signed in to the XP marketplace (e.g.”
Publisher declares: read-only yes · destructive no · open-world yes
Takes no inputs.
get_my_orderson 3 other serversreads or searches
“Show the authenticated user their own orders on the XP marketplace and where each one stands.”
Publisher declares: read-only yes · destructive no · open-world no
1 input
- limitinteger or null“How many recent orders to return, 1-50.”
get_order_statuson 51 other serversreads or searches
“Get the status of one of the authenticated user's orders on the XP marketplace, by the order_uuid that buy_tickets returned.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- order_uuidstringrequired“The order_uuid returned by buy_tickets (or listed by get_my_orders).”
get_my_ticketsreads or searches
“Show the authenticated user the tickets currently delivered to their XP marketplace account, all backed by XP's Quality XPerience Guarantee.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
- limitinteger or null“How many tickets to return, 1-200.”
- offsetinteger“Skip this many.”
list_my_favoriteson 1 other serverreads or searches
“Use when an authenticated user wants the performers they've favorited on the XP marketplace (e.g.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
- limitinteger or null“How many favorites to return, 1-200.”
- offsetinteger“Skip this many.”
get_my_walletreads or searches
“Use when an authenticated user wants their XP marketplace Privy embedded-wallet address and USDC balance (e.g.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
get_my_referral_kickbacksreads or searches
“Use when an authenticated user wants their XP marketplace referral kickback totals and rows (e.g.”
Publisher declares: read-only yes · destructive no · open-world no
4 inputs
- referral_startstring or null“Optional referral-window start (YYYY-MM-DD).”
- referral_endstring or null“Optional referral-window end (YYYY-MM-DD).”
- order_startstring or null“Optional order-window start (YYYY-MM-DD).”
- order_endstring or null“Optional order-window end (YYYY-MM-DD).”
list_open_listingsreads or searches
“From XP's connected resale + primary order book.”
Publisher declares: read-only yes · destructive no · open-world no
11 inputs
- daysinteger“Only include offers created within this many days.”
- sort_bystring“Sort field: created_at, event_date, amount, state, updated_at.”
- sort_orderstring“Sort direction.”
- sell_to_xpboolean“If true, only offers where sell_to_xp is true.”
- event_namestring or null“Filter by event title substring.”
- performerstring or null“Filter by performer name substring.”
- min_amount_usdnumber or null“Minimum total for the whole listing in dollars (all its tickets together), not per ticket.”
- max_amount_usdnumber or null“Maximum total for the whole listing in dollars (all its tickets together), not per ticket.”
- min_amountinteger or null“Deprecated, use min_amount_usd.”
- max_amountinteger or null“Deprecated, use max_amount_usd.”
- limitinteger“Max offers to return after fetch.”
get_open_listingreads or searches
“From XP's connected resale + primary order book.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- identifierstringrequired“Public listing identifier from list_open_listings.”
get_my_listing_statuson 1 other serverreads or searches
“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.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- identifierstringrequired“Public listing identifier from create_listing (listing_identifier), list_open_listings or list_my_listings.”
list_my_listingson 5 other serversreads or searches
“Paged: a large book comes back one page per lifecycle category, and the result carries pagination totals per category.”
Publisher declares: read-only yes · destructive no · open-world no
3 inputs
- state_categorystring or null“Optional: active, pending, has_open_bids, awaiting_seller_transfer_proof, needs_user_attention, ready_to_claim, rejected_bids, terminal.”
- limitinteger or null“Listings per state category, 1-200.”
- offsetinteger“Skip this many within each category.”
get_my_bidsreads or searches
“Use when an authenticated user wants to see the bids they have placed on the XP marketplace — e.g.”
Publisher declares: read-only yes · destructive no · open-world no
2 inputs
- limitinteger or null“How many bids to return, 1-200.”
- offsetinteger“Skip this many.”
make_offer_on_listingdescribed as changing data
“From XP's connected resale + primary order book.”
Publisher declares: read-only no · destructive yes · open-world no
4 inputs, 1 required
- listing_identifierstringrequired“Public listing identifier from list_open_listings.”
- amount_per_ticket_usdnumber or null“Whole dollars per ticket (50 = $50.00), the same unit create_standing_bid takes.”
- amount_centsinteger or null“Deprecated, use amount_per_ticket_usd.”
- confirmboolean“Defaults to false, a preview of the computed total.”
accept_offeron 10 other serversdescribed as changing data
“ACCEPTING SELLS TO A BUYER AND STARTS A CLOCK: the offer comes from a buyer on XP, not from XP.”
Publisher declares: read-only no · destructive yes · open-world no
3 inputs, 3 required
- identifierstringrequired“Public listing identifier from list_my_listings or get_my_listing_status.”
- offer_uuidstringrequired“Offer UUID from get_my_listing_status open_offers.”
- confirmbooleanrequired“Required.”
reject_offerdescribed as changing data
“From XP's connected resale + primary order book.”
Publisher declares: read-only no · destructive yes · open-world no
3 inputs, 3 required
- identifierstringrequired“Public listing identifier from list_my_listings or get_my_listing_status.”
- offer_uuidstringrequired“Offer UUID from get_my_listing_status open_offers.”
- confirmbooleanrequired“Required.”
cancel_my_offerdescribed as changing data
“From XP's connected resale + primary order book.”
Publisher declares: read-only no · destructive yes · open-world no
3 inputs, 3 required
- identifierstringrequired“Public listing identifier the offer was placed on.”
- offer_uuidstringrequired“Identifier of the offer to cancel.”
- confirmbooleanrequired“Required.”
list_muted_listingsreads or searches
“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.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
mute_listingcreates or changes datadescribed as changing data
“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.g.”
Publisher declares: read-only no · destructive no · open-world no
2 inputs, 1 required
- listing_identifierstringrequired“Listing identifier from list_open_listings or get_open_listing.”
- mutedboolean“True to mute (hide it from the user's marketplace feed), False to unmute.”
list_my_standing_bidsreads or searches
“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.”
Publisher declares: read-only yes · destructive no · open-world no
Takes no inputs.
get_standing_bidreads or searches
“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'.”
Publisher declares: read-only yes · destructive no · open-world no
1 input, 1 required
- standing_bid_idstringrequired“Standing offer id from list_my_standing_bids or create_standing_bid.”
create_standing_bidcreates or changes datadescribed as changing data
“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.”
Publisher declares: read-only no · destructive yes · open-world no
6 inputs, 4 required
- event_idsarrayrequired“Event ids this offer may fill on, from search_market or search_events.”
- sectionsarrayrequired“Section names the offer covers, e.g.”
- amount_per_ticket_usdnumberrequired“Whole dollars per ticket.”
- quantityintegerrequired“How many tickets the offer is good for.”
- confirmboolean“False (default) previews without committing.”
- expires_atstring or null“Optional ISO-8601 UTC expiry.”
rescind_standing_biddeletesdescribed as changing data
“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.”
Publisher declares: read-only no · destructive yes · open-world no
2 inputs, 1 required
- standing_bid_idstringrequired“Standing offer id from list_my_standing_bids.”
- confirmboolean“False (default) previews.”
buy_listing_nowmoves moneydescribed as changing data
“From XP's connected resale + primary order book.”
Publisher declares: read-only no · destructive yes · open-world no
4 inputs, 1 required
- identifierstringrequired“Listing identifier from list_open_listings or get_open_listing.”
- railstring“How to pay.”
- ask_per_ticket_usdnumber or null“The per-ticket price the preview showed (its ask_per_ticket_usd).”
- confirmboolean“False (default) previews.”
create_listingon 23 other serverscreates or changes datadescribed as changing data
“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'.”
Publisher declares: read-only no · destructive no · open-world no
12 inputs, 5 required
- event_idintegerrequired“Event identifier from search_market or search_events.”
- quantityintegerrequired“How many tickets are being listed together.”
- is_adabooleanrequired“Required.”
- is_obstructed_viewbooleanrequired“Required.”
- is_srobooleanrequired“Required.”
- sectionstring or null“Section name exactly as the venue prints it, e.g.”
- rowstring or null“Row, e.g.”
- gaboolean“True for general admission with no seat numbers.”
- first_seatinteger or null“First seat number, if seated.”
- last_seatinteger or null“Last seat number, if seated.”
- ask_per_ticket_usdnumber or null“Optional asking price per ticket in dollars.”
- confirmboolean“False (default) previews.”
cancel_my_listingdeletesdescribed as changing data
“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'.”
Publisher declares: read-only no · destructive yes · open-world no
2 inputs, 1 required
- listing_identifierstringrequired“Listing identifier from list_my_listings or create_listing.”
- confirmboolean“False (default) previews.”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does: 100% of 40 tools
Says what it returns: 100% of 39 tools
States limits, defaults or errors: 32% of 37 tools
Says when to use it: 100% of 40 tools
Items covered per tool: 3.4 of 4 on average

Counted from the listing

Parameters with a description: 100% of 131
Tools with a description: 100% of 40
Typical description length: 669 characters

The tool set

Counted from the listing

Tools: 40
Size of the list: about 15,415 tokens for an agent to load (characters ÷ 4)
Naming: 40 of 40 names use snake_case

AI reading: easy to mix up

search_events and search_market
get_event_details and get_venue_details
get_ticket_listings and get_market_read
make_offer_on_listing and buy_listing_now

The AI items cover 40 of 40 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found these. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai

Settings → Connectors → Add custom connector, then paste:
https://mcp.xp.tickets/mcp

Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json

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

VS Code · .vscode/mcp.json

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

VS Code (command line) · Bash or zsh terminal (macOS, Linux)

code --add-mcp '{"name":"xp-tickets","type":"http","url":"https://mcp.xp.tickets/mcp"}'

Claude Code

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

Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+

npx @modelcontextprotocol/inspector@2.11.0 --server-url https://mcp.xp.tickets/mcp --transport http

The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry says	We found	Result	Source · date
Remote endpoint mcp.xp.tickets/mcp	Session opened	matches	our test · 2026-10-23
No credential declared as required	Opened a session without any credential	matches	our test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

Not ranked by downloads: a remote server publishes no download figure
Not ranked by stars: no public GitHub repository

MetRegistry entry is active and says how to run itActive, with a package or a remote address.
Not metSource repository link opensThe registry entry gives no repository link.
Does not applyRepository is not archivedNo public GitHub repository to read.
Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-23. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about tickets.xp/xp-tickets

Answered from the data above

Is tickets.xp/xp-tickets safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 11 of its tools describe changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does tickets.xp/xp-tickets need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has tickets.xp/xp-tickets been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security verdict is published before verification.

What can tickets.xp/xp-tickets do?

It lists 40 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, create or change data, delete and move money. We did not call any tool, so this describes the text, not the behaviour.

Can tickets.xp/xp-tickets change or delete data?

11 of its tools say in their description that they create, edit, delete, send or run something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

io.github.Dudude-bit/yandex-lavka-mcpalso has tools that creates or changes data, deletes, moves money, reads or searchescompare with this one
app.himalayas/mcpHimalayas Remote Jobsalso has tools that creates or changes data, deletes, moves money, reads or searchescompare with this one
io.github.YawLabs/lemonsqueezy-mcpLemonSqueezy MCP Serveralso has tools that creates or changes data, deletes, moves money, reads or searchescompare with this one
io.github.markswendsen-code/ubereatsalso has tools that creates or changes data, deletes, moves money, reads or searchescompare with this one
io.github.hermoso-ai/hermosoHermosoalso has tools that creates or changes data, deletes, moves money, reads or searchescompare with this one
io.github.the402ai/mcp-serveralso has tools that creates or changes data, deletes, moves money, reads or searchescompare with this one

Active servers whose topic is also “commerce-and-marketing” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Open without sign-in

It accepted a session without any credential and lists tools whose names suggest they change data. We did not call them. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23

Inventory: exercised
Hidden instructions: exercised
Real execution: not run · our policy
Secret leak: not run · nothing to check it against
Internal addresses: not run · our policy
Unconfirmed changes: not run · our policy
Bad input: not run · our policy
Model requests: not run · nothing to check it against
Sensitive questions: not run · nothing to check it against
Folder boundary: not run · our policy
Log leaks: not run · nothing to check it against
Hidden content: exercised
Fake assistant turns: exercised
Token passthrough: not applicable
Token audience: not applicable
Sign-in redirect: not run · our policy
Consent handling: not testable from outside
Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5

1Inventory
tool-listReads the declared tools, resources and prompts.exercised
2Hidden instructions
description-poisoningLooks for hidden instructions in tool descriptions.exercised
12Hidden content
audience-hidingChecks resources that hide content from the user.exercised
13Fake assistant turns
fake-assistant-turnChecks prompts that pose as the assistant's own words.exercised
18Sign-in metadata
oauth-url-schemeChecks the published sign-in metadata for unsafe URLs.exercised

Not run, with the reason · 11

3Real execution
real-executionCalls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
4Secret leak
canary-leakPlants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
5Internal addresses
ssrfChecks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
6Unconfirmed changes
write-without-confirmationChecks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
7Bad input
error-handlingSends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
8Model requests
samplingChecks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
9Sensitive questions
elicitation-sensitive-dataChecks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
10Folder boundary
root-boundaryChecks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
11Log leaks
logging-side-channelChecks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
16Sign-in redirect
open-redirectChecks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
17Consent handling
confused-deputyChecks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside

Does not apply to this server · 2

14Token passthrough
token-passthroughChecks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
15Token audience
token-audience-validationChecks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

0 msStarted a read-only session with the server's remote endpoint
2,194 msConnected after 0 redirects. No credential was sent or needed.
Read the inventory: 40 tools, 11 resources, 6 prompts.
11,573 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified

commerce-and-marketing

AI-classified · 2026-10-23

Pricing modelAI-classified

no value

No value: the AI answer was held back because the quoted text did not clearly support it.

Programming language

does not apply

no existing GitHub repository (server declares no repository link, so there is nothing to fetch)

Hosting type

remote (hosted by the publisher)

registry · 2026-10-23

MCP capability

logging, prompts, resources, tools

our test · 2026-10-23

Transport

streamable HTTP

registry · 2026-10-23

Required credentials

none declared

registry · no declaration is not a guarantee

Package registry

does not apply

remote-only server: no package is shipped, so there is no package registry

Freshness

0–30 days

registry updatedAt · 2026-10-23

Lifecycle status

active

registry · 2026-10-23

License class

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Integrity hash

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Signature / provenance

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Dependency advisories

does not apply

ships no package, so there are no dependencies to audit

Popularity

does not apply

remote-only server: ships no package, so there is nothing to look up in a package registry

Publisher signals

not stated

no readable GitHub owner to describe

Maintenance

does not apply

server declares no repository link, so there is nothing to fetch

Environment

the publisher's infrastructure

where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “tickets.xp/xp-tickets: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/tickets.xp/xp-tickets

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/tickets.xp/xp-tickets)](https://protocolprobe.com/mcp/servers/tickets.xp/xp-tickets)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology