StubHub

Search StubHub's live event catalog and browse resale ticket listings from an AI agent.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the StubHub connector does

The StubHub MCP server connects the resale ticket marketplace to Claude, ChatGPT and any MCP-compatible agent. Three tools search StubHub's event catalog, pull live listings for one event, and expand a single listing. All three read. Nothing here buys a ticket, and nothing lists one for sale or changes a price.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

StubHub tools (3)

  • event_search
  • fetch_listings
  • highlight_listing

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • We never reached the server. An anonymous initialize returned HTTP 403 from CloudFront carrying a 919-byte HTML error page, with no www-authenticate header. Six other paths — four OAuth metadata locations, the host root, and a deliberately nonsensical control path — all returned the byte-identical body once the per-request CloudFront request ID is normalised away.
  • No RFC 9728 descriptor could be read, for the same reason. This server publishes no scope evidence we could reach. The scope table on this page belongs to StubHub's separate Partner API, not to this endpoint, and must not be read as this connector's permissions.
  • No tool schemas or safety annotations. Without a tools/list response there are no machine-declared readOnlyHint or destructiveHint values for any of the three tools. The parameter lists on this page come from StubHub's documentation, which does not publish JSON Schema types or say which parameters are enumerated.
  • The tool-name match is semantic, not literal. The directory's snake_case and StubHub's Title Case share no exact string. They map one-to-one after normalisation and the parameter lists corroborate each pairing, but a rename that preserved the meaning would not be visible to us.
  • No purchase, no listing, no price change — on this surface only. The absence is real and StubHub states it, but StubHub's Partner API documents creating, updating and deleting seller listings and patching ticket_price. Those live on a different host behind a different OAuth registration. Treat "the agent cannot sell" as true of this connector, not of StubHub.
  • The stubhub_id session identifier is unverifiable from outside. StubHub calls it anonymous. We have no way to confirm what it resolves to server-side or how long it persists.
  • No rate limits are published for this endpoint. StubHub's connector article says nothing about request ceilings, and its Partner API documentation covers a different product.
  • The connector's docs live in one article and nowhere else. Of 280 articles in StubHub's help centre index, exactly one mentions ChatGPT, Claude, MCP or connectors. There is no second first-party account of this surface to cross-check against.
  • The documentation page is invisible to text extraction. support.stubhub.com serves an HTML shell whose article body is fetched client-side; a text extractor scores it at zero words. The 1,068-word article was recovered from the site's own public content route, which the page's JavaScript bundle names. Anyone auditing this page from the rendered HTML alone will find nothing.

Frequently asked questions

Can Claude buy StubHub tickets for me?

No. StubHub's help article states directly that these tools only provide information and that the agent does not make transactions on behalf of users. All three tools read. When you have chosen a ticket the connector hands you off to StubHub, where you sign in and complete the purchase yourself under the FanProtect Guarantee.

Can an AI agent list my tickets for sale on StubHub?

No. None of the three tools writes anything, and no tool name carries a create, list, price or offer verb. StubHub does run a separate Partner API with a full seller surface — create, update and delete listings, plus a patchable ticket price — but that API is a different product on a different host and none of it is wired into this connector.

How many tools does the StubHub MCP server have?

Three, and both available sources agree. Anthropic's directory lists event_search, fetch_listings and highlight_listing. StubHub's own help article independently names the same three as Event Search, Fetch Listings and Highlight Listing, and documents every parameter of each. The two lists match one-to-one once capitalisation and spacing are normalised.

Do I need a StubHub account to use the connector?

Not to search. Anthropic's directory records this endpoint as authless with a no-auth posture, and StubHub's setup instructions for Claude are simply to open Settings, browse connectors and click Connect, with no sign-in step described. An account becomes necessary only at checkout, which happens on StubHub's own site.

Why is the StubHub MCP endpoint hosted at open-ai-app.stubhub.net?

Because the same surface serves both assistants. StubHub's help article covers ChatGPT and Claude together and documents a ChatGPT-specific @StubHub invocation alongside Claude's. The hostname reads as an OpenAI-era name reused for a Claude connector. Only two of the 1,897 servers in our directory snapshot carry an OpenAI-flavoured hostname.

What data does the StubHub connector send about me?

Search terms, plus a session identifier. Every one of the three tools accepts a stubhub_id parameter, which StubHub documents as an anonymous identifier that keeps the session consistent across multiple tool calls. event_search also takes an intent_level flag marking whether you are buying seriously or just browsing, which is commercial signal rather than a search filter.

Can the connector see ticket prices and seat views?

Yes, both, in real time. StubHub states the integration returns live availability and pricing rather than cached webpage summaries. fetch_listings returns prices, view-from-seat imagery and venue maps for one event, and can sort by cheapest, best seats, best value or recommended. highlight_listing then expands a single listing with further detail.

Did Agentman verify the StubHub MCP connection live?

No, and the reason is worth stating. An anonymous request to the endpoint returned HTTP 403 from CloudFront with an HTML body, not a JSON authentication challenge. Seven unrelated paths including a nonsense control returned that identical body, so the edge refuses our client before the origin answers. The auth posture was never observed.

Sources

Use it in an agent

Put StubHub to work.

Connect StubHub once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019Our AI receptionist answers.