# FrontRowTickets.com MCP Server

> Live FrontRowTickets.com ticket inventory for AI agents: search, availability, pricing, deals.

- name: com.frontrowtickets/frontrowtickets-mcp
- version: 0.1.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 89/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/com.frontrowtickets%2Ffrontrowtickets-mcp
- tools: https://api.protogrid.dev/v1/servers/com.frontrowtickets%2Ffrontrowtickets-mcp/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "frontrowtickets-mcp": {
      "type": "http",
      "url": "https://mcp.frontrowtickets.com/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-1d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 89/100 (new)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 4 of 4 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,035 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 1 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 4, about 1,035 tokens to load them all
- tool set hash: 8df55a60b59caac16c08460a77fedae9
- tools last changed: 2026-10-19T22:22:33.560Z
- badge: [![protogrid quality](https://protogrid.dev/badge/com.frontrowtickets/frontrowtickets-mcp.svg)](https://protogrid.dev/servers/com.frontrowtickets/frontrowtickets-mcp)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-10-19 `get_deals` changed (description, inputSchema) **meaning changed**
  - before: Cheapest available events under a price cap, optionally filtered by city and date range.
  - after: Use when budget is the primary filter: returns the cheapest available events under a required max_price cap (applied to each event's starting price), cheapest first, up to 25 results; events without pricing data are excluded. City and date range are optional additional filters. Use search_events for text- or category-driven discovery instead.
- 2026-10-19 `get_availability` changed (description, inputSchema) **meaning changed**
  - before: Ticket availability and starting price for one event. Note: the TicketNetwork Catalog API does not expose section-level price bands, so only totals and the starting price are returned.
  - after: Answers 'can I get tickets for this event?' for one event: refreshed from the live source at call time, returning current availability and starting price. max_price is a hard gate — the event is reported only if its starting price is at or below it (otherwise availability:null with a note); quantity is informational context only, not a reservation. Use get_event when you need the event's full record, get_deals to browse by budget instead. Note: the catalog API does not expose section-level price bands, so only totals and the starting price are returned.
- 2026-10-19 `get_event` changed (description) **meaning changed**
  - before: Full details for one event: venue, date, ticket count, price range, sections available.
  - after: Full details for one event: venue, date, ticket count, price range, and sections. The record is live-refreshed from the catalog when called (cached copy otherwise), so this is the fullest picture of the event. Prefer get_availability when the only question is 'can I get N tickets at or under $X' — it answers that directly without the full record.
- 2026-10-19 `search_events` changed (description, inputSchema) **meaning changed**
  - before: Search FrontRowTickets.com ticket inventory by text, city, date range, or category. Returns matching events with ticket counts and starting prices.
  - after: Start here for discovery: search FrontRowTickets.com ticket inventory by free text, city, date range, and category (sports, concerts, theater, comedy). All filters are optional and combine freely; returns up to 'limit' events (default 10, max 50, no further pages), soonest first, with ticket counts and starting prices. Use get_event for one event's full record, get_deals when the user has a hard budget cap.

Full history: https://api.protogrid.dev/v1/servers/com.frontrowtickets%2Ffrontrowtickets-mcp/changes

## Remotes

- https://mcp.frontrowtickets.com/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (4)

- `get_availability`: Answers 'can I get tickets for this event?' for one event: refreshed from the live source at call time, returning current availability and starting price. max_price is a hard gate — the event is reported only if its starting price is at or below it (otherwise availability:null with a note); quantity is informational context only, not a reservation. Use get_event when you need the event's full record, get_deals to browse by budget instead. Note: the catalog API does not expose section-level price bands, so only totals and the starting price are returned.
- `get_deals`: Use when budget is the primary filter: returns the cheapest available events under a required max_price cap (applied to each event's starting price), cheapest first, up to 25 results; events without pricing data are excluded. City and date range are optional additional filters. Use search_events for text- or category-driven discovery instead.
- `get_event`: Full details for one event: venue, date, ticket count, price range, and sections. The record is live-refreshed from the catalog when called (cached copy otherwise), so this is the fullest picture of the event. Prefer get_availability when the only question is 'can I get N tickets at or under $X' — it answers that directly without the full record.
- `search_events`: Start here for discovery: search FrontRowTickets.com ticket inventory by free text, city, date range, and category (sports, concerts, theater, comedy). All filters are optional and combine freely; returns up to 'limit' events (default 10, max 50, no further pages), soonest first, with ticket counts and starting prices. Use get_event for one event's full record, get_deals when the user has a hard budget cap.