Huntress

io.github.WYRE-AI由 GitHub 帳號 WYRE-AI 發布v1.2.24更新於 Nov 4, 2026

MCP server for Huntress — accounts, organizations, agents, incidents, and reports.

已驗證STDIO僅桌面安全與監控商業與電商

概覽

AI 產生的概覽

讓 AI 助理以結構化方式存取 Huntress 網路安全平台資料的 MCP 伺服器,涵蓋帳戶、組織、代理程式、事件、帳務、訊號與使用者。

可以做什麼
  • 透過導覽工具瀏覽 Huntress 各領域,再依需求載入對應領域的工具
  • 讀取帳戶資訊與目前操作者,列出或查詢代理程式
  • 列出、查詢、建立、更新與刪除組織
  • 處理事件:事件報告、修復項目(核准或拒絕)與升級項目(解決)
  • 檢視帳務與彙總報告,列出或查詢安全訊號
  • 以完整的增刪改查管理使用者成員關係
適用情境
適合需要助理直接查詢或操作 Huntress 安全帳戶的情境,例如檢視事件、升級項目與訊號,核對帳務報告,或維護組織與成員關係,而不必切換到 Huntress 主控台。
執行需求
以本機 stdio 程序執行,或使用已發布映像檔以 HTTP 容器執行。stdio 或 env 驗證模式需要 HUNTRESS_API_KEY 與 HUNTRESS_API_SECRET 中的 Huntress API 憑證;Docker 映像檔預設為 gateway 模式,憑證透過請求標頭傳入,且必須設定 CONDUIT_S2S_SECRET。僅 npx 或原始碼方式需要 Node.js。
安裝前請注意
需要 Huntress API 金鑰與密鑰,可存取你的安全租戶資料。工具包含對組織與成員關係的建立、更新與刪除,以及對修復項目的核准或拒絕,助理操作會變更實際資料。HTTP 模式需使用高強度的 CONDUIT_S2S_SECRET,切勿提交至版本庫,並避免在本機測試之外使用不安全的開發開關。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 Huntress,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

Huntress MCP Server

[Build Status] [License] [Node.js]

A Model Context Protocol (MCP) server that provides AI assistants with structured access to Huntress cybersecurity platform data and operations.

Note: This project is maintained by Wyre Technology.

Quick Start

Claude Desktop — download, open, done:

  1. Download huntress-mcp.mcpb from the latest release
  2. Open the file (double-click or drag into Claude Desktop)
  3. Enter your Huntress credentials when prompted (API Key, API Secret)

No terminal, no JSON editing, no Node.js install required.

Claude Code (CLI):

bash
claude mcp add huntress-mcp \  -e HUNTRESS_API_KEY=your-api-key \  -e HUNTRESS_API_SECRET=your-api-secret \  -- npx -y github:WYRE-AI/huntress-mcp

See Installation for Docker and from-source methods.

Features

  • 🔌 MCP Protocol Compliance: Full support for MCP resources and tools
  • 🛡️ Comprehensive Security Coverage: Tools spanning agents, organizations, incidents, escalations, billing, signals, and users
  • 🔍 Decision-Tree Navigation: Start with huntress_navigate to explore domains, then dynamically load domain-specific tools
  • 📝 CRUD Operations: Create, read, update, delete operations for organizations, memberships, incidents, and more
  • 🔒 Secure Authentication: HTTP Basic Auth with Huntress API credentials
  • 🌐 Dual Transport: Supports both stdio (local) and HTTP Streamable (remote/Docker) transports
  • 📦 MCPB Packaging: One-click installation via MCP Bundle for desktop clients
  • 🐳 Docker Ready: Containerized deployment with HTTP transport and health checks
  • ⚡ Rate Limiting: Built-in rate limiter respects Huntress API limits (60 req/min)
  • 📊 Structured Logging: Comprehensive logging with configurable levels

Table of Contents

Installation

Option 1: MCPB Bundle (Claude Desktop)

The simplest method — no terminal, no JSON editing, no Node.js install required.

  1. Download huntress-mcp.mcpb from the latest release
  2. Open the file (double-click or drag into Claude Desktop)
  3. Enter your Huntress credentials when prompted (API Key, API Secret)

For Claude Code (CLI), one command:

bash
claude mcp add huntress-mcp \  -e HUNTRESS_API_KEY=your-api-key \  -e HUNTRESS_API_SECRET=your-api-secret \  -- npx -y github:WYRE-AI/huntress-mcp

Option 2: Docker

The image listens on 0.0.0.0 inside the container and defaults to AUTH_MODE=gateway. Publish the port on loopback and pass the service-to-service secret. In gateway mode, Huntress credentials arrive on each request as headers; they are not read from the environment.

bash
docker run -d \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -p 127.0.0.1:8080:8080 \  ghcr.io/wyre-ai/huntress-mcp:latest

Compose refuses to start when CONDUIT_S2S_SECRET is unset:

bash
CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up

Option 3: From Source

bash
git clone https://github.com/WYRE-AI/huntress-mcp.gitcd huntress-mcpnpm cinpm run build

Configuration

Copy .env.example and set the variables below.

