Humanitix MCP by usefulapi

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 网店与支付

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://humanitix.usefulapi.io/mcp

claude mcp add --transport http humanitix https://humanitix.usefulapi.io/mcp

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

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

https://humanitix.usefulapi.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• humanitix_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.

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

• humanitix_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.

• humanitix_list_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.

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

• humanitix_list_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.

• humanitix_get_ticket

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

• humanitix_list_tags

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

• humanitix_get_tag

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

• humanitix_list_global_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.

• humanitix_list_global_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.

• humanitix_check_in_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.

• humanitix_check_out_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.

• humanitix_create_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.

• humanitix_update_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 (4

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 usefulapi.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 28 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 15 个工具描述，未发现针对 AI 的隐藏指令

与“网店与支付”中的其他服务器比较i

• 星标数多于此分类中其他 1743 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 1743 个服务器的 92% 更新
• 基础检查结果等于或优于此分类中其他 1743 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

{