Skip to content

Humanitix MCP by usefulapi

io.usefulapi/humanitixusefulapi.iostreamable-httpv1.40.4Scanned

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

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

Tools: 4 delete, 0 irreversible, 0 write, 11 read.
  • Reads private data · 1
  • Reads text others write · 7
  • Can send data out · 0
  • No findings

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

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 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 Humanitix MCP by usefulapi can do

The Humanitix MCP by usefulapi is published by usefulapi.io, a domain the MCP Registry verified. It has 15 tools. It can delete or cancel things (4 tools: humanitix_check_in_ticket, humanitix_check_out_ticket, humanitix_create_event and humanitix_update_event). 11 tools only read.

1 tool reads private data (humanitix_list_orders); 7 tools bring in text other people can write (humanitix_list_events, humanitix_get_event, humanitix_get_check_in_count and 4 more).

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

Last scanned Oct 25, 2026, version 1.40.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.

15 tools

Deletes or cancels 4Claude 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 11Show 11 read-only tools
  • 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).Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "ticket": it reads issues, which other people can write.
    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…Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe description's first sentence says "fetch" and "url": it reads web pages, which anyone can write.
    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.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe name "humanitix_get_ticket" says "get" and "ticket": it reads issues, which other people can write.
    • untrusted-inputThe description's first sentence says "fetch" and "ticket": it reads issues, which other people can write.
    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.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • 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 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.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • 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 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.Reads private dataReads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • private-dataThe description's first sentence says "list" and "email": it reads mail.
    • untrusted-inputThe description's first sentence says "list" and "email": it reads inbound email, which other people can write.
    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.Reads text others writeNo findings

    Why it is in this group

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

    What it can reach

    • untrusted-inputThe name "humanitix_list_tickets" says "list" and "ticket": it reads issues, which other people can write.
    • 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 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.

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 data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write7
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 20, 2026, 19:36 UTC, unchanged since Oct 29, 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.

Posture changes

  1. Oct 29, 2026
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://humanitix.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://humanitix.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

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.

  1. PostureRemote posture changed. Reachable: yes -> no; HTTP status of an anonymous initialize: 200 -> none; tools/list served without credentials: yes -> no (and 6 more).View diff
    • Reachable: yes to no
    • HTTP status of an anonymous initialize: 200 to none
    • tools/list served without credentials: yes to no
    • Tools that change things, listed without credentials: 4 to 0
    • Protocol version: 2025-06-18 to none
    • RFC 9728 protected resource metadata: https://humanitix.usefulapi.io/.well-known/oauth-protected-resource/mcp to none
    • Authorization servers: https://humanitix.usefulapi.io to none
    • Dynamic client registration: yes to not observed
    • Client ID metadata documents: no to not observed

Install

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

claude mcp add --transport http humanitix https://humanitix.usefulapi.io/mcp
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as humanitix. Review it before you use it.

Capability tags behind 7 rules
  • mcp__humanitix__humanitix_list_events untrusted-input
  • mcp__humanitix__humanitix_get_event untrusted-input
  • mcp__humanitix__humanitix_get_check_in_count untrusted-input
  • mcp__humanitix__humanitix_list_orders private-data, untrusted-input
  • mcp__humanitix__humanitix_list_tickets untrusted-input
  • mcp__humanitix__humanitix_get_ticket untrusted-input
  • mcp__humanitix__humanitix_list_global_event_dates 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/humanitix/verify?hash=b50ec9745ce467d0a32606ad03708f4fb558387153e3462fe6dde98eddf513fd" | jq -e '.changed == false'

Pinned hash b50ec9745ce4, from Oct 25, 2026, 23:19 UTC.

Watch

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

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

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

Badge

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

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

Humanitix MCP by usefulapi: questions and answers

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

Is the Humanitix MCP by usefulapi safe?

No scan can promise that. What its definitions show: 15 tools, 4 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Humanitix MCP by usefulapi delete data?

Yes. 4 tools can delete, cancel or revoke something: humanitix_check_in_ticket, humanitix_check_out_ticket, humanitix_create_event and humanitix_update_event.

Can the Humanitix 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 Humanitix MCP by usefulapi have?

15 tools: 4 destructive, 11 read. humanitix_check_in_ticket, humanitix_check_out_ticket, humanitix_create_event, humanitix_update_event, humanitix_list_events, humanitix_get_event, humanitix_get_check_in_count, humanitix_list_orders and 7 more.

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

Its remote endpoint did not answer the last anonymous look.

Does the Humanitix 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 Humanitix MCP by usefulapi changed its tools?

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