Skip to content
TicketSea logo

TicketSea MCP server

Which MCP servers are TicketSea's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-27

← Back to TicketSea

Whose server it is
  • Registry namecom.ticketsea/ticketseaverified in the MCP registry

The registry name sits under ticketsea.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-27
  • Stateanswerschecked 2026-10-27
  • Tools7
  • Server calls itselfticketsea
  • Server version1.5.0
  • Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 277 ms.

Should an agent connect itNot proven either way yet
  • Its tools do every use case we checked: Find concerts, games, and shows happening near you; Compare ticket links from official sellers and resale sites.
  • Checked on 2 of the 7 days it takes to judge reliability.

Once connected

  • For "Find concerts, games, and shows happening near you", the likely first call is search_events.
  • For "Compare ticket links from official sellers and resale sites", the likely first call is get_ticket_links.
  • Parameters are untyped or undescribed in 2 of 7 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 2, the first on 2026-10-27
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 2 so far
  • What an agent can do with it2 of 2 use cases
  • Answeredmeasuring2 of the 7 daily checks it takes to print a share
  • Median first answer407 ms
  • Space in an agent's context≈ 1,694 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsA · 95 of 100
  • Typed results7 of 7 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 2 of 7

What an agent can do with it

  • can do · Find concerts, games, and shows happening near you
  • can do · Compare ticket links from official sellers and resale sites
  • not sure · Track how ticket prices for an event change over time

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers7 tools · read 2026-10-27
  • search_catalog

    Use this when the user names an artist, team, venue or event and you need the matching TicketSea records. Ranked search with prefixes, aliases and labeled one-edit corrections. Artist and venue matches are worldwide; an event radius needs…

  • search_events

    Use this when the user wants upcoming concerts, sports, theatre or other live events by performer or event name, city, country, category or dates. Returns cached provider listings in date order. Each upcoming event has its TicketSea page…

  • get_event

    Use this when you have an event's slug from a search result and need that event's current details: date, local time, venue, sale state, cancellation and any published price range. Returns the newest available snapshot; older details are…

  • get_ticket_links

    Use this when the user wants to buy or compare tickets for one specific event. Returns the exact-event seller links from a fresh, upcoming snapshot (links), each labeled primary or resale, official and affiliate, and the other sellers the…

  • prepare_event_visit

    Use this when the user is planning a trip to one specific event and wants tickets together with a place to stay, parking or directions. One call returns the latest event details, every seller link for the event, the venue address…

  • get_ticket_prices

    Use this when the user asks whether tickets are getting cheaper or pricier, what it costs to get in, which events dropped or rose in price this week, or how an event's price has moved. Returns TicketSea's daily ticket price figures from…

  • get_service_status

    Use this when a search fails or returns nothing unexpectedly and you need to know whether TicketSea's listings are current. Returns the latest snapshot time for each country. This is not a seller uptime or booking success measurement.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "ticketsea": {
      "type": "http",
      "url": "https://ticketsea.com/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http ticketsea https://ticketsea.com/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://ticketsea.com/mcp as a custom connector in the settings.

OpenAPI spec

9 paths, read 2026-10-27. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.