TicketsData
REMOTE · MCP.TICKETSDATA.COM · SCANNED OCT 7
Real-time ticket listings, prices and fees across major ticket marketplaces.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 926 tokens (~231/item across 4 items; 4 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 Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the TicketsData MCP server?
TicketsData is a hosted endpoint at https://mcp.ticketsdata.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.ticketsdata.com
claude mcp add --transport http ticketsdata-ticketsdata-mcp 'https://mcp.ticketsdata.com/mcp'
{
"mcpServers": {
"ticketsdata-ticketsdata-mcp": {
"url": "https://mcp.ticketsdata.com/mcp"
}
}
} {
"servers": {
"ticketsdata-ticketsdata-mcp": {
"type": "http",
"url": "https://mcp.ticketsdata.com/mcp"
}
}
} [mcp_servers.ticketsdata-ticketsdata-mcp] url = "https://mcp.ticketsdata.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ticketsdata-ticketsdata-mcp": {
"type": "remote",
"url": "https://mcp.ticketsdata.com/mcp",
"enabled": true
}
}
} openclaw mcp add ticketsdata-ticketsdata-mcp --url 'https://mcp.ticketsdata.com/mcp' --transport streamable-http
mcp_servers:
ticketsdata-ticketsdata-mcp:
url: "https://mcp.ticketsdata.com/mcp" {
"McpServers": {
"ticketsdata-ticketsdata-mcp": {
"Transport": "http",
"Url": "https://mcp.ticketsdata.com/mcp"
}
}
} assistant mcp add ticketsdata-ticketsdata-mcp -t streamable-http -u 'https://mcp.ticketsdata.com/mcp'
{
"mcpServers": {
"ticketsdata-ticketsdata-mcp": {
"type": "http",
"url": "https://mcp.ticketsdata.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 7 Oct 26 0
- Schema quality: 191 → 231 ▼ functional
- Stability: unverified → 0.07 ▲ functional
- 5 Oct 26 71
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 8 Oct 2026 · Probed https://mcp.ticketsdata.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.ticketsdata.com | CN=YR2,O=Let's Encrypt,C=US | 4 Oct 2026 | 2 Jan 2027 | RSA 2048 | SHA256-RSA | 62bf9898d92278bf6dde6fae31d2824e2ac |
| SANs: mcp.ticketsdata.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.ticketsdata.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| ticketsdata.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.ticketsdata.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.ticketsdata.com/mcp | HTTPS enforced | 301 | https://mcp.ticketsdata.com/mcp |
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 →
compare_marketplaces Compare one event across marketplaces ~191
Cross-market report for ONE event. Give any marketplace's event URL: TicketsData finds the same event on the other marketplaces, fetches all of them live, and returns matched URLs, normalized listings per marketplace, per-market price and fee summaries, the cheapest all-in entry point and per-section price spreads between marketplaces. Returns the complete TicketsData API response, unchanged: always as a link to a JSON file, and also inline when it is small enough. EXPENSIVE: costs 1 report plus up to 12 API credits and takes 10 to 30 seconds. Needs a Pro plan or above. Only one can run at a time per account. Use get_event_listings instead when the user asks about a single marketplace.
| Name | Type | Req | Description |
|---|---|---|---|
| event_url | string | yes | Full event URL from ticketmaster, stubhub, seatgeek, vividseats, gametime, tickpick or viagogo. |
No output schema declared.
No examples provided.
find_events Find events for a performer or venue ~199
List upcoming events for a performer, artist, team, organizer or venue page on one marketplace. Use it to discover event URLs, then pass one to get_event_listings or compare_marketplaces. Real time, costs 1 API credit. Returns the complete TicketsData API response, unchanged: always as a link to a JSON file, and also inline when it is small enough. Pass performer_url for most platforms. venue_url is for dice only (dice.fm/venue/... and dice.fm/promoters/... pages). For eventbrite pass the organizer page URL as performer_url. viagogo and axs are not supported here.
| Name | Type | Req | Description |
|---|---|---|---|
| performer_url | – | – | Performer, artist, team or organizer page URL on that marketplace. |
| platform | string | yes | Marketplace id: ticketmaster, stubhub, seatgeek, vividseats, gametime, tickpick, dice, eventbrite. |
| venue_url | – | – | dice only: venue or promoter page URL. |
No output schema declared.
No examples provided.
get_event_listings Get live listings for an event ~240
Fetch live ticket listings for ONE event on ONE marketplace: section, row, quantity, price and fees. Real time, not cached. Costs 1 API credit per call. Returns the complete TicketsData API response, unchanged: always as a link to a JSON file, and also inline (whole when small, otherwise the first part of the listings in the API's order). The body structure differs per marketplace. Primary platforms (ticketmaster, dice, eventbrite, axs) return face-value offers and ticket tiers rather than resale listings. axs needs a Pro plan or above.
| Name | Type | Req | Description |
|---|---|---|---|
| event_url | string | yes | Full event URL on that marketplace. ticketmaster, gametime and dice also accept a bare event ID. |
| mode | – | – | Optional. gametime: 'all' (quantities 1 to 10) or 'qty=N'. ticketmaster: 'availability', 'pricing' or 'quickpicks'. Omit for other platforms. |
| platform | string | yes | Marketplace id: ticketmaster, stubhub, seatgeek, vividseats, gametime, tickpick, viagogo, dice, eventbrite, axs. |
No output schema declared.
No examples provided.
list_marketplaces List supported marketplaces ~57
List the marketplaces TicketsData supports, the URL or ID format each one expects, which ones support event discovery and cross-market comparison, and valid mode values. Free: uses no credits. Call this first when unsure how to format an input.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the TicketsData MCP server?
TicketsData is an MCP server listed in the public MCP registry as io.github.ticketsdata/ticketsdata-mcp. Real-time ticket listings, prices and fees across major ticket marketplaces. This page covers its hosted endpoint (https://mcp.ticketsdata.com/mcp).
Is the TicketsData MCP server safe to use?
TicketsData scores 71 out of 100 on VerifyMCP. 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 TicketsData MCP server expose?
TicketsData exposes 4 tools: list_marketplaces, get_event_listings, find_events, compare_marketplaces. Their descriptions and schemas cost roughly 687 tokens of context every time the server is loaded.
Does the TicketsData MCP server require authentication?
No. We connected to TicketsData without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the TicketsData MCP server still maintained?
TicketsData is still listed as active in the MCP registry. We last reached this channel on 7 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.