Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Read Humanitix events, orders, tickets and live check-in counts, and check tickets in or out.
0 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Outdated check
Last connection measurement is over 24 hours old. Current availability is unknown.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using Humanitix MCP by usefulapi
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http humanitix-mcp-by-usefulapi https://humanitix.usefulapi.io/mcpCapabilities
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.
DiscoveredMark 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.
DiscoveredCreate 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.
DiscoveredHow 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.
DiscoveredFetch 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}.
DiscoveredFetch one order of an event, with its totals breakdown, answers to checkout questions and buyer details. Humanitix: GET /v1/events/{eventId}/orders/{orderId}.
DiscoveredFetch one tag by id. Humanitix: GET /v1/tags/{tagId}.
DiscoveredFetch one ticket of an event, including its check-in history and any swap history. Humanitix: GET /v1/events/{eventId}/tickets/{ticketId}.
DiscoveredList 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.
DiscoveredList 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.
DiscoveredList 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.
DiscoveredList 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.
DiscoveredList the tags you use to group events (events carry them in tagIds). Paged. Humanitix: GET /v1/tags.
DiscoveredList 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.
DiscoveredUpdate 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}.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 62 ms | 15 |