mcp.ticketsdata.com
https://mcp.ticketsdata.com/mcp
active Production-safe Score 92/100 http no auth
At a glance
| Endpoint | https://mcp.ticketsdata.com/mcp |
|---|---|
| Source | https://github.com/uniquekaiser/getmcp-extensions/blob/main/assets/remote-catalogue.json |
| Transport | http |
| Tools | 5 |
| Auth | none |
| First seen | 2026-11-01 17:01:46 |
| Last checked | 2026-11-17 21:46:20 |
Observed reliability
| 7-day uptime | 100% |
|---|---|
| 24-hour uptime | 100% |
| Handshake success | 100% |
| Latency p50 / p95 | 559 / 758 ms |
| Last successful check | 2026-11-17 21:46:20 |
Measured by Arclan's validator via repeated live MCP handshakes. How this is computed →
Tools (5)
list_marketplaces— List the marketplaces TicketsData supports, the URL or ID format each one expects, which ones support event discovery and cross-market compaget_event_listings— Fetch live ticket listings for ONE event on ONE marketplace: section, row, quantity, price and fees. Real time, not cached. Costs 1 API credfind_events— List upcoming events for a performer, artist, team, organizer or venue page on one marketplace. Use it to discover event URLs, then pass onecompare_marketplaces— Cross-market report for ONE event. Give any marketplace's event URL: TicketsData finds the same event on the other marketplaces, fetches allanalyze_listings— Work on the COMPLETE response of an earlier get_event_listings, compare_marketplaces or find_events call, including items too many to show i
Validation history
| Checked | Reachable | Handshake | Latency | Score | State |
|---|---|---|---|---|---|
| 2026-11-17 21:46:20 | ✓ | ✓ | 562 ms | 90 | active |
| 2026-11-17 21:31:15 | ✓ | ✓ | 506 ms | 90 | active |
| 2026-11-17 21:16:04 | ✓ | ✓ | 522 ms | 90 | active |
| 2026-11-17 21:00:48 | ✓ | ✓ | 570 ms | 90 | active |
| 2026-11-17 20:45:46 | ✓ | ✓ | 421 ms | 90 | active |
| 2026-11-17 20:30:45 | ✓ | ✓ | 416 ms | 90 | active |
| 2026-11-17 20:15:39 | ✓ | ✓ | 519 ms | 90 | active |
| 2026-11-17 19:59:35 | ✓ | ✓ | 506 ms | 90 | active |
| 2026-11-17 19:44:28 | ✓ | ✓ | 869 ms | 90 | active |
| 2026-11-17 19:29:24 | ✓ | ✓ | 544 ms | 90 | active |
| 2026-11-17 19:14:23 | ✓ | ✓ | 438 ms | 90 | active |
| 2026-11-17 18:58:37 | ✓ | ✓ | 540 ms | 90 | active |
| 2026-11-17 18:43:35 | ✓ | ✓ | 519 ms | 90 | active |
| 2026-11-17 18:28:34 | ✓ | ✓ | 401 ms | 90 | active |
| 2026-11-17 18:13:32 | ✓ | ✓ | 437 ms | 90 | active |
Query this programmatically
Agents can pull this record live over the MCP protocol or REST:
get_server("https://mcp.ticketsdata.com/mcp") # via the Arclan MCP endpoint https://arclan.ai/mcp
GET https://arclan.ai/api/registry/mcp-ticketsdata-com-mcp # JSON