# UPFRONT (remote · api.upfront.tickets)

All-in ticket prices across ticket sites, seat views and venue guides for US events.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `api.upfront.tickets`: 73/100 (this document), [markdown](https://verifymcp.io/servers/tickets-upfront-upfront/api.md), [page](https://verifymcp.io/servers/tickets-upfront-upfront/api)

## Channel facts

- Endpoint: `https://api.upfront.tickets/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 4259 tokens (~473/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (22% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 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.

## Install

### How do I install the UPFRONT MCP server?

UPFRONT is a hosted endpoint at https://api.upfront.tickets/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.

### Claude

```bash
claude mcp add --transport http tickets-upfront-upfront 'https://api.upfront.tickets/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tickets-upfront-upfront": {
      "url": "https://api.upfront.tickets/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tickets-upfront-upfront": {
      "type": "http",
      "url": "https://api.upfront.tickets/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tickets-upfront-upfront]
url = "https://api.upfront.tickets/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tickets-upfront-upfront": {
      "type": "remote",
      "url": "https://api.upfront.tickets/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tickets-upfront-upfront --url 'https://api.upfront.tickets/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tickets-upfront-upfront:
    url: "https://api.upfront.tickets/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tickets-upfront-upfront": {
      "Transport": "http",
      "Url": "https://api.upfront.tickets/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tickets-upfront-upfront -t streamable-http -u 'https://api.upfront.tickets/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tickets-upfront-upfront": {
      "type": "http",
      "url": "https://api.upfront.tickets/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-06 (score 73, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-05 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-04 (score 72, 0)

- [security] Tool “best_seats” rewrote its description, which is the text the model reads
- [security] Tool “section_info” rewrote its description, which is the text the model reads

### 2026-11-03 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 69, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 69)

First indexed and scored.

## MCP tools (9)

### `find_events` (~599 tokens)

Find events

Events on sale on UPFRONT (games, concerts, shows, comedy), soonest
first. Matches requests like "Knicks games next week", "concerts in
Denver this weekend" or "something fun near Fenway under $100".

query: words matched against the event, venue or city ("Hamilton",
"Madison Square Garden"); "*" (the default) means no text filter.
near: a place name ("Denver", "Fenway Park", "Austin, TX"): only
events within radius km (default 100) of it.
lat/lng: coordinates of a location the user has shared.
performer: a team or artist ("Knicks", "Olivia Rodrigo"): only
events they play. More exact than query for a team or artist.
categories: zero or more of exactly these values: mlb, nba, nfl,
nhl, mma, ncaaFootball, ncaaBasketball, wwe, soccer, boxing,
tennis, popRock, rapHipHop, country, latin, alternative, hardRock,
reggae, world, classical, religious, musicFestivals, broadway,
musical, dance, opera, comedy. There is no generic "concerts"
value; music is split into the genres listed.
start_datetime/end_datetime: absolute local ISO datetimes. "This
weekend" is the coming Saturday 00:00 to Sunday 23:59:59; "tonight"
is today 00:00 to 23:59:59. Without them, every upcoming date counts.
max_price: the most per ticket, fees included, in dollars.
page/per_page: further pages of results.

The catalog records no audience, vibe or popularity; categories and
words in event names ("Family", "18+") are the closest signals.

Returns events: eventId, name, venue, city, state, startsAt (local),
fromAllInPrice, url. fromAllInPrice is the lowest per-ticket price
on UPFRONT with every fee in, as the event page showed it at
UPFRONT's last check; it is not a quote for a number of tickets,
and null means none listed right now. url is the event's page on
UPFRONT. Parking and tailgate events (isParkingEvent) come after the
games. place says where `near` was read as; performer says which
team or artist was used, with otherMatches when the name could mean
others. An empty list can also mean the sea…

Input parameters:

- `categories`
- `end_datetime`
- `lat`
- `lng`
- `max_price`
- `near`
- `page` (integer)
- `per_page` (integer)
- `performer`
- `query` (string)
- `radius` (integer)
- `start_datetime`

### `get_seating_map` (~156 tokens)

Seating chart

A link to the venue's seating-chart image for one event: a static
diagram showing every section's shape and position relative to the
field or stage, color-coded by tier or level.

event_id: UPFRONT's event id (eventId in event results). The chart
belongs to the venue's seating layout, not the date, so the same
image serves every event there, including far-future events with no
tickets yet.

Returns {"mapImageUrl"} on success, {} when there is no chart for
this venue, or {"error": "search_failed"} when the lookup failed
after retries. In the last two cases no map is available.

Input parameters:

- `event_id` (integer, required)

### `compare_prices` (~638 tokens)

Compare all-in prices

One event's all-in prices on every site in one answer: UPFRONT's
own listings and the other marketplaces (StubHub, SeatGeek, Vivid
Seats, TickPick, Gametime, AXS, Ticketmaster), cheapest first.
Matches requests like "cheapest 2 seats together for Saturday's
game under $500 total" or "who has it cheaper?". event_id is
UPFRONT's event id (eventId in event results).

quantity: how many tickets are needed together. Only listings that
sell exactly that many as one group count, and totalAllInPrice is
the whole group's price.
max_price: the most per ticket, fees included, in dollars.
max_total_price: the budget for the whole group, as the user stated
it (needs quantity); UPFRONT works out the per-ticket limit.
section: a section name or number ("112", "Floor"): only that
section.
limit: how many picks to return (default 5, at most 10).

Returns:
\- event: name, venue, city, startsAt and url (the event's page).
\- sites: one per site, cheapest first: site ("UPFRONT" for ours),
  checked, checkedAt, listings (how many match there) and
  lowestAllInPrice. checked "ok" means the site was read;
  "incomplete" means only some listings came back; "failed" means
  it couldn't be read, which is not the same as having nothing. A
  site missing from sites wasn't matched to this event, which is
  not the same as sold out there.
\- listings: the cheapest matching picks across every site: site,
  section, row, allInPrice (per ticket, that site's own price with
  its fees), totalAllInPrice (with quantity), quantities, notes and
  url, the link to buy exactly that listing on that site.
  feesIncluded false (rare) means that site gave no fees-in price.
\- moreListings: how many matched but weren't returned.

Other sites' prices are as of checkedAt and may have changed since.
otherSites says where they came from: "saved" is UPFRONT's last
check of each site, which can be hours or a few days old; "none"
means no recent check, and event.url compares every site live. All
prices are all-in totals…

Input parameters:

- `event_id` (integer, required)
- `limit` (integer)
- `max_price`
- `max_total_price`
- `quantity`
- `section`

Output parameters:

- `error` (string)
- `event`
- `listings` (array)
- `moreListings` (integer)
- `notShown` (array)
- `otherSites` (object)
- `quantity` (integer)
- `sites` (array)
- `unavailable` (string)

### `find_ticket_groups` (~622 tokens)

UPFRONT tickets

UPFRONT's own listings for one event that can be bought now,
cheapest first. event_id is UPFRONT's event id (eventId in event
results); this does not search by name or place.

quantity: the exact number of tickets needed together ("for two
people" is 2). When set, only listings that sell that many as ONE
group are returned; two separate listings can't be combined into
one group.
max_price/min_price: the per-ticket price in dollars, fees included.
max_total_price: the budget for the whole group, in dollars, as the
user stated it ("$200 for two" is 200). Needs quantity; UPFRONT
works out the per-ticket limit from it.
section: a section name or number ("112", "Floor", "Mezzanine"):
only that section's listings.
limit: how many listings to return (default 10, at most 25).
eticket_only / instant_download_only: only listings with that
delivery method.
min_days_before_event / max_days_before_event: only listings
released within that window before the event ("last-minute").

Returns:
\- totalListings, lowestAllInPrice, highestAllInPrice: across every
  listing matching the filters, not only those returned.
\- listings: the cheapest matches, each with section, row, allInPrice
  (per ticket, every fee included), totalAllInPrice (the group's
  price, when quantity is set), quantities (how many can be bought
  together from this listing), notes, standardSection,
  deliveryMethods and url.
\- moreListings: how many matched but weren't returned.
Parking-only listings are left out, except on a parking event,
where every listing is a parking pass.

notes (what the seller wrote, e.g. "Obstructed view") and
standardSection (UPFRONT's name for the section, when matched) are
the only view or location signals on a listing; there is no
view-quality score. When they say nothing, no view information is
available for that listing. Distance, height, cover and a picture
of the view come from UPFRONT's section facts, at venues with an
UPFRONT seating chart.

url is the link to buy exactly that…

Input parameters:

- `eticket_only`
- `event_id` (integer, required)
- `instant_download_only`
- `limit` (integer)
- `max_days_before_event`
- `max_price`
- `max_total_price`
- `min_days_before_event`
- `min_price`
- `quantity`
- `section`

Output parameters:

- `error` (string)
- `highestAllInPrice`
- `listings` (array)
- `lowestAllInPrice`
- `moreListings` (integer)
- `quantity` (integer)
- `totalListings` (integer)

### `best_seats` (~405 tokens)

Best seats by view

UPFRONT's own listings for one event ranked by where the seats are,
not only by price: "best view for 2 under $250", "closest seats to
the court for $400 total", "seats in the shade", "not too high up".
event_id is UPFRONT's event id (eventId in event results).

prefer: "closest" (nearest the field, court or stage; the default),
"lowest" (lowest eye height), "covered" (rows a deck or roof
overhead reaches well past, straight up and 30 degrees out toward
the field and to either side, first; for shade or rain, though wind
can still blow rain in) or "value" (the best mix of closeness and
price).
quantity: the number of tickets needed together. max_price: per
ticket, fees included. max_total_price: the whole group's budget,
with quantity.
limit: how many picks (default 5, at most 10).

Each pick has the section, row, all-in price (and total for the
quantity), the row's distance and height, whether it's covered, the
section's view picture (UPFRONT's 3D view, not a photo), its
section page, why it was picked, and url, the link to buy exactly
that listing.

placed says how many of the matching listings could be put on the
seating chart; only those are ranked. hasFacts false means UPFRONT
has no seat facts for this venue, so the picks are simply the
cheapest and the ranking is by price only. {"error":
"search_failed"} means the listings lookup failed, not that nothing
is on sale.

Input parameters:

- `event_id` (integer, required)
- `limit` (integer)
- `max_price`
- `max_total_price`
- `prefer` (string)
- `quantity`

### `section_info` (~315 tokens)

Section facts and view

What one section of a venue is like: where it is, how far its front
and back are from the field, court or stage, how high they sit,
which rows are covered (a deck or roof overhead reaching well past
every seat in the row, so a row at a deck's front edge isn't;
wind can still blow rain in), and a picture of the view from it. Matches
questions like "is section 314 at Lumen Field covered?", "what's
the view from 210?" or "how high up is row 20 in 111?". It has no
row or seat counts.

venue: the venue's name ("Madison Square Garden", "MSG", "Dodger
Stadium").
section: the section's name or number as tickets name it ("111",
"Section 111", "Field Box 22").
row: optional; one row to describe ("10", "M"). A row between the
front and back is estimated from them and marked "estimated".

Covers the venues with an UPFRONT seating chart; for any other
venue the answer says so and lists the ones covered.

viewPicture is a picture of the view from the section, rendered
from UPFRONT's 3D model of the venue (not a photo). sectionPage is
the section's page on UPFRONT. source says where the facts come
from.

Input parameters:

- `row`
- `section` (string, required)
- `venue` (string, required)

### `report_fact` (~266 tokens)

Report a wrong fact

Passes a fan's correction of one of UPFRONT's facts to a person at
UPFRONT to check: "section 112 has 18 rows, not 17", "the bag
policy changed, backpacks are allowed now", "gates open at 5:30".
It is for corrections the user gives or asks to send to UPFRONT.

kind: one of "rows" (rows or seats in a section), "view", "section"
(its name or where it is), "bags", "entry", "parking", "transit",
"food", "other".
venue: the venue's name. section, row: when it's about one.
claim: what the fan says is right, in their words, with what
UPFRONT said if known (under 1,000 characters).
source: how the fan knows ("sat there on Oct 12", a link), if they
said.

Nothing on UPFRONT changes until a person checks it: the correction
is passed on, not fixed. Every request files a separate report.

Input parameters:

- `claim` (string, required)
- `kind` (string, required)
- `row`
- `section`
- `source`
- `venue` (string, required)

### `venue_info` (~320 tokens)

Venue guide: bags, entry, parking, food

What to know before going to a venue, from UPFRONT's venue guide:
the bag policy and what fans can bring, gates and entry, parking,
getting there by transit or rideshare, and food and drink,
including what the guide says about gluten-free, vegetarian or
vegan, halal and kosher food. Matches questions like "what's the
bag policy at MetLife?", "when do doors open at MSG?" or "where do
I park for Lambeau?".

venue: the venue's name ("MetLife Stadium", "MSG", "Lumen Field,
Seattle").
topics: optional; only these parts, at more length: any of "bags",
"entry", "parking", "transit", "food". Without it, every part.

Covers the 36 stadiums, arenas and amphitheaters UPFRONT has a
guide for; for any other venue the answer says so and lists the
ones with guides.

Each part is the guide's own words ("text", plus the guide's "faq"
questions and answers). factsLastChecked is the date UPFRONT last
checked the guide's facts; rules can change for a single event, and
the venue's own event page has the final word. guideUrl is the
guide on UPFRONT. dietary lists what the guide says per diet;
dietaryNotMentioned lists diets the guide doesn't cover, which
doesn't mean the venue has nothing for them.

Input parameters:

- `topics`
- `venue` (string, required)

### `artist_tours` (~409 tokens)

Tour dates and prices

An artist's upcoming dates on UPFRONT in one answer: every date,
venue and city, the lowest all-in price per show, and UPFRONT's
tour guide when there is one. Matches requests like "when is
Olivia Rodrigo playing near Philadelphia?", "Noah Kahan tour dates"
or "cheapest Iron Maiden show this spring", including shows across
several cities.

artist: the artist's name ("Olivia Rodrigo").
near: a place name ("Philadelphia", "Austin, TX"): only dates within
radius km (default 150) of it. lat/lng: coordinates of a location
the user has shared. Without either, the whole tour.
start_date/end_date: YYYY-MM-DD, both included; without them, every
date.
limit: how many dates to list (default 30, at most 60), soonest
first. totalDates counts every date that matched.

Each date has the event's eventId, name, venue, city, state, local
start time, fromAllInPrice and url. fromAllInPrice is the lowest
per-ticket price on UPFRONT with every fee included, as the event
page showed it at UPFRONT's last check; it is not a quote for a
number of tickets, and null means no tickets listed right now (not
sold out). url is the event's page on UPFRONT.

tourGuide, when present, is UPFRONT's guide to the tour (dates,
venues, presales, how to buy). artistPage lists every date.
otherMatches are other performers the name could mean. found false
means no artist by that name has dates in UPFRONT's catalog.

Input parameters:

- `artist` (string, required)
- `end_date`
- `lat`
- `limit` (integer)
- `lng`
- `near`
- `radius` (integer)
- `start_date`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tickets-upfront-upfront/api#diagnostics

## Score history

- 2026-11-06: 73
- 2026-11-05: 73
- 2026-11-04: 72
- 2026-11-03: 72
- 2026-11-02: 71
- 2026-11-01: 71
- 2026-10-31: 70
- 2026-10-30: 70
- 2026-10-29: 69
- 2026-10-28: 69

## Common questions

### What is the UPFRONT MCP server?

UPFRONT is an MCP server listed in the public MCP registry as tickets.upfront/upfront. All-in ticket prices across ticket sites, seat views and venue guides for US events. This page covers its hosted endpoint (https://api.upfront.tickets/mcp).

### Is the UPFRONT MCP server safe to use?

UPFRONT scores 73 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 UPFRONT MCP server expose?

UPFRONT exposes 9 tools: find_events, get_seating_map, compare_prices, find_ticket_groups, best_seats, and 4 more. Their descriptions and schemas cost roughly 3,730 tokens of context every time the server is loaded.

### Does the UPFRONT MCP server require authentication?

No. We connected to UPFRONT without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the UPFRONT MCP server still maintained?

UPFRONT is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

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

VerifyMCP ran 13 checks on UPFRONT, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://api.upfront.tickets/mcp
- Website: https://upfront.tickets/mcp
- Changelog RSS feed: https://verifymcp.io/servers/tickets-upfront-upfront/api.xml
- Changelog JSON feed: https://verifymcp.io/servers/tickets-upfront-upfront/api/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tickets-upfront-upfront/api.json
- HTML version of this page: https://verifymcp.io/servers/tickets-upfront-upfront/api