ThreatLocker
OCI · GHCR.IO/WYRE-TECHNOLOGY/THREATLOCKER-MCP:V1.3.6
MCP server for ThreatLocker — zero-trust endpoint protection, allowlisting, and policies.
Available components
Last scanned (2 hours ago)
Scores higher than 66% of OCI servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency6
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 57 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 842 tokens (~49/item across 17 items; 17 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 17 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: 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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Oct 26 −2
No change was recorded against any check on this day. Stability & Change Management went from 97 to 80.
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 77 to 97. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 −4
- Stability: pass → 0.77 functional
- 3 Oct 26 +1
- Stability: 0.97 → pass security
- 1 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed oci/ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
threatlocker_approvals_get ~32
Get a single approval request by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| approvalRequestId | string | yes | Approval request ID |
No output schema declared.
No examples provided.
threatlocker_approvals_get_permit_application ~36
Get permit application details for an approval request.
| Name | Type | Req | Description |
|---|---|---|---|
| approvalRequestId | string | yes | Approval request ID |
No output schema declared.
No examples provided.
threatlocker_approvals_list ~79
List approval requests with optional filters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
threatlocker_approvals_pending_count ~20
Get count of pending approval requests.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
threatlocker_audit_file_history ~32
Get audit history for a specific file path.
| Name | Type | Req | Description |
|---|---|---|---|
| fullPath | string | yes | Full file path |
No output schema declared.
No examples provided.
threatlocker_audit_get ~32
Get a single audit log entry by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| actionLogId | string | yes | Action log ID |
No output schema declared.
No examples provided.
threatlocker_audit_search ~101
Search audit log entries with optional filters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
threatlocker_computer_groups_dropdown ~19
Get computer groups in dropdown format.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
threatlocker_computer_groups_list ~58
List computer groups with optional filters.
| Name | Type | Req | Description |
|---|---|---|---|
| includeAllComputers | boolean | – | Include "All Computers" group |
| includeGlobal | boolean | – | Include global groups |
| osType | string | – | Operating system type filter |
No output schema declared.
No examples provided.
threatlocker_computers_get ~29
Get a single computer by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| computerId | string | yes | Computer ID |
No output schema declared.
No examples provided.
threatlocker_computers_get_checkins ~60
Get checkin history for a computer.
| Name | Type | Req | Description |
|---|---|---|---|
| computerId | string | yes | Computer ID |
| pageNumber | number | – | Page number (default 1) |
| pageSize | number | – | Page size (default 50) |
No output schema declared.
No examples provided.
threatlocker_computers_list ~81
List ThreatLocker computers with optional filters.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
threatlocker_navigate ~148
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | 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… |
No output schema declared.
No examples provided.
threatlocker_organizations_for_move_computers ~22
Get organizations available for moving computers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
threatlocker_organizations_get_auth_key ~19
Get the organization auth key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
threatlocker_organizations_list_children ~58
List child organizations with optional filters.
| Name | Type | Req | Description |
|---|---|---|---|
| pageNumber | number | – | Page number (default 1) |
| pageSize | number | – | Page size (default 50) |
| searchText | string | – | Search text filter |
No output schema declared.
No examples provided.
threatlocker_status ~16
Show credentials status and available domains
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the ThreatLocker MCP server?
ThreatLocker runs locally as a container image, launched with docker run --rm -i -e THREATLOCKER_API_KEY -e THREATLOCKER_ORGANIZATION_ID -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL 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.
oci · ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6
claude mcp add wyre-technology-threatlocker-mcp -- docker run --rm -i -e THREATLOCKER_API_KEY -e THREATLOCKER_ORGANIZATION_ID -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/threatlocker-mcp:v1.3.6
This image reads THREATLOCKER_API_KEY, THREATLOCKER_ORGANIZATION_ID, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.
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 46 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 17 October 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.