Home / MCP registry index / tickets.xp/xp-tickets

XP Tickets

tickets.xp/xp-tickets in the official MCP registry. Endpoint https://mcp.xp.tickets/mcp.

The registry describes it as: Live-event ticket exchange for agents: quote, buy, make offers, bid, and sell, with escrow.

We read its 44 tools on 2026-10-31. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

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

Cursor: ~/.cursor/mcp.json

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

VS Code

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

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard

claude plugin marketplace add jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

search_events get_event_details search_performers get_ticket_listings buy_tickets search_venues get_venue_details check_listing get_listening_assignment submit_seller_leads submit_discovered_sources add_my_sources get_discovery_plan search_market get_market_read get_recent_sales get_price_history get_my_context get_seat_map get_user_account auth_status get_my_orders get_order_status get_my_tickets list_my_favorites get_my_wallet list_open_listings get_open_listing get_my_listing_status list_my_listings get_my_bids make_offer_on_listing accept_offer reject_offer cancel_my_offer list_muted_listings mute_listing list_my_standing_bids get_standing_bid create_standing_bid rescind_standing_bid buy_listing_now create_listing cancel_my_listing

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-10-31): ec228a2cc1c581b1. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/tickets-xp-xp-tickets/badge.svg)](https://lazaretto.dev/mcp-registry/tickets-xp-xp-tickets)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.