Threatlocker MCP Server

threatlocker-mcp PyPI v0.2.1

Published by space-c0wboy — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for the ThreatLocker Portal API

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 96/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 4 = 96. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 30

Each tool and what it can reach — statically extracted from the published source.

  • action_log_get_file_download_details_by_idingests untrusted input
  • approval_request_get_file_download_details_by_idingests untrusted input
  • action_log_get_by_id_v2no sensitive capability
  • application_get_by_idno sensitive capability
  • application_get_matching_listno sensitive capability
  • approval_request_get_by_idno sensitive capability
  • approval_request_get_countno sensitive capability
  • approval_request_get_permit_application_by_idno sensitive capability
  • approval_request_get_storage_approval_by_idno sensitive capability
  • approval_request_update_for_ignoreno sensitive capability
Show 20 more tools ↓
  • approval_request_update_for_rejectno sensitive capability
  • approval_request_update_for_take_ownershipno sensitive capability
  • computer_disable_protectionno sensitive capability
  • computer_enable_protectionno sensitive capability
  • computer_get_by_all_parametersno sensitive capability
  • computer_get_for_edit_by_idno sensitive capability
  • computer_group_get_dropdown_by_organization_idno sensitive capability
  • computer_move_to_other_organizationno sensitive capability
  • computer_update_baseline_rescanno sensitive capability
  • computer_update_for_editno sensitive capability
  • computer_update_maintenance_modeno sensitive capability
  • maintenance_mode_end_by_idno sensitive capability
  • maintenance_mode_get_by_computer_idno sensitive capability
  • maintenance_mode_insertno sensitive capability
  • online_devices_get_by_parametersno sensitive capability
  • policy_get_by_idno sensitive capability
  • system_audit_get_by_parametersno sensitive capability
  • system_audit_get_for_health_centerno sensitive capability
  • tag_get_by_idno sensitive capability
  • tag_get_dropdown_options_by_organization_idno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.2.1 latest A 96/100 0 1.13.0 2026-08-25

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/threatlocker-mcp/badge.svg)](https://mcptrustchecker.com/registry/threatlocker-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/threatlocker-mcp"><img src="https://mcptrustchecker.com/registry/threatlocker-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/threatlocker-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan threatlocker-mcp --online --registry pypi

Use the free API → How scoring works

More in Security & Testing