Humanitix MCP by usefulapi

by usefulapi.io · remote · no sign-in to list tools · v1.16.3 · published by io.usefulapi

Read Humanitix events, orders, tickets and live check-in counts, and check tickets in or out.

Deletes · 4

Compare Registry entry

15 tools: 4 can delete or cancel things and 11 only read.

Scanned Oct 21, 2026

Deletes or cancels4Claude Code: deny: see these tools
Can't be undone0Claude Code: ask
Changes things0Claude Code: ask
Only reads11Claude Code: allow: see these tools

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

15 tools

Deletes or cancels 4Removes, cancels or revokes something.Claude Code: deny

humanitix_check_in_ticketMark a ticket as checked in at the door.No findings
Why it is in this group
- The description's first verb is "mark": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Mark a ticket as checked in at the door. Returns any scanning messages configured for that ticket. Undo with humanitix_check_out_ticket. Humanitix: POST /v1/events/{eventId}/tickets/{ticketId}/check-in.
Annotations the server declares
- title: Check in a ticket
- destructiveHint: true
humanitix_check_out_ticketMark a checked-in ticket as checked out (e.g.No findings
Why it is in this group
- The description's first verb is "mark": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Mark a checked-in ticket as checked out (e.g. to undo a mistaken check-in or track re-entry). Humanitix: POST /v1/events/{eventId}/tickets/{ticketId}/check-out.
Annotations the server declares
- title: Check out a ticket
- destructiveHint: true
humanitix_create_eventCreate a base event (name, description, timezone, one or more date ranges, location, keywords, classification).No findings
Why it is in this group
- The name "humanitix_create_event" says "create": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Create a base event (name, description, timezone, one or more date ranges, location, keywords, classification). Ticket types are then set up in the Humanitix console. Requires a special permission Humanitix activates on your account (403 otherwise). Humanitix: POST /v1/events.
Annotations the server declares
- title: Create an event
- destructiveHint: true
humanitix_update_eventUpdate an event's name, description, timezone, location, keywords or classification, and add or reschedule dates (date operations CREATE and UPDATE; deleting dates is not exposed).No findings
Why it is in this group
- The name "humanitix_update_event" says "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it
Update an event's name, description, timezone, location, keywords or classification, and add or reschedule dates (date operations CREATE and UPDATE; deleting dates is not exposed). Only fields you pass are sent. Requires a special permission Humanitix activates on your account (403 otherwise). Humanitix: PATCH /v1/events/{eventId}.
Annotations the server declares
- title: Update an event
- destructiveHint: true

Only reads 11Looks things up and changes nothing.Claude Code: allow

humanitix_get_check_in_countHow many attendees have checked in for one date of an event, in total and per ticket type (ticket types with sales only, most check-ins first).No findings
Why it is in this group
- The name "humanitix_get_check_in_count" says "get": a word for reading.
Description, as the server wrote it
How many attendees have checked in for one date of an event, in total and per ticket type (ticket types with sales only, most check-ins first). BETA endpoint. Humanitix: GET /v1/events/{eventId}/check-in-count.
Annotations the server declares
- title: Get check-in count
- readOnlyHint: true
humanitix_get_eventFetch one event: name, description, URL, dates (each date's _id is the event_date_id other tools take), ticket types, packaged tickets, pricing, location, capacity and publish stat…No findings
Why it is in this group
- The name "humanitix_get_event" says "get": a word for reading.
Description, as the server wrote it
Fetch one event: name, description, URL, dates (each date's _id is the event_date_id other tools take), ticket types, packaged tickets, pricing, location, capacity and publish state. Humanitix: GET /v1/events/{eventId}.
Annotations the server declares
- title: Get one event
- readOnlyHint: true
humanitix_get_orderFetch one order of an event, with its totals breakdown, answers to checkout questions and buyer details.No findings
Why it is in this group
- The name "humanitix_get_order" says "get": a word for reading.
Description, as the server wrote it
Fetch one order of an event, with its totals breakdown, answers to checkout questions and buyer details. Humanitix: GET /v1/events/{eventId}/orders/{orderId}.
Annotations the server declares
- title: Get one order
- readOnlyHint: true
humanitix_get_tagFetch one tag by id.No findings
Why it is in this group
- The name "humanitix_get_tag" says "get": a word for reading.
Description, as the server wrote it
Fetch one tag by id. Humanitix: GET /v1/tags/{tagId}.
Annotations the server declares
- title: Get one tag
- readOnlyHint: true
humanitix_get_ticketFetch one ticket of an event, including its check-in history and any swap history.No findings
Why it is in this group
- The name "humanitix_get_ticket" says "get": a word for reading.
Description, as the server wrote it
Fetch one ticket of an event, including its check-in history and any swap history. Humanitix: GET /v1/events/{eventId}/tickets/{ticketId}.
Annotations the server declares
- title: Get one ticket
- readOnlyHint: true
humanitix_list_eventsList your events, newest first, with dates, ticket types, pricing and capacity.No findings
Why it is in this group
- The name "humanitix_list_events" says "list": a word for reading.
Description, as the server wrote it
List your events, newest first, with dates, ticket types, pricing and capacity. Filter to upcoming events or events changed since a date. Paged (total/page/pageSize in the response). Humanitix: GET /v1/events.
Annotations the server declares
- title: List events
- readOnlyHint: true
humanitix_list_global_event_datesList individual event dates from across the platform — one row per date — with the public on-sale status of every ticket type.No findings
Why it is in this group
- The name "humanitix_list_global_event_dates" says "list": a word for reading.
Description, as the server wrote it
List individual event dates from across the platform — one row per date — with the public on-sale status of every ticket type. Requires a special permission Humanitix activates on your account (403 otherwise). Paged. Humanitix: GET /v1/global/event-dates.
Annotations the server declares
- title: List platform-wide event dates
- readOnlyHint: true
humanitix_list_global_eventsList public events from across the whole Humanitix platform, filterable by type, category and subcategory.No findings
Why it is in this group
- The name "humanitix_list_global_events" says "list": a word for reading.
Description, as the server wrote it
List public events from across the whole Humanitix platform, filterable by type, category and subcategory. Requires a special permission Humanitix activates on your account (403 otherwise). Paged. Humanitix: GET /v1/global/events.
Annotations the server declares
- title: List platform-wide events
- readOnlyHint: true
humanitix_list_ordersList the orders for an event (optionally one date of it): buyer name/email, financial status, totals, discounts, payment type and sales channel.No findings
Why it is in this group
- The name "humanitix_list_orders" says "list": a word for reading.
Description, as the server wrote it
List the orders for an event (optionally one date of it): buyer name/email, financial status, totals, discounts, payment type and sales channel. Paged. Humanitix: GET /v1/events/{eventId}/orders.
Annotations the server declares
- title: List an event's orders
- readOnlyHint: true
humanitix_list_tagsList the tags you use to group events (events carry them in tagIds).No findings
Why it is in this group
- The name "humanitix_list_tags" says "list": a word for reading.
Description, as the server wrote it
List the tags you use to group events (events carry them in tagIds). Paged. Humanitix: GET /v1/tags.
Annotations the server declares
- title: List tags
- readOnlyHint: true
humanitix_list_ticketsList the tickets (attendees) for an event, optionally one date of it and complete or cancelled only: attendee name, ticket type, price, check-in state and seating.No findings
Why it is in this group
- The name "humanitix_list_tickets" says "list": a word for reading.
Description, as the server wrote it
List the tickets (attendees) for an event, optionally one date of it and complete or cancelled only: attendee name, ticket type, price, check-in state and seating. Paged. Humanitix: GET /v1/events/{eventId}/tickets.
Annotations the server declares
- title: List an event's tickets
- readOnlyHint: 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.

Install

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

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

Run in a terminal.

Claude Code permissions

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

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__humanitix__humanitix_list_events",
      "mcp__humanitix__humanitix_get_event",
      "mcp__humanitix__humanitix_get_check_in_count",
      "mcp__humanitix__humanitix_list_orders",
      "mcp__humanitix__humanitix_get_order",
      "mcp__humanitix__humanitix_list_tickets",
      "mcp__humanitix__humanitix_get_ticket",
      "mcp__humanitix__humanitix_list_tags",
      "mcp__humanitix__humanitix_get_tag",
      "mcp__humanitix__humanitix_list_global_events",
      "mcp__humanitix__humanitix_list_global_event_dates"
    ],
    "ask": [],
    "deny": [
      "mcp__humanitix__humanitix_check_in_ticket",
      "mcp__humanitix__humanitix_check_out_ticket",
      "mcp__humanitix__humanitix_create_event",
      "mcp__humanitix__humanitix_update_event"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as humanitix. Review it before you use it.

Keep track

Get told when this server's tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/io.usefulapi/humanitix/changes.xml

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

Anlyon alternative

4 of these tools change something. Run those 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 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 →

Compare with other servers for the same product.

Source: MCP Registry · repository. Synced Oct 21, 2026, 19:23 UTC.

For agents: Markdown · JSON · report this listing