# Ticketsauce MCP by usefulapi (remote · ticketsauce.usefulapi.io)

Read Ticketsauce events, orders and ticket check-in IDs (read-only).

- Trust score: 18/100 (low)
- Change this week: −45
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `ticketsauce.usefulapi.io`: 18/100 (this document), [markdown](https://verifymcp.io/servers/io-usefulapi-ticketsauce/ticketsauce.md), [page](https://verifymcp.io/servers/io-usefulapi-ticketsauce/ticketsauce)

## Channel facts

- Endpoint: `https://ticketsauce.usefulapi.io/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.11.3`

## 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-05.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Ticketsauce MCP by usefulapi server?

Ticketsauce MCP by usefulapi is a hosted endpoint at https://ticketsauce.usefulapi.io/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 io-usefulapi-ticketsauce 'https://ticketsauce.usefulapi.io/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "io-usefulapi-ticketsauce": {
      "url": "https://ticketsauce.usefulapi.io/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "io-usefulapi-ticketsauce": {
      "type": "http",
      "url": "https://ticketsauce.usefulapi.io/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.io-usefulapi-ticketsauce]
url = "https://ticketsauce.usefulapi.io/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "io-usefulapi-ticketsauce": {
      "type": "remote",
      "url": "https://ticketsauce.usefulapi.io/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add io-usefulapi-ticketsauce --url 'https://ticketsauce.usefulapi.io/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  io-usefulapi-ticketsauce:
    url: "https://ticketsauce.usefulapi.io/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "io-usefulapi-ticketsauce": {
      "Transport": "http",
      "Url": "https://ticketsauce.usefulapi.io/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add io-usefulapi-ticketsauce -t streamable-http -u 'https://ticketsauce.usefulapi.io/mcp'
```

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-ticketsauce": {
      "type": "http",
      "url": "https://ticketsauce.usefulapi.io/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-02 (score 18, −49)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: pass → unverified
- [security regression] Stability: 0.20 → unverified
- [functional regression] Schema quality: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-01 (score 67, +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-10-31 (score 66, +3)

- [security improvement] Authorization: partial → pass
- [functional improvement] MCP protocol: fail → pass
- [functional] New prompt “audit_promo_code_use”
- [functional] New prompt “find_a_buyer_s_order_and_tickets”
- [functional] New prompt “pull_check_in_ids_for_door_reconciliation”
- [functional] New prompt “review_recent_orders_for_an_event”
- [functional] New prompt “review_the_events_you_are_running”
- [functional] MCP protocol version: 2025-06-18 → 2025-11-25
- [functional] Server version: 1.7.0 → 1.9.0
- [functional] Server version: 1.6.0 → 1.7.0
- [functional] Server version: 1.5.2 → 1.6.0

### 2026-10-30 (score 63, 0)

- [functional] Server version: 1.5.1 → 1.5.2
- [functional] Server version: 1.5.0 → 1.5.1

### 2026-10-29 (score 63, +1)

- [functional] Server version: 1.4.0 → 1.5.0
- [functional] Server version: 1.3.0 → 1.4.0

### 2026-10-28 (score 62, 0)

- [functional] Server version: 1.1.0 → 1.3.0

### 2026-10-27 (score 62, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional] Server version: 1.0.0 → 1.1.0

### 2026-10-26 (score 61)

First indexed and scored.

## MCP tools (5)

### `ticketsauce_list_events` (~363 tokens)

List events

List the events you own on Ticketsauce with id, name, slug, start/end (local and UTC), venue address, timezone, organization, privacy type, whether tickets are on sale, and the event and ticket-shop URLs. Filter by start/end/created dates (yyyy-mm-dd, UTC), a phrase such as this_weekend, organization or partner. The API has no paging for events. Use the event id for orders and check-ins. GET /v2/events.

Input parameters:

- `active_only` (boolean): Only active events (the API default is true).
- `created_after` (string): Events created on/after this date, yyyy-mm-dd.
- `created_before` (string): Events created on/before this date, yyyy-mm-dd.
- `end_after` (string): Events ending on/after this date, yyyy-mm-dd.
- `end_before` (string): Events ending on/before this date, yyyy-mm-dd.
- `inactive_only` (boolean): Only inactive events (the API default is false).
- `include_performers` (boolean): Include the performers of each event.
- `organization_id` (string): Only events of this organization.
- `partner_id` (string): Only events of this partner.
- `privacy_type` (string): public (API default), unlisted or all.
- `sort_by` (string): Sort field (default date).
- `sort_dir` (string): Sort direction (default asc).
- `start_after` (string): Events starting on/after this date, yyyy-mm-dd.
- `start_before` (string): Events starting on/before this date, yyyy-mm-dd.
- `start_phrase` (string): Events starting in a named period (today, this_weekend, next_month...).

### `ticketsauce_get_event` (~110 tokens)

Get event

One event by id or slug: everything in the list plus summary and description (text and HTML), order_count and ticket_count (tickets sold, not refunded or voided). Replies are cached for an hour. GET /v2/event/{id_or_slug}.

Input parameters:

- `event` (string, required): Event id (UUID) or event slug, as returned by ticketsauce_list_events.
- `include_performers` (boolean): Include the performers.
- `photos` (boolean): Include the photo gallery records.

### `ticketsauce_list_orders` (~400 tokens)

List orders of an event

Orders of one event, oldest first by default (pass sort_dir desc for newest first): order id, status, buyer name, email, phone and address, totals (total_paid, refund_amount, taxes, fees), promo code, ticket_count, paid date. Contains your customers' personal data. Filter by order or modified dates, a phrase, buyer email or last name (exact match), totals, or promo use; optionally embed tickets, questionnaire answers and line-item fees. Paged: per_page up to 500, then pass next_page. Replies are cached for an hour. GET /v2/orders/{event_id}.

Input parameters:

- `event_id` (string, required): Event id (UUID) from ticketsauce_list_events.
- `modified_after` (string): Modified on/after (UTC).
- `modified_before` (string): Modified on/before (UTC).
- `ordered_after` (string): Ordered on/after (UTC).
- `ordered_before` (string): Ordered on/before (UTC).
- `ordered_phrase` (string): Ordered in a named period.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Orders per page, 1-500 (default 100).
- `promo_used_only` (boolean): Only orders that used a promo code.
- `q` (string): Exact buyer email address or last name.
- `return_line_item_fees` (boolean): Include line-item fees.
- `return_questionnaires` (boolean): Include questionnaire answers.
- `return_tickets` (boolean): Include each order's tickets.
- `sort_by` (string): Sort field (default date).
- `sort_dir` (string): Sort direction (default asc).
- `total_above` (number): Only orders with a total greater than this.
- `total_below` (number): Only orders with a total less than this.

### `ticketsauce_get_order` (~76 tokens)

Get order

One order by id, with its buyer details, totals and its tickets (ticket type, name, price, redeemed state, promo code). Contains personal data. Replies are cached for an hour. GET /v2/order/{order_id}.

Input parameters:

- `order_id` (string, required): Order id (UUID) from ticketsauce_list_orders.

### `ticketsauce_list_checkin_ids` (~144 tokens)

List ticket check-in ids

The ticket check-in ids of one event, for door/scanning reconciliation (the API documents no response fields; the reply is returned as is). Paged: per_page up to 5000, then pass next_page. Replies are cached for 5 minutes. GET /v2/tickets/checkin_ids/{event_id}.

Input parameters:

- `event_id` (string, required): Event id (UUID) from ticketsauce_list_events.
- `page` (integer): Page number, from 1 (default 1). Pass the previous reply's next_page.
- `per_page` (integer): Ids per page, 1-5000 (default 1000).

## Diagnostics

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

## Score history

- 2026-11-05: 18
- 2026-11-04: 18
- 2026-11-03: 18
- 2026-11-02: 18
- 2026-11-01: 67
- 2026-10-31: 66
- 2026-10-30: 63
- 2026-10-29: 63
- 2026-10-28: 62
- 2026-10-27: 62
- 2026-10-26: 61

## Common questions

### What is the Ticketsauce MCP by usefulapi server?

Ticketsauce MCP by usefulapi is listed in the public MCP registry as io.usefulapi/ticketsauce. Read Ticketsauce events, orders and ticket check-in IDs (read-only). This page covers its hosted endpoint (https://ticketsauce.usefulapi.io/mcp).

### Is the Ticketsauce MCP by usefulapi server safe to use?

Ticketsauce MCP by usefulapi scores 18 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 Ticketsauce MCP by usefulapi server expose?

Ticketsauce MCP by usefulapi exposes 5 tools: ticketsauce_list_events, ticketsauce_get_event, ticketsauce_list_orders, ticketsauce_get_order, ticketsauce_list_checkin_ids. Their descriptions and schemas cost roughly 1,093 tokens of context every time the server is loaded.

### Does the Ticketsauce MCP by usefulapi server require authentication?

Its publisher declares no required credentials for Ticketsauce MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

### Is the Ticketsauce MCP by usefulapi server still maintained?

Ticketsauce MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 5 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 Ticketsauce MCP by usefulapi server?

VerifyMCP ran 4 checks on Ticketsauce MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Ticketsauce MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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://ticketsauce.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Website: https://usefulapi.io/ticketsauce/
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-ticketsauce/ticketsauce.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-ticketsauce/ticketsauce/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/io-usefulapi-ticketsauce/ticketsauce.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-ticketsauce/ticketsauce