# Huntress (oci · ghcr.io/wyre-technology/huntress-mcp:v1.2.19)

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

- Trust score: 37/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-22

## Components

- oci · `ghcr.io/wyre-technology/huntress-mcp:v1.2.19`: 37/100 (this document), [markdown](https://verifymcp.io/servers/wyre-technology-huntress-mcp/ghcr-io-wyre-technology-huntress-mcp-v1-2-19.md), [page](https://verifymcp.io/servers/wyre-technology-huntress-mcp/ghcr-io-wyre-technology-huntress-mcp-v1-2-19)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-technology/huntress-mcp:v1.2.19`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-22.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 1 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 83/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1644 tokens (~51/item across 32 items; 32 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 2 categories.** Categories scored 0 because we could not verify them: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the Huntress MCP server?

Huntress runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-technology/huntress-mcp:v1.2.19. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-technology-huntress-mcp -- docker run --rm -i ghcr.io/wyre-technology/huntress-mcp:v1.2.19
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-technology-huntress-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/huntress-mcp:v1.2.19"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-technology-huntress-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/huntress-mcp:v1.2.19"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-technology-huntress-mcp -- docker run --rm -i ghcr.io/wyre-technology/huntress-mcp:v1.2.19
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-technology-huntress-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/huntress-mcp:v1.2.19"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-technology-huntress-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-technology/huntress-mcp:v1.2.19"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-technology-huntress-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/huntress-mcp:v1.2.19"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-technology-huntress-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-technology/huntress-mcp:v1.2.19"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-22 (score 37, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-08-20 (score 37)

First indexed and scored.

## MCP tools (32)

### `huntress_navigate` (~118 tokens)

Discover available Huntress tools by domain. Returns tool names and descriptions for the selected domain. All tools are callable at any time — this is a help/discovery aid, not a prerequisite.

Input parameters:

- `domain` (string, required): The domain to explore: - accounts: account info, current actor - agents: list/get endpoint agents - organizations: CRUD organizations - incidents: incident reports, escalations, remediations - billin…

### `huntress_status` (~19 tokens)

Check Huntress API connection status and available domains.

### `huntress_accounts_get` (~22 tokens)

Get the Huntress account associated with the current API credentials.

### `huntress_accounts_actor` (~25 tokens)

Get the current actor (user/account/reseller) for the API credentials.

### `huntress_agents_list` (~67 tokens)

List Huntress agents with optional filters.

Input parameters:

- `limit` (number): Max results (1-500, default 10)
- `organization_id` (number): Filter by organization ID
- `page_token` (string): Pagination token
- `platform` (string): Filter by platform

### `huntress_agents_get` (~26 tokens)

Get a single agent by ID.

Input parameters:

- `id` (number, required): Agent ID

### `huntress_organizations_list` (~37 tokens)

List organizations.

Input parameters:

- `limit` (number): Max results (1-500)
- `page_token` (string): Pagination token

### `huntress_organizations_get` (~25 tokens)

Get organization by ID.

Input parameters:

- `id` (number, required): Organization ID

### `huntress_organizations_create` (~95 tokens)

⚠ HIGH-IMPACT. Creates a new organization in Huntress, which provisions tenant scope for agents, users, and security policies. Reversible via delete, but creation is visible to operators and may trigger downstream automations. Confirm with the user before invoking.

Input parameters:

- `key` (string, required): Organization key for agent grouping (max 256 chars)
- `name` (string, required): Organization name (max 256 chars)

### `huntress_organizations_update` (~100 tokens)

⚠ HIGH-IMPACT. Updates an organization's name, key, or report recipients. Changing the key affects agent grouping; changing report recipients alters who receives security reports. Reversible by reverting the fields. Confirm with the user before invoking.

Input parameters:

- `id` (number, required): Organization ID
- `key` (string): New key
- `name` (string): New name
- `report_recipients` (array): Email recipients for reports

### `huntress_organizations_delete` (~62 tokens)

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes an organization and all of its associated data, agents, and security settings. This action cannot be undone. Confirm with the user before invoking.

Input parameters:

- `id` (number, required): Organization ID

### `huntress_incidents_list` (~95 tokens)

List incident reports with optional filters.

Input parameters:

- `agent_id` (number): Filter by agent ID
- `limit` (number): Max results (1-500)
- `organization_id` (number): Filter by org ID
- `page_token` (string): Pagination token
- `platform` (string): Filter by platform
- `severity` (string): Filter by severity
- `status` (string): Filter by status

### `huntress_incidents_get` (~27 tokens)

Get incident report by ID.

Input parameters:

- `id` (number, required): Incident report ID

### `huntress_incidents_resolve` (~27 tokens)

Resolve an incident report.

Input parameters:

- `id` (number, required): Incident report ID

### `huntress_incidents_remediations` (~49 tokens)

List remediations for an incident report.

Input parameters:

- `incident_report_id` (number, required): Incident report ID
- `limit` (number)
- `page_token` (string)

### `huntress_incidents_remediation_get` (~41 tokens)

Get a specific remediation.

Input parameters:

- `incident_report_id` (number, required): Incident report ID
- `remediation_id` (number, required): Remediation ID

### `huntress_incidents_bulk_approve` (~36 tokens)

Bulk approve all remediations for an incident report.

Input parameters:

- `incident_report_id` (number, required): Incident report ID

### `huntress_incidents_bulk_reject` (~88 tokens)

Bulk reject all remediations for an incident report.

Input parameters:

- `comment` (string, required): Reason for rejection
- `email` (string): Contact email
- `incident_report_id` (number, required): Incident report ID
- `name` (string): Name of rejecting user
- `phone_number` (string): Contact phone
- `useful` (boolean): Whether the plan was useful

### `huntress_escalations_list` (~31 tokens)

List escalations.

Input parameters:

- `limit` (number)
- `page_token` (string)

### `huntress_escalations_get` (~31 tokens)

Get escalation by ID (includes entities).

Input parameters:

- `id` (number, required): Escalation ID

### `huntress_escalations_resolve` (~49 tokens)

Resolve an escalation.

Input parameters:

- `determination` (string): For unwanted access escalations
- `id` (number, required): Escalation ID
- `scope` (string): Rule scope

### `huntress_billing_reports_list` (~38 tokens)

List billing reports.

Input parameters:

- `limit` (number)
- `page_token` (string)
- `status` (string)

### `huntress_billing_reports_get` (~28 tokens)

Get billing report by ID.

Input parameters:

- `id` (number, required): Billing report ID

### `huntress_summary_reports_list` (~67 tokens)

List summary reports.

Input parameters:

- `limit` (number)
- `organization_id` (number)
- `page_token` (string)
- `period_max` (string): Max period filter
- `period_min` (string): Min period filter
- `type` (string)

### `huntress_summary_reports_get` (~27 tokens)

Get summary report by ID.

Input parameters:

- `id` (number, required): Summary report ID

### `huntress_signals_list` (~86 tokens)

List security signals.

Input parameters:

- `entity_id` (string)
- `entity_type` (string)
- `investigated_at_max` (string)
- `investigated_at_min` (string)
- `limit` (number)
- `organization_id` (number)
- `page_token` (string)
- `statuses` (string)
- `types` (string)

### `huntress_signals_get` (~25 tokens)

Get signal by ID.

Input parameters:

- `id` (number, required): Signal ID

### `huntress_users_list` (~42 tokens)

List memberships (users).

Input parameters:

- `limit` (number)
- `organization_id` (number): Filter by organization ID
- `page_token` (string)

### `huntress_users_get` (~24 tokens)

Get membership by ID.

Input parameters:

- `id` (number, required): Membership ID

### `huntress_users_create` (~108 tokens)

⚠ HIGH-IMPACT. Creates a membership (invites a user) and grants them the specified permission level — including potentially Admin or Security Engineer privileges. Reversible by deleting the membership. Confirm with the user before invoking.

Input parameters:

- `email` (string, required): User email
- `first_name` (string, required): First name
- `last_name` (string, required): Last name
- `organization_id` (number): Invite to org instead of account
- `permissions` (string, required): Permission level

### `huntress_users_update` (~72 tokens)

⚠ HIGH-IMPACT. Updates a membership's permission level, which can grant or revoke Admin, Security Engineer, or other privileged roles. Reversible by setting permissions back. Confirm with the user before invoking.

Input parameters:

- `id` (number, required): Membership ID
- `permissions` (string, required): New permission level

### `huntress_users_delete` (~57 tokens)

⚠ DESTRUCTIVE — IRREVERSIBLE. Permanently deletes a user membership and removes their access to the organization. This action cannot be undone. Confirm with the user before invoking.

Input parameters:

- `id` (number, required): Membership ID

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-technology-huntress-mcp/ghcr-io-wyre-technology-huntress-mcp-v1-2-19#diagnostics

## Score history

- 2026-08-22: 37
- 2026-08-21: 37
- 2026-08-20: 37

## Common questions

### What is the Huntress MCP server?

Huntress is an MCP server listed in the public MCP registry as io.github.wyre-technology/huntress-mcp. MCP server for Huntress, accounts, organizations, agents, incidents, and reports. This page covers its container image (ghcr.io/wyre-technology/huntress-mcp:v1.2.19).

### Is the Huntress MCP server safe to use?

Huntress scores 37 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Huntress MCP server expose?

Huntress exposes 32 tools: huntress_navigate, huntress_status, huntress_accounts_get, huntress_accounts_actor, huntress_agents_list, and 27 more. Their descriptions and schemas cost roughly 1,644 tokens of context every time the server is loaded.

### Is the Huntress MCP server still maintained?

Huntress is still listed as active in the MCP registry. We last reached this channel on 22 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Huntress MCP server under?

Huntress declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- Repository: https://github.com/wyre-technology/huntress-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-technology-huntress-mcp/ghcr-io-wyre-technology-huntress-mcp-v1-2-19.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-technology-huntress-mcp/ghcr-io-wyre-technology-huntress-mcp-v1-2-19.json
- HTML version of this page: https://verifymcp.io/servers/wyre-technology-huntress-mcp/ghcr-io-wyre-technology-huntress-mcp-v1-2-19