Ticker Docs

Overview

A Bloomberg terminal for the ticket market, exposed to your AI over MCP.

The Ticker Screener MCP turns Claude, or any MCP client, into a research terminal pointed at the live ticket-resale market. Screen ~447,000 live events with a composable predicate DSL, pull deep per-event and per-performer analytics, save Screens as scheduled Views, and fetch the why behind a move, in plain language, from your AI.

Primitives, not verdicts

The server exposes raw analytics (z-scores, cross-sectional percentiles, quartiles, face-value rollups) and lets you compose the screening logic in predicates. There is no is_this_a_good_buy tool. You ask the questions; the data answers.

Get started

The tools at a glance

The server exposes 47 tools. Every connection is signed in, so the groups below are what a tool touches, not what it needs.

Screen and search

Find events, performers and venues, and learn what the predicate DSL accepts.

screen_eventsScreen Events
search_eventsSearch Events
list_screen_columnsList Screener Columns
find_venueFind Venue
get_venue_scheduleVenue Schedule

Event and performer analytics

The joined analytics snapshot, its history, the charts, and the context behind a move.

get_event_analyticsEvent Analytics
get_event_analytics_historyEvent Analytics History
get_performer_analyticsPerformer Analytics
get_event_price_chartEvent Price Chart
get_event_demand_chartEvent Demand Chart
get_performer_rank_chartPerformer Rank Chart
get_event_workspaceGet Event Workspace
research_eventResearch Event Context

Sections, seats and sellers

Inside one event: section counts, the seats behind them, and who is holding the inventory.

get_event_sectionsEvent Sections
get_event_sections_liveEvent Live Section Counts
get_event_sections_atEvent Sections At A Time
get_event_section_seriesEvent Section Open Series
get_event_ga_historyEvent General Admission History
get_event_seats_liveEvent Live Seats
get_event_seats_recentEvent Recent Seat Moves
get_event_seat_historyEvent Seat History
get_event_seller_concentrationEvent Seller Concentration
get_event_seller_seriesEvent Seller Series
get_event_seller_marketEvent Seller Market
get_event_sale_windowsEvent Sale Windows

Saved Views and Matches

Save a Screen so it runs on a schedule, and read the events entering it.

list_viewsList Saved Views
create_viewCreate Saved View
update_viewUpdate Saved View
delete_viewDelete Saved View
get_view_alert_previewPreview a View's Alerts
list_matchesList Matches
get_matchGet Match

Delivery destinations

Where a View's Matches go besides email, and which View delivers to what.

list_destinationsList Alert Destinations
create_destinationCreate Alert Destination
update_destinationUpdate Alert Destination
delete_destinationDelete Alert Destination
list_view_targetsList a View's Delivery Destinations
set_view_targetAttach a Destination to a View
remove_view_targetDetach a Destination from a View

Watchlist

Follow single events and set what a watch fires on.

watch_eventWatch Event
unwatch_eventUnwatch Event
list_watchlistList Watchlist
update_watchUpdate Watch
get_watch_defaultsGet Watchlist Defaults
set_watch_defaultsSet Watchlist Defaults
list_watch_triggersList Watch Triggers

Your account

Your plan, when it renews, and what is left of each allowance.

get_accountGet Account

A typical loop

  1. Discover columns: list_screen_columns to see what you can filter and rank on.
  2. Screen: screen_events with a predicate over those columns, sorted by a ranking primitive.
  3. Drill in: get_event_analytics / get_performer_analytics on what stands out.
  4. Explain: research_event for the catalyst behind the move.
  5. Watch it: create_view so the next dislocation comes to you as an Alert.

On this page