Ticketmaster
NPM · @PIPEWORX/MCP-TICKETMASTER · 2 COMPONENTS
Ticketmaster Discovery v2 MCP.
Available components
Last scanned (4 hours ago)
Scores higher than 58% of npm servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ticketmaster). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1170 tokens (~117/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage91
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 73% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-ticketmaster@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-ticketmaster |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ticketmaster/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560461982 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6de090c60df7d8308a1f5d93cea8bc9a029cd9c305cb308dda41fd692b004ee89c427febb31467c6dabcf53f646de249cdfec2b74c7b08827a83f3dce |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
attraction ~24
Single attraction.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| locale | string | – | – |
No output schema declared.
No examples provided.
attraction_search ~182
Ticketmaster Discovery API — search attractions (artists, sports teams, performers) by keyword, classificationName, or other filters. Returns attraction name, ID, classifications, and images.
| Name | Type | Req | Description |
|---|---|---|---|
| classificationName | string | – | Segment/genre, e.g. "Music", "Sports". |
| countryCode | string | – | 2-letter country code, e.g. "US". |
| keyword | string | – | Artist, team or performer name, e.g. "Taylor Swift". Omitting it returns Ticketmaster's default attraction feed, not a search. |
| page | number | – | 0-based page number. Deep paging is capped at page × size ≤ 1000. |
| size | number | – | Results per page (default 20). |
| sort | string | – | Sort order. Ticketmaster accepts only these values for attractions; anything else is a 400. |
No output schema declared.
No examples provided.
classification ~48
Ticketmaster Discovery API — full detail for a single classification by ID: segment, genre, sub-genre hierarchy with names and IDs.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| locale | string | – | – |
No output schema declared.
No examples provided.
classifications ~46
Ticketmaster Discovery API — list all event classification segments, genres, and sub-genres (e.g. Music > Rock > Alternative). Use to discover valid classificationName values for filtering event_search.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
event ~24
Single event.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| locale | string | – | – |
No output schema declared.
No examples provided.
event_images ~20
Images for an event.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
event_search ~496
Ticketmaster Discovery API — search live events by keyword, city, countryCode, stateCode, venueId, attractionId, classificationName (e.g. 'Music'), and date window. PREFER for "what is on at <venue>", "upcoming <artist> concerts", "events in <city> this month". Pass the venue/artist as keyword, or venueId from venue_search for an exact venue. Returns events with dates, venue, and ticket links.
| Name | Type | Req | Description |
|---|---|---|---|
| attractionId | string | – | Ticketmaster attraction id (from attraction_search). |
| city | string | – | City name, e.g. "New York". |
| classificationName | string | – | Segment/genre, e.g. "Music", "Sports", "Theatre". |
| countryCode | string | – | 2-letter country code, e.g. "US". |
| endDateTime | string | – | ISO-8601 UTC upper bound, e.g. "2026-08-31T23:59:59Z". |
| keyword | string | – | Free-text search: venue, artist, team or event name (e.g. "Madison Square Garden", "Taylor Swift"). Pass the subject of the question here — omitting it returns Ticketmaster's unfiltered default feed,… |
| page | number | – | 0-based page number. Ticketmaster caps deep paging at page × size ≤ 1000, so with the default size of 20 the last reachable page is 50; narrow with city/date filters instead of paging further. |
| postalCode | string | – | Postal/ZIP code. |
| size | number | – | Results per page (default 20, max 200). |
| sort | string | – | Sort order. Ticketmaster accepts only these values; anything else is a 400. Common: "date,asc" (soonest first), "relevance,desc". |
| startDateTime | string | – | ISO-8601 UTC lower bound, e.g. "2026-08-01T00:00:00Z". Use with endDateTime for "this month". |
| stateCode | string | – | 2-letter state code, e.g. "NY". |
| venueId | string | – | Ticketmaster venue id (from venue_search). More precise than keyword for "what is on at <venue>" — a keyword can match a nearby or similarly named venue. |
No output schema declared.
No examples provided.
suggest ~47
Ticketmaster Discovery API — autocomplete suggestions for a keyword: returns matching events, attractions, and venues ranked by relevance. Use to resolve partial names before querying other endpoints.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
No output schema declared.
No examples provided.
venue ~24
Single venue.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| locale | string | – | – |
No output schema declared.
No examples provided.
venue_search ~207
Ticketmaster Discovery API — search venues by keyword, city, stateCode, countryCode, or postalCode. Returns venue name, address, city, state, capacity, coordinates and the venue id to pass to event_search as venueId.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City name, e.g. "New York". |
| countryCode | string | – | 2-letter country code, e.g. "US". |
| keyword | string | – | Venue name to search for, e.g. "Madison Square Garden". |
| page | number | – | 0-based page number. Deep paging is capped at page × size ≤ 1000. |
| postalCode | string | – | Postal/ZIP code. |
| size | number | – | Results per page (default 20). |
| sort | string | – | Sort order. Ticketmaster accepts only these values for venues; anything else is a 400. |
| stateCode | string | – | 2-letter state code, e.g. "NY". |
No output schema declared.
No examples provided.
How do I install the Ticketmaster MCP server?
Ticketmaster runs locally as an npm package, launched with npx -y @pipeworx/mcp-ticketmaster. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-ticketmaster
claude mcp add pipeworx-io-ticketmaster -- npx -y @pipeworx/mcp-ticketmaster
What is the Ticketmaster MCP server?
Ticketmaster is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ticketmaster. Ticketmaster Discovery v2 MCP. This page covers its npm package (@pipeworx/mcp-ticketmaster).
Is the Ticketmaster MCP server safe to use?
Ticketmaster scores 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Ticketmaster MCP server expose?
Ticketmaster exposes 10 tools: event_search, event, event_images, attraction_search, attraction, and 5 more. Their descriptions and schemas cost roughly 1,118 tokens of context every time the server is loaded.
Is the Ticketmaster MCP server still maintained?
Ticketmaster is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Ticketmaster MCP server under?
Ticketmaster declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.