Snipe-IT MCP by usefulapi

它能帮你做什么

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

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 其他

安装

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

你需要

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

你用的是哪个应用？

https://snipe-it.usefulapi.io/mcp

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

{
  "mcpServers": {
    "snipe-it": {
      "url": "https://snipe-it.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "snipe-it": {
      "type": "http",
      "url": "https://snipe-it.usefulapi.io/mcp"
    }
  }
}

https://snipe-it.usefulapi.io/mcp

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

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

它能做什么

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

• snipeit_get_me

  Get the Snipe-IT user this connection acts as: name, username, department, location and permissions. Good first call to confirm the connection. Snipe-IT API: GET /api/v1/users/me.

• snipeit_list_hardware

  List assets (hardware), with status, model, location and assignment. Filter by model, category, location, company, status or assignee. Snipe-IT API: GET /api/v1/hardware.

• snipeit_get_hardware

  Get one asset by its numeric id: asset tag, serial, model, status, assignment, custom fields and checkout history. Snipe-IT API: GET /api/v1/hardware/{id}.

• snipeit_find_hardware_by_tag

  Find one asset by its asset tag, for example ASSET-0001. Snipe-IT API: GET /api/v1/hardware/bytag/{asset_tag}.

• snipeit_find_hardware_by_serial

  Find one asset by its serial number. Snipe-IT API: GET /api/v1/hardware/byserial/{serial}.

• snipeit_list_overdue_audits

  List assets whose physical audit is overdue. Snipe-IT API: GET /api/v1/hardware/audit/overdue.

• snipeit_list_users

  List the users (people) in Snipe-IT, with department and location. Search by name, username, email or employee number. Snipe-IT API: GET /api/v1/users.

• snipeit_get_user

  Get one user by numeric id, with department, location, groups and permissions. Snipe-IT API: GET /api/v1/users/{id}.

• snipeit_list_user_assets

  List the assets currently checked out to one user. Snipe-IT API: GET /api/v1/users/{id}/assets.

• snipeit_list_licenses

  List software licenses with seat counts and expiry. Snipe-IT API: GET /api/v1/licenses.

• snipeit_get_license

  Get one software license by numeric id: seats, product key holder, expiry and supplier. Snipe-IT API: GET /api/v1/licenses/{id}.

• snipeit_list_license_seats

  List the seats of one software license and who holds each seat. Snipe-IT API: GET /api/v1/licenses/{id}/seats.

• snipeit_list_models

  List asset models (the product definitions that assets are created from). Snipe-IT API: GET /api/v1/models.

• snipeit_list_categories

  List categories (asset, accessory, consumable, component or license). Snipe-IT API: GET /api/v1/categories.

• snipeit_list_locations

  List locations (sites, buildings or rooms) with their addresses. Snipe-IT API: GET /api/v1/locations.

• snipeit_list_status_labels

  List status labels (for example Ready to Deploy, Deployed, Broken, Archived) with their ids. Use the ids for status filters and checkouts. Snipe-IT API: GET /api/v1/statuslabels.

• snipeit_get_activity_report

  Read the activity log: who checked out, edited or deleted what, and when. Filter by target or item. Snipe-IT API: GET /api/v1/reports/activity.

• snipeit_checkout_hardware

  Check an asset out to a user, another asset or a location. Changes who holds the asset and sets its status label. Snipe-IT API: POST /api/v1/hardware/{id}/checkout.

• snipeit_checkin_hardware

  Check an asset back in: it leaves its holder and gets the status label you give. Snipe-IT API: POST /api/v1/hardware/{id}/checkin.

基础检查i

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

• ✓ 通过

  作者与仓库一致

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

• … 尚未检查

  仍在维护

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

• … 尚未检查

  有许可证

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

• ✓ 通过

  端点有响应

  在 8 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

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

与“其他”中的其他服务器比较i

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

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

替代选择

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

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

作者的 README

{