# Ticketmaster (npm · @pipeworx/mcp-ticketmaster)

Ticketmaster Discovery v2 MCP.

- Trust score: 78/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-ticketmaster/ticketmaster-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ticketmaster/ticketmaster-mcp)
- npm · `@pipeworx/mcp-ticketmaster`: 78/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ticketmaster/pipeworx-mcp-ticketmaster.md), [page](https://verifymcp.io/servers/pipeworx-io-ticketmaster/pipeworx-mcp-ticketmaster)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ticketmaster`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ticketmaster).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 91/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 73% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-ticketmaster -- npx -y @pipeworx/mcp-ticketmaster
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-ticketmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ticketmaster"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-ticketmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ticketmaster"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-ticketmaster -- npx -y @pipeworx/mcp-ticketmaster
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-ticketmaster": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-ticketmaster"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-ticketmaster --command npx --arg -y --arg @pipeworx/mcp-ticketmaster
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-ticketmaster:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-ticketmaster"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-ticketmaster": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-ticketmaster"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-ticketmaster -t stdio -c npx -a -y @pipeworx/mcp-ticketmaster
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-ticketmaster": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ticketmaster"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-30 (score 78, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (10)

### `event_search` (~496 tokens)

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.

Input parameters:

- `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.

### `event` (~24 tokens)

Single event.

Input parameters:

- `id` (string, required)
- `locale` (string)

### `event_images` (~20 tokens)

Images for an event.

Input parameters:

- `id` (string, required)

### `attraction_search` (~182 tokens)

Ticketmaster Discovery API — search attractions (artists, sports teams, performers) by keyword, classificationName, or other filters. Returns attraction name, ID, classifications, and images.

Input parameters:

- `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.

### `attraction` (~24 tokens)

Single attraction.

Input parameters:

- `id` (string, required)
- `locale` (string)

### `venue_search` (~207 tokens)

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.

Input parameters:

- `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".

### `venue` (~24 tokens)

Single venue.

Input parameters:

- `id` (string, required)
- `locale` (string)

### `classifications` (~46 tokens)

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.

### `classification` (~48 tokens)

Ticketmaster Discovery API — full detail for a single classification by ID: segment, genre, sub-genre hierarchy with names and IDs.

Input parameters:

- `id` (string, required)
- `locale` (string)

### `suggest` (~47 tokens)

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.

Input parameters:

- `keyword` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-ticketmaster/pipeworx-mcp-ticketmaster#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### 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.

### What did VerifyMCP test on the Ticketmaster MCP server?

VerifyMCP ran 15 checks on Ticketmaster, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Ticketmaster: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-ticketmaster
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-ticketmaster
- Repository: https://github.com/pipeworx-io/mcp-ticketmaster
- Website: https://pipeworx.io/packs/ticketmaster
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-ticketmaster/pipeworx-mcp-ticketmaster.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-ticketmaster/pipeworx-mcp-ticketmaster/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-ticketmaster/pipeworx-mcp-ticketmaster.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-ticketmaster/pipeworx-mcp-ticketmaster