# ThreatLocker (oci · ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6)

MCP server for ThreatLocker — zero-trust endpoint protection, allowlisting, and policies.

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

## Components

- oci · `ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6`: 36/100 (this document), [markdown](https://verifymcp.io/servers/wyre-technology-threatlocker-mcp/ghcr-io-wyre-technology-threatlocker-mcp-v1-3-6.md), [page](https://verifymcp.io/servers/wyre-technology-threatlocker-mcp/ghcr-io-wyre-technology-threatlocker-mcp-v1-3-6)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6`
- 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).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 842 tokens (~49/item across 17 items; 17 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**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 ThreatLocker MCP server?

ThreatLocker runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6. 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-threatlocker-mcp -- docker run --rm -i ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### Hermes

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

### Netclaw

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

### Other

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

## 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-20 (score 36)

First indexed and scored.

## MCP tools (17)

### `threatlocker_navigate` (~148 tokens)

Discover available ThreatLocker 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: - computers: Computer management - list/get computers, get check-ins, and device information - computer_groups: Computer group management - list computer groups and dropdown op…

### `threatlocker_status` (~16 tokens)

Show credentials status and available domains

### `threatlocker_computers_list` (~81 tokens)

List ThreatLocker computers with optional filters.

Input parameters:

- `childOrganizations` (boolean): Include child organizations
- `computerGroup` (string): Computer group filter
- `pageNumber` (number): Page number (default 1)
- `pageSize` (number): Page size (default 50)
- `searchText` (string): Search text filter

### `threatlocker_computers_get` (~29 tokens)

Get a single computer by ID.

Input parameters:

- `computerId` (string, required): Computer ID

### `threatlocker_computers_get_checkins` (~60 tokens)

Get checkin history for a computer.

Input parameters:

- `computerId` (string, required): Computer ID
- `pageNumber` (number): Page number (default 1)
- `pageSize` (number): Page size (default 50)

### `threatlocker_computer_groups_list` (~58 tokens)

List computer groups with optional filters.

Input parameters:

- `includeAllComputers` (boolean): Include "All Computers" group
- `includeGlobal` (boolean): Include global groups
- `osType` (string): Operating system type filter

### `threatlocker_computer_groups_dropdown` (~19 tokens)

Get computer groups in dropdown format.

### `threatlocker_approvals_list` (~79 tokens)

List approval requests with optional filters.

Input parameters:

- `childOrganizations` (boolean): Include child organizations
- `pageNumber` (number): Page number (default 1)
- `pageSize` (number): Page size (default 50)
- `searchText` (string): Search text filter
- `status` (string): Approval status filter

### `threatlocker_approvals_get` (~32 tokens)

Get a single approval request by ID.

Input parameters:

- `approvalRequestId` (string, required): Approval request ID

### `threatlocker_approvals_pending_count` (~20 tokens)

Get count of pending approval requests.

### `threatlocker_approvals_get_permit_application` (~36 tokens)

Get permit application details for an approval request.

Input parameters:

- `approvalRequestId` (string, required): Approval request ID

### `threatlocker_audit_search` (~101 tokens)

Search audit log entries with optional filters.

Input parameters:

- `childOrganizations` (boolean): Include child organizations
- `endDate` (string): End date filter (ISO 8601)
- `pageNumber` (number): Page number (default 1)
- `pageSize` (number): Page size (default 50)
- `searchText` (string): Search text filter
- `startDate` (string): Start date filter (ISO 8601)

### `threatlocker_audit_get` (~32 tokens)

Get a single audit log entry by ID.

Input parameters:

- `actionLogId` (string, required): Action log ID

### `threatlocker_audit_file_history` (~32 tokens)

Get audit history for a specific file path.

Input parameters:

- `fullPath` (string, required): Full file path

### `threatlocker_organizations_list_children` (~58 tokens)

List child organizations with optional filters.

Input parameters:

- `pageNumber` (number): Page number (default 1)
- `pageSize` (number): Page size (default 50)
- `searchText` (string): Search text filter

### `threatlocker_organizations_get_auth_key` (~19 tokens)

Get the organization auth key.

### `threatlocker_organizations_for_move_computers` (~22 tokens)

Get organizations available for moving computers.

## Diagnostics

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

## Score history

- 2026-08-22: 36
- 2026-08-21: 36
- 2026-08-20: 36

## Common questions

### What is the ThreatLocker MCP server?

ThreatLocker is an MCP server listed in the public MCP registry as io.github.wyre-technology/threatlocker-mcp. MCP server for ThreatLocker, zero-trust endpoint protection, allowlisting, and policies. This page covers its container image (ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6).

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

ThreatLocker scores 36 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 ThreatLocker MCP server expose?

ThreatLocker exposes 17 tools: threatlocker_navigate, threatlocker_status, threatlocker_computers_list, threatlocker_computers_get, threatlocker_computers_get_checkins, and 12 more. Their descriptions and schemas cost roughly 842 tokens of context every time the server is loaded.

### Is the ThreatLocker MCP server still maintained?

ThreatLocker 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 ThreatLocker MCP server under?

ThreatLocker 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/threatlocker-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-technology-threatlocker-mcp/ghcr-io-wyre-technology-threatlocker-mcp-v1-3-6.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-technology-threatlocker-mcp/ghcr-io-wyre-technology-threatlocker-mcp-v1-3-6.json
- HTML version of this page: https://verifymcp.io/servers/wyre-technology-threatlocker-mcp/ghcr-io-wyre-technology-threatlocker-mcp-v1-3-6