io.usefulapi/ticketsauce

None of its 5 tools are described as changing anything. For 5 the reading was uncertain, so no mark is shown.

• ticketsauce_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 …”

  Publisher declares: read-only yes · destructive no · open-world yes

  15 inputs

  • organization_idstring“Only events of this organization.”
  • partner_idstring“Only events of this partner.”
  • start_afterstring“Events starting on/after this date, yyyy-mm-dd.”
  • start_beforestring“Events starting on/before this date, yyyy-mm-dd.”
  • start_phrasestring“Events starting in a named period (today, this_weekend, next_month...).”
  • end_afterstring“Events ending on/after this date, yyyy-mm-dd.”
  • end_beforestring“Events ending on/before this date, yyyy-mm-dd.”
  • created_afterstring“Events created on/after this date, yyyy-mm-dd.”
  • created_beforestring“Events created on/before this date, yyyy-mm-dd.”
  • active_onlyboolean“Only active events (the API default is true).”
  • inactive_onlyboolean“Only inactive events (the API default is false).”
  • privacy_typestring“public (API default), unlisted or all.”
  • sort_bystring“Sort field (default date).”
  • sort_dirstring“Sort direction (default asc).”
  • include_performersboolean“Include the performers of each event.”
• ticketsauce_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).”

  Publisher declares: read-only yes · destructive no · open-world yes

  3 inputs, 1 required

  • eventstringrequired“Event id (UUID) or event slug, as returned by ticketsauce_list_events.”
  • photosboolean“Include the photo gallery records.”
  • include_performersboolean“Include the performers.”
• ticketsauce_list_orders

  “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…”

  Publisher declares: read-only yes · destructive no · open-world yes

  17 inputs, 1 required

  • event_idstringrequired“Event id (UUID) from ticketsauce_list_events.”
  • qstring“Exact buyer email address or last name.”
  • ordered_afterstring“Ordered on/after (UTC).”
  • ordered_beforestring“Ordered on/before (UTC).”
  • ordered_phrasestring“Ordered in a named period.”
  • modified_afterstring“Modified on/after (UTC).”
  • modified_beforestring“Modified on/before (UTC).”
  • total_abovenumber“Only orders with a total greater than this.”
  • total_belownumber“Only orders with a total less than this.”
  • promo_used_onlyboolean“Only orders that used a promo code.”
  • return_ticketsboolean“Include each order's tickets.”
  • return_questionnairesboolean“Include questionnaire answers.”
  • return_line_item_feesboolean“Include line-item fees.”
  • sort_bystring“Sort field (default date).”
  • sort_dirstring“Sort direction (default asc).”
  • pageinteger“Page number, from 1 (default 1).”
  • per_pageinteger“Orders per page, 1-500 (default 100).”
• ticketsauce_get_order

  “One order by id, with its buyer details, totals and its tickets (ticket type, name, price, redeemed state, promo code).”

  Publisher declares: read-only yes · destructive no · open-world yes

  1 input, 1 required

  • order_idstringrequired“Order id (UUID) from ticketsauce_list_orders.”
• ticketsauce_list_checkin_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).”

  Publisher declares: read-only yes · destructive no · open-world yes

  3 inputs, 1 required

  • event_idstringrequired“Event id (UUID) from ticketsauce_list_events.”
  • pageinteger“Page number, from 1 (default 1).”
  • per_pageinteger“Ids per page, 1-5000 (default 1000).”

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-27.

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.