A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Nothing to run from here
Humanitix is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
15
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Read Humanitix events, orders, tickets and live check-in counts, and check tickets in or out.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http humanitix-mcp https://humanitix.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# humanitix_list_events, humanitix_get_event, humanitix_get_check_in_count and 12 more
Humanitix costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
USAll 334 servers
usefulapi334 servers
24 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http humanitix-mcp https://humanitix.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
15 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 1. Defaults to 1. |
| page_size | integer | no | Results per page, 1-100 (API default 100). |
| in_future_only | boolean | no | Only events whose end date is in the future. |
| since | string | no | Only results created/updated since this ISO 8601 date-time, e.g. 2026-01-01T00:00:00.000Z. |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event id (24-character hex id). |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event id (24-character hex id). |
| event_date_id | string | yes | The event date id (24-character hex id). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event id (24-character hex id). |
| event_date_id | string | no | The event date id (24-character hex id). |
| page | integer | no | Page number, starting at 1. Defaults to 1. |
| page_size | integer | no | Results per page, 1-100 (API default 100). |
| since | string | no | Only results created/updated since this ISO 8601 date-time, e.g. 2026-01-01T00:00:00.000Z. |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
Fetch one order of an event, with its totals breakdown, answers to checkout questions and buyer details. Humanitix: GET /v1/events/{eventId}/orders/{orderId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| 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 | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event id (24-character hex id). |
| event_date_id | string | no | The event date id (24-character hex id). |
| status | string | no | Only tickets with this status. |
| page | integer | no | Page number, starting at 1. Defaults to 1. |
| page_size | integer | no | Results per page, 1-100 (API default 100). |
| since | string | no | Only results created/updated since this ISO 8601 date-time, e.g. 2026-01-01T00:00:00.000Z. |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
Fetch one ticket of an event, including its check-in history and any swap history. Humanitix: GET /v1/events/{eventId}/tickets/{ticketId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event id (24-character hex id). |
| ticket_id | string | yes | The ticket id (24-character hex id). |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
List the tags you use to group events (events carry them in tagIds). Paged. Humanitix: GET /v1/tags.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 1. Defaults to 1. |
| page_size | integer | no | Results per page, 1-100 (API default 100). |
Fetch one tag by id. Humanitix: GET /v1/tags/{tagId}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| tag_id | string | yes | The tag id (24-character hex id). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 1. Defaults to 1. |
| page_size | integer | no | Results per page, 1-100 (API default 100). |
| type | string | no | Event type, e.g. concertOrPerformance. |
| category | string | no | Event category, e.g. music. |
| subcategory | string | no | Subcategory within the category (e.g. jazz for music). Requires category. |
| with_artists_only | boolean | no | Only events that list artists. |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| page | integer | no | Page number, starting at 1. Defaults to 1. |
| page_size | integer | no | Results per page, 1-100 (API default 100). |
| type | string | no | Event type, e.g. concertOrPerformance. |
| category | string | no | Event category, e.g. music. |
| subcategory | string | no | Subcategory within the category (e.g. jazz for music). Requires category. |
| with_artists_only | boolean | no | Only events that list artists. |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event id (24-character hex id). |
| ticket_id | string | yes | The ticket id (24-character hex id). |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event id (24-character hex id). |
| ticket_id | string | yes | The ticket id (24-character hex id). |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Event name. |
| timezone | string | yes | IANA timezone, e.g. Australia/Sydney or Pacific/Auckland. |
| dates | array | yes | One or more date ranges (1-700). |
| description | string | no | Event description. |
| event_location | no | Where the event happens: online, address (geocoded), custom (free text) or toBeAnnounced. | |
| keywords | array | no | Up to 10 unique search keywords, each 1-25 characters. |
| classification | object | no | How the event is classified. subcategory must belong to category. |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
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}.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | string | yes | The event id (24-character hex id). |
| name | string | no | New event name. |
| description | string | no | New description. |
| timezone | string | no | New IANA timezone. |
| event_location | no | Where the event happens: online, address (geocoded), custom (free text) or toBeAnnounced. | |
| keywords | array | no | Up to 10 unique search keywords, each 1-25 characters. |
| classification | object | no | How the event is classified. subcategory must belong to category. |
| dates | array | no | Date operations: CREATE a new date range, or UPDATE an existing one by its _id. |
| override_location | string | no | Query a region other than your account's own (ISO 3166-1 alpha-2). Humanitix stores data per region. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Humanitix or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.11.1.
1.11.1
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Humanitix can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.