io.usefulapi/humanitix
REMOTE · HUMANITIX.USEFULAPI.IO · SCANNED OCT 4
Read Humanitix events, orders, tickets and live check-in counts, and check tickets in or out.
Available components
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. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
remote · humanitix.usefulapi.io
claude mcp add --transport http io-usefulapi-humanitix 'https://humanitix.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-humanitix": {
"url": "https://humanitix.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-humanitix": {
"type": "http",
"url": "https://humanitix.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-humanitix] url = "https://humanitix.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-humanitix": {
"type": "remote",
"url": "https://humanitix.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-humanitix --url 'https://humanitix.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-humanitix:
url: "https://humanitix.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-humanitix": {
"Transport": "http",
"Url": "https://humanitix.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-humanitix -t streamable-http -u 'https://humanitix.usefulapi.io/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Oct 26 +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.
- 2 Oct 26 +43
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Endpoint reachability: behind authorisation → reachable ▲ functional
- Stability: unverified → 0.07 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Server version: 1.0.0 → 1.5.1 functional
- 1 Oct 26 −25
- Endpoint reachability: reachable → behind authorisation ▼ security
- Tool safety: pass → unverified ▼ security
- 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. security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: Schema blocked by authentication: the endpoint requires auth we don't have to read it. functional
- 30 Sept 26 +40
- Injection markers: unverified → pass ▲ security
- 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. security
- MCP protocol: unverified → fail ▼ functional
- 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 functional
- 29 Sept 26 18
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://humanitix.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of humanitix.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://humanitix.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://humanitix.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://humanitix.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://humanitix.usefulapi.io/mcp |
| Authorisation server | https://humanitix.usefulapi.io |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://humanitix.usefulapi.io/mcp | Verified | 200 | |
| http (plaintext) | http://humanitix.usefulapi.io/mcp | HTTPS enforced | 301 | https://humanitix.usefulapi.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
humanitix_check_in_ticket Check in a ticket ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | 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 | yes | The ticket id (24-character hex id). |
No output schema declared.
No examples provided.
humanitix_check_out_ticket Check out a ticket ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | 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 | yes | The ticket id (24-character hex id). |
No output schema declared.
No examples provided.
humanitix_create_event Create an event ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| classification | object | – | How the event is classified. subcategory must belong to category. |
| dates | array | yes | 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 | yes | 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 | yes | IANA timezone, e.g. Australia/Sydney or Pacific/Auckland. |
No output schema declared.
No examples provided.
humanitix_get_check_in_count Get check-in count ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_date_id | string | yes | The event date id (24-character hex id). |
| event_id | string | yes | The event id (24-character hex id). |
No output schema declared.
No examples provided.
humanitix_get_event Get one event ~116
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | 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. |
No output schema declared.
No examples provided.
humanitix_get_order Get one order ~116
Fetch one order of an event, with its totals breakdown, answers to checkout questions and buyer details. Humanitix: GET /v1/events/{eventId}/orders/{orderId}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | The event id (24-character hex id). |
| order_id | string | yes | 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. |
No output schema declared.
No examples provided.
humanitix_get_tag Get one tag ~47
Fetch one tag by id. Humanitix: GET /v1/tags/{tagId}.
| Name | Type | Req | Description |
|---|---|---|---|
| tag_id | string | yes | The tag id (24-character hex id). |
No output schema declared.
No examples provided.
humanitix_get_ticket Get one ticket ~113
Fetch one ticket of an event, including its check-in history and any swap history. Humanitix: GET /v1/events/{eventId}/tickets/{ticketId}.
| Name | Type | Req | Description |
|---|---|---|---|
| event_id | string | yes | 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 | yes | The ticket id (24-character hex id). |
No output schema declared.
No examples provided.
humanitix_list_events List events ~193
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
humanitix_list_global_event_dates List platform-wide event dates ~212
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
humanitix_list_global_events List platform-wide events ~206
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
humanitix_list_orders List an event's orders ~209
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_date_id | string | – | The event date id (24-character hex id). |
| event_id | string | yes | 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. |
No output schema declared.
No examples provided.
humanitix_list_tags List tags ~81
List the tags you use to group events (events carry them in tagIds). Paged. Humanitix: GET /v1/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | Page number, starting at 1. Defaults to 1. |
| page_size | integer | – | Results per page, 1-100 (API default 100). |
No output schema declared.
No examples provided.
humanitix_list_tickets List an event's tickets ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| event_date_id | string | – | The event date id (24-character hex id). |
| event_id | string | yes | 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. |
No output schema declared.
No examples provided.
humanitix_update_event Update an event ~256
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}.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.