# io.usefulapi/humanitix (remote · humanitix.usefulapi.io)

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

- Trust score: 77/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

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

## Channel facts

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

## 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-10-04.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2357 tokens (~157/item across 15 items; 15 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 13/100
  - Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the io.usefulapi/humanitix MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "io-usefulapi-humanitix": {
      "type": "http",
      "url": "https://humanitix.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-10-04 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-02 (score 76, +43)

- [security improvement] Authorization: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: behind authorisation → reachable
- [functional improvement] Stability: unverified → 0.07
- [functional improvement] Tool coverage: unverified → 100
- [functional] Server version: 1.0.0 → 1.5.1

### 2026-10-01 (score 33, −25)

- [security regression] Endpoint reachability: reachable → behind authorisation
- [security regression] Tool safety: pass → unverified
- [security improvement] HTTPS: unverified → pass
- [security] Authorization: Authorisation not fully verified: no authorisation is required to connect, but we couldn't read the whole tool list to see what that exposes.
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it.

### 2026-09-30 (score 58, +40)

- [security improvement] Injection markers: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [security] Authorization: Authorisation not fully verified: this server exposes a tool marked destructive (humanitix_check_in_ticket) and its handshake is open, but we could not confirm whether a tool call is gated, so we do not assert it is callable unauthenticated.
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Schema quality: excellent
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: fail
- [functional] First check of Tool coverage: 100

### 2026-09-29 (score 18)

First indexed and scored.

## MCP tools (15)

### `humanitix_list_events` (~193 tokens)

List events

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.

Input parameters:

- `in_future_only` (boolean): Only events whose end date is in the future.
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `page` (integer): Page number, starting at 1. Defaults to 1.
- `page_size` (integer): Results per page, 1-100 (API default 100).
- `since` (string): Only results created/updated since this ISO 8601 date-time, e.g. 2026-01-01T00:00:00.000Z.

### `humanitix_get_event` (~116 tokens)

Get one event

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}.

Input parameters:

- `event_id` (string, required): The event id (24-character hex id).
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.

### `humanitix_get_check_in_count` (~99 tokens)

Get check-in count

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.

Input parameters:

- `event_date_id` (string, required): The event date id (24-character hex id).
- `event_id` (string, required): The event id (24-character hex id).

### `humanitix_list_orders` (~209 tokens)

List an event's orders

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.

Input parameters:

- `event_date_id` (string): The event date id (24-character hex id).
- `event_id` (string, required): The event id (24-character hex id).
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `page` (integer): Page number, starting at 1. Defaults to 1.
- `page_size` (integer): Results per page, 1-100 (API default 100).
- `since` (string): Only results created/updated since this ISO 8601 date-time, e.g. 2026-01-01T00:00:00.000Z.

### `humanitix_get_order` (~116 tokens)

Get one order

Fetch one order of an event, with its totals breakdown, answers to checkout questions and buyer details. Humanitix: GET /v1/events/{eventId}/orders/{orderId}.

Input parameters:

- `event_id` (string, required): The event id (24-character hex id).
- `order_id` (string, required): The order id (24-character hex id).
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.

### `humanitix_list_tickets` (~227 tokens)

List an event's tickets

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.

Input parameters:

- `event_date_id` (string): The event date id (24-character hex id).
- `event_id` (string, required): The event id (24-character hex id).
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `page` (integer): Page number, starting at 1. Defaults to 1.
- `page_size` (integer): Results per page, 1-100 (API default 100).
- `since` (string): Only results created/updated since this ISO 8601 date-time, e.g. 2026-01-01T00:00:00.000Z.
- `status` (string): Only tickets with this status.

### `humanitix_get_ticket` (~113 tokens)

Get one ticket

Fetch one ticket of an event, including its check-in history and any swap history. Humanitix: GET /v1/events/{eventId}/tickets/{ticketId}.

Input parameters:

- `event_id` (string, required): The event id (24-character hex id).
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `ticket_id` (string, required): The ticket id (24-character hex id).

### `humanitix_list_tags` (~81 tokens)

List tags

List the tags you use to group events (events carry them in tagIds). Paged. Humanitix: GET /v1/tags.

Input parameters:

- `page` (integer): Page number, starting at 1. Defaults to 1.
- `page_size` (integer): Results per page, 1-100 (API default 100).

### `humanitix_get_tag` (~47 tokens)

Get one tag

