# io.github.wyre-technology/threatlocker-mcp

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.3.6
- **Author:** io.github.wyre-technology
- **License:** Unknown
- **Source:** https://github.com/wyre-technology/threatlocker-mcp

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 113 days — stale; the grade is a claim about the present made from dated evidence

## Security scan

- **Status:** clean
- **Scanned:** 2026-06-14T11:35:20.561Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

17 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `threatlocker_approvals_list`
- `threatlocker_approvals_get`
- `threatlocker_approvals_pending_count`
- `threatlocker_approvals_get_permit_application`
- `threatlocker_audit_search`
- `threatlocker_audit_get`
- `threatlocker_audit_file_history`
- `threatlocker_computer_groups_list`
- `threatlocker_computer_groups_dropdown`
- `threatlocker_computers_list`
- `threatlocker_computers_get`
- `threatlocker_computers_get_checkins`
- `threatlocker_navigate`
- `threatlocker_status`
- `threatlocker_organizations_list_children`
- `threatlocker_organizations_get_auth_key`
- `threatlocker_organizations_for_move_computers`

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Extensive blast radius — mutates data; holds an api key.
- Floor 37, ceiling 49 (tier: extensive)
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.wyre-technology%2Fthreatlocker-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.wyre-technology%2Fthreatlocker-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.wyre-technology%2Fthreatlocker-mcp
- HTML page: https://forgeregistry.com/registry/io.github.wyre-technology%2Fthreatlocker-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.