Skip to content

Ticketsauce MCP by usefulapi

io.usefulapi/ticketsauceusefulapi.iostreamable-httpv1.16.4Scanned

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

5 tools: 5 only read.

Tools: 0 delete, 0 irreversible, 0 write, 5 read.
  • Reads private data · 2
  • Reads text others write · 5
  • Can send data out · 0
  • No findings

The remote endpoint did not answer the last look. Remote posture

Anlyon alternative

Run the operations that matter as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

What the Ticketsauce MCP by usefulapi can do

The Ticketsauce MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 5 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.

2 tools read private data (ticketsauce_list_orders and ticketsauce_list_checkin_ids); 5 tools bring in text other people can write (ticketsauce_list_events, ticketsauce_get_event, ticketsauce_list_orders and 2 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Last scanned Oct 26, 2026, version 1.16.4.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

5 tools

Only reads 5Show 5 read-only tools
  • ticketsauce_get_eventOne 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).Reads text others writeNo findings

    Why it is in this group

    • The name "ticketsauce_get_event" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "html": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get event
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ticketsauce_get_orderOne order by id, with its buyer details, totals and its tickets (ticket type, name, price, redeemed state, promo code).Reads text others writeNo findings

    Why it is in this group

    • The name "ticketsauce_get_order" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: Get order
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ticketsauce_list_checkin_idsThe ticket check-in ids of one event, for door/scanning reconciliation (the API documents no response fields; the reply is returned as is).Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "ticketsauce_list_checkin_ids" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "document": it reads documents.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: List check-in ids
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ticketsauce_list_eventsList 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 eve…Reads text others writeNo findings

    Why it is in this group

    • The name "ticketsauce_list_events" says "list": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "list" and "ticket": it reads issues, which other people can write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: List events
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true
  • ticketsauce_list_ordersOrders 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…Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "ticketsauce_list_orders" says "list": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "email": it reads mail.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    • untrusted-inputThe description's first sentence says "email": it reads inbound email, which other people can write.
    Description, as the server wrote it
    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}.

    Annotations the server declares

    • title: List orders
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data2
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write5
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

The remote endpoint did not answer the last look

Looked at Nov 17, 2026, 15:25 UTC, unchanged since Oct 26, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
no
HTTP status of an anonymous initialize
not observed
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed

The probe stopped: The server redirected a POST to a different request.

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.16.4. Values in angle brackets are yours to fill in.

claude mcp add --transport http ticketsauce https://ticketsauce.usefulapi.io/mcp
claude mcp add --transport http ticketsauce https://ticketsauce.usefulapi.io/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__ticketsauce__ticketsauce_list_events",
      "mcp__ticketsauce__ticketsauce_get_event",
      "mcp__ticketsauce__ticketsauce_list_orders",
      "mcp__ticketsauce__ticketsauce_get_order",
      "mcp__ticketsauce__ticketsauce_list_checkin_ids"
    ],
    "ask": [],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ticketsauce. Review it before you use it.

Capability tags behind 5 rules
  • mcp__ticketsauce__ticketsauce_list_events untrusted-input
  • mcp__ticketsauce__ticketsauce_get_event untrusted-input
  • mcp__ticketsauce__ticketsauce_list_orders private-data, untrusted-input
  • mcp__ticketsauce__ticketsauce_get_order untrusted-input
  • mcp__ticketsauce__ticketsauce_list_checkin_ids private-data, untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.usefulapi/ticketsauce/verify?hash=2f5e68d14906a26b281b4ba52f0efb4730dd3ec8a3f76c48fd9b89fd8fcea923" | jq -e '.changed == false'

Pinned hash 2f5e68d14906, from Oct 26, 2026, 00:26 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.usefulapi/ticketsauce/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.usefulapi/ticketsauce
[![Anlyon Radar](https://radar.anlyon.com/badge/io.usefulapi/ticketsauce.svg)](https://radar.anlyon.com/servers/io.usefulapi/ticketsauce)

Source: MCP Registry · repository. Synced Nov 18, 2026, 11:19 UTC.

Ticketsauce MCP by usefulapi: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Ticketsauce MCP by usefulapi safe?

No scan can promise that. What its definitions show: 5 tools, all of which only read, and 0 findings from fixed checks. Read-only tools can still pass private data to a model.

Can the Ticketsauce MCP by usefulapi delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Ticketsauce MCP by usefulapi do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Ticketsauce MCP by usefulapi have?

5 tools: 5 read. ticketsauce_list_events, ticketsauce_get_event, ticketsauce_list_orders, ticketsauce_get_order and ticketsauce_list_checkin_ids.

Does the Ticketsauce MCP by usefulapi need sign-in or OAuth?

Its remote endpoint did not answer the last anonymous look.

Does the Ticketsauce MCP by usefulapi send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Ticketsauce MCP by usefulapi changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Oct 26, 2026.