Fetch one tag by id. Humanitix: GET /v1/tags/{tagId}.

Input parameters:

- `tag_id` (string, required): The tag id (24-character hex id).

### `humanitix_list_global_events` (~206 tokens)

List platform-wide events

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.

Input parameters:

- `category` (string): Event category, e.g. music.
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `page` (integer): Page number, starting at 1. Defaults to 1.
- `page_size` (integer): Results per page, 1-100 (API default 100).
- `subcategory` (string): Subcategory within the category (e.g. jazz for music). Requires category.
- `type` (string): Event type, e.g. concertOrPerformance.
- `with_artists_only` (boolean): Only events that list artists.

### `humanitix_list_global_event_dates` (~212 tokens)

List platform-wide event dates

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.

Input parameters:

- `category` (string): Event category, e.g. music.
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `page` (integer): Page number, starting at 1. Defaults to 1.
- `page_size` (integer): Results per page, 1-100 (API default 100).
- `subcategory` (string): Subcategory within the category (e.g. jazz for music). Requires category.
- `type` (string): Event type, e.g. concertOrPerformance.
- `with_artists_only` (boolean): Only events that list artists.

### `humanitix_check_in_ticket` (~128 tokens)

Check in a ticket

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.

Input parameters:

- `event_id` (string, required): The event id (24-character hex id).
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `ticket_id` (string, required): The ticket id (24-character hex id).

### `humanitix_check_out_ticket` (~123 tokens)

Check out a ticket

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.

Input parameters:

- `event_id` (string, required): The event id (24-character hex id).
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `ticket_id` (string, required): The ticket id (24-character hex id).

### `humanitix_create_event` (~231 tokens)

Create an event

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.

Input parameters:

- `classification` (object): How the event is classified. subcategory must belong to category.
- `dates` (array, required): One or more date ranges (1-700).
- `description` (string): Event description.
- `event_location`: Where the event happens: online, address (geocoded), custom (free text) or toBeAnnounced.
- `keywords` (array): Up to 10 unique search keywords, each 1-25 characters.
- `name` (string, required): Event name.
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `timezone` (string, required): IANA timezone, e.g. Australia/Sydney or Pacific/Auckland.

### `humanitix_update_event` (~256 tokens)

Update an event

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}.

Input parameters:

- `classification` (object): How the event is classified. subcategory must belong to category.
- `dates` (array): Date operations: CREATE a new date range, or UPDATE an existing one by its _id.
- `description` (string): New description.
- `event_id` (string, required): The event id (24-character hex id).
- `event_location`: Where the event happens: online, address (geocoded), custom (free text) or toBeAnnounced.
- `keywords` (array): Up to 10 unique search keywords, each 1-25 characters.
- `name` (string): New event name.
- `override_location` (string): Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region.
- `timezone` (string): New IANA timezone.

## Diagnostics

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

## Score history

- 2026-10-04: 77
- 2026-10-03: 76
- 2026-10-02: 76
- 2026-10-01: 33
- 2026-09-30: 58
- 2026-09-29: 18

## Common questions

### What is the io.usefulapi/humanitix MCP server?

io.usefulapi/humanitix is an MCP server listed in the public MCP registry as io.usefulapi/humanitix. Read Humanitix events, orders, tickets and live check-in counts, and check tickets in or out. This page covers its hosted endpoint (https://humanitix.usefulapi.io/mcp).

### Is the io.usefulapi/humanitix MCP server safe to use?

io.usefulapi/humanitix scores 77 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 io.usefulapi/humanitix MCP server expose?

io.usefulapi/humanitix exposes 15 tools: humanitix_list_events, humanitix_get_event, humanitix_get_check_in_count, humanitix_list_orders, humanitix_get_order, and 10 more. Their descriptions and schemas cost roughly 2,357 tokens of context every time the server is loaded.

### Does the io.usefulapi/humanitix MCP server require authentication?

Yes. io.usefulapi/humanitix asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the io.usefulapi/humanitix MCP server still maintained?

io.usefulapi/humanitix is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://humanitix.usefulapi.io/mcp
- Repository: https://github.com/m190/usefulapi-mcp
- Changelog RSS feed: https://verifymcp.io/servers/io-usefulapi-humanitix/humanitix.xml
- Changelog JSON feed: https://verifymcp.io/servers/io-usefulapi-humanitix/humanitix.json
- HTML version of this page: https://verifymcp.io/servers/io-usefulapi-humanitix/humanitix