VariableRequiredDescription
HUNTRESS_API_KEYFor stdio and AUTH_MODE=envHuntress API public key
HUNTRESS_API_SECRETFor stdio and AUTH_MODE=envHuntress API secret
MCP_TRANSPORTNostdio (default) or http
AUTH_MODENogateway (Docker image and Compose default) or env. Gateway mode requires X-Huntress-Api-Key and X-Huntress-Api-Secret on each /mcp request and never falls back to HUNTRESS_*. env uses those variables only after S2S auth succeeds.
CONDUIT_S2S_SECRETYes for HTTPService-to-service secret. The HTTP server logs an error and exits non-zero when this is empty or a known placeholder (changeme, secret, replace-me, your-s2s-secret, and the other example values). Compose will not start without it. Never commit a real value. Generate one with openssl rand -hex 32.
MCP_ALLOW_INSECURE_DEVNoSet to exactly 1 only for local development to start HTTP without CONDUIT_S2S_SECRET. The process logs a warning, does not enforce X-Gateway-S2S, and listens on 127.0.0.1 only. A non-loopback MCP_HTTP_HOST (including 0.0.0.0) is ignored and the override is logged. A known placeholder secret is still refused.
MCP_HTTP_HOSTNoBind address when CONDUIT_S2S_SECRET is set. Defaults to 127.0.0.1 when unset. The container image sets 0.0.0.0.
MCP_HTTP_PORTNoHTTP port. Defaults to 8080.
LOG_LEVELNoLog level (debug, info, warn, error). Defaults to info.

/health and /healthz stay unauthenticated and do not read credentials. The stdio transport does not use CONDUIT_S2S_SECRET.

HTTP authentication

With MCP_TRANSPORT=http and CONDUIT_S2S_SECRET set, every /mcp request must include X-Gateway-S2S:

t=<unix seconds>,v1=<hex hmac-sha256>

v1 is HMAC-SHA256 over the exact message t=<unix seconds>, keyed with CONDUIT_S2S_SECRET, hex-encoded. The timestamp must be within 300 seconds of the server clock. A missing or invalid header returns 401. The secret is never written to logs.

javascript
import { createHmac } from 'node:crypto';
const t = Math.floor(Date.now() / 1000);const v1 = createHmac('sha256', process.env.CONDUIT_S2S_SECRET).update(`t=${t}`).digest('hex');const xGatewayS2s = `t=${t},v1=${v1}`;

In AUTH_MODE=gateway, /mcp also requires X-Huntress-Api-Key and X-Huntress-Api-Secret. Those headers are the only credential source for that request. A request missing either header returns 401 and does not fall back to HUNTRESS_API_KEY / HUNTRESS_API_SECRET.

javascript
await fetch('http://127.0.0.1:8080/mcp', {  method: 'POST',  headers: {    'content-type': 'application/json',    accept: 'application/json, text/event-stream',    'x-gateway-s2s': xGatewayS2s,    'x-huntress-api-key': apiKey,    'x-huntress-api-secret': apiSecret,  },  body: JSON.stringify({ jsonrpc: '2.0', id: 1, method: 'tools/list' }),});

Domains

The server uses decision-tree navigation. Start with huntress_navigate to pick a domain:

DomainTools
accountsGet account info, get current actor
agentsList agents, get agent by ID
organizationsList, get, create, update, delete organizations
incidentsIncident reports (list/get/resolve), remediations (list/get/approve/reject), escalations (list/get/resolve)
billingBilling reports, summary reports
signalsList/get security signals
usersMembership CRUD (list/get/create/update/delete)

Docker Deployment

See docker-compose.yml for full configuration. The checked-in Compose service is gateway mode. It does not set HUNTRESS_API_KEY or HUNTRESS_API_SECRET and does not use env_file, so a project .env cannot inject static vendor credentials into the container. Compose still interpolates CONDUIT_S2S_SECRET from that file and will not start when it is unset. The port is published on 127.0.0.1.

bash
cp .env.example .env# Set CONDUIT_S2S_SECRET. Leave it empty in the example; never commit a real value.CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" docker compose up -d

Single-tenant HTTP (AUTH_MODE=env) still requires the S2S secret, then uses HUNTRESS_API_KEY and HUNTRESS_API_SECRET. It is separate from the gateway Compose service:

bash
docker run -d \  -e CONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" \  -e AUTH_MODE=env \  -e HUNTRESS_API_KEY=your-key \  -e HUNTRESS_API_SECRET=your-secret \  -p 127.0.0.1:8080:8080 \  ghcr.io/wyre-ai/huntress-mcp:latest

Local HTTP without a secret is development-only. It binds 127.0.0.1 only and logs a warning:

bash
MCP_TRANSPORT=http MCP_ALLOW_INSECURE_DEV=1 npm run start:http

Development

bash
npm cinpm run build       # Build the projectnpm run dev         # Watch modenpm run test        # Run testsnpm run lint        # Type-checknpm run clean       # Remove dist/
# HTTP refuses to start until CONDUIT_S2S_SECRET is setCONDUIT_S2S_SECRET="$CONDUIT_S2S_SECRET" npm run start:http
# Local HTTP only, without a service-to-service secret (always binds 127.0.0.1)MCP_ALLOW_INSECURE_DEV=1 npm run start:http

Testing

bash
npm test            # Run test suitenpm run test:watch  # Watch mode

Contributing

See CONTRIBUTING.md for guidelines.

License

Apache 2.0 — Copyright WYRE Technology

來源:README.md,提交 946adcf

工具

0
SourceWeft 曾在隔離沙箱中以無憑證方式啟動該軟體包一次,以列出其工具,但未能完成:該軟體包類型無法在沙箱中執行。

版本歷史

4
  1. v1.2.24最新Nov 4, 2026
  2. v1.2.23Oct 14, 2026
  3. v1.2.22Oct 8, 2026
  4. v1.2.21Sep 16, 2026

評分

已滿足適用檢查項的 40%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。