ThreatLocker MCP

io.github.Servosity/threatlocker-mcp

About ThreatLocker MCP

ThreatLocker MCP is an MCP server published by the GitHub account Servosity. Every ThreatLocker Portal API feature, plus the write operations the read-only tools lack and a

It runs on your own machine: your AI client starts it from the MCP bundle package threatlocker-mcp.mcpb at version 0.3.13.

It asks for 3 secrets: PRINTING_PRESS_CLIENT_PROFILE, THREATLOCKER_API_KEY and THREATLOCKER_MCP_HTTP_TOKEN. Give it a key with the least access that still works.

Version 0.3.13 was published on 27 October 2026, and the source code is public, so you can read it before installing.

Written from the registry entry. 7 automated checks on registry metadata: 4 pass, 1 warn, 0 fail, 2 info. How we check.

What it asks for

VariableRequiredSecretDescription
PRINTING_PRESS_CLIENT_PROFILEYesYesSet the PRINTING_PRESS_CLIENT_PROFILE credential for the ThreatLocker MCP server.
THREATLOCKER_API_KEYYesYesPortal API key (ThreatLocker portal: Settings > API Keys), sent as the Authorization header on every call.
THREATLOCKER_BASE_URLNoNoBase URL for the ThreatLocker API. Leave the prefilled default unless your account uses a different regional or self-hosted host.
THREATLOCKER_ORG_IDNoNoTenant GUID sent as ManagedOrganizationId (the --org flag overrides it). Most Portal API data calls answer 401/403 without it, so set it unless you pass --org on every call.
THREATLOCKER_USER_AGENTNoNoOverrides the User-Agent the CLI sends on ThreatLocker requests. Leave blank to use the CLI's own built-in User-Agent.
THREATLOCKER_MCP_READ_ONLYNoNoOptional. Set to exactly 1 to expose only read-only tools and refuse any state-changing execute call.
THREATLOCKER_NO_LOCAL_DATANoNoOptional. Set to 1 to save no API data locally: sync and audit pull are refused, the response cache is off, and reads go to the API.
THREATLOCKER_MCP_HTTP_TOKENNoYesRequired only when running the MCP server with --transport http. Not needed for the default local stdio transport.

Checks

CheckResultDetail
Source repository linkedPasshttps://github.com/servosity/msp-skills
Version pinnedPassEvery package has an explicit version
Secrets requestedWarnAsks for 3 secrets: PRINTING_PRESS_CLIENT_PROFILE, THREATLOCKER_API_KEY, THREATLOCKER_MCP_HTTP_TOKEN
Known package registryPassAll packages come from npm, PyPI, OCI, NuGet or MCPB
Namespace ownershipInfoName verified via GitHub account Servosity
Registry text aimed at the AIPassDescription and settings contain no hidden characters or instructions to the AI
Code red flagsInfoPackage could not be read (too large)

Popularity & health: 63 / 100

Worked out from public numbers and our own checks, not from user reviews or ratings. It says how used and how looked-after a server is, not whether it is safe.

Popularity9 / 40

67 GitHub stars, no download count, 0 Hacker News posts (0 points). Best two of the three, each on a log scale.

Activity25 / 25

Last push 2026-10-28, last release 2026-10-27, 1,049 commits in 90 days.

Issue health13 / 15

83 closed of 94 issues.

Our checks16 / 20

1 warning, each costing a fifth.

14 forks, 379 merged pull requests. Sources: GitHub, npm, PyPI (pypistats.org) and Hacker News (Algolia), fetched 2026-10-31.

What people say

No Hacker News threads link to its source code.

Look further: search Reddit, search Hacker News, read its GitHub issues. These are not reviews we checked.

Facts

Registry nameio.github.Servosity/threatlocker-mcp
PublisherGitHub account Servosity
How the name is verifiedName verified via GitHub account Servosity. The registry ties the name prefix to that account or domain; it does not check the code.
TypeLocal: runs on your machine from a package
Packagesmcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.13/threatlocker-mcp.mcpb 0.3.13 (stdio)
Version0.3.13
Published
Last updated
Source repositoryhttps://github.com/servosity/msp-skills
WebsiteNone linked
CategorySearch & web (assigned by keyword rule, not by hand)

Related servers in Search & web