Skip to content
mcp/harbor

ThreatLocker MCP changelog

io.github.servosity/threatlocker-mcp

12 changes recorded. MCP Harbor re-reads this listing from the official registry every six hours and asks the live server what it exposes, and keeps what changed between one look and the next.

  • server.json 2 fields changed
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.15/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.16/threatlocker-mcp.mcpb
    version
    0.3.15 0.3.16

  • server.json 2 fields changed
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.14/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.15/threatlocker-mcp.mcpb
    version
    0.3.14 0.3.15

  • server.json 2 fields changed
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.13/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.14/threatlocker-mcp.mcpb
    version
    0.3.13 0.3.14

  • AGENTS.md +24 −2

    https://raw.githubusercontent.com/servosity/msp-skills/HEAD/AGENTS.md 

    − 2. **After** generating, prove nothing regressed:−   `tools/maintainer/verify_all.sh <slug>` before pushing. See `CONTRIBUTING.md`.+ 2. **After** generating, retire or re-apply the fleet-wide hand-fixes (onboard.py+    does this for you), then prove nothing regressed:+    python3 tools/maintainer/replay_handfixes.py --slug <slug>+    `tools/maintainer/fleet_handfixes.json` records, per fleet-wide id, whether the+    press now generates it (retired: its entry is not demanded from `retire_at` on,+    the press's own shape is) or the replay tool re-applies it. Reconcile by hand+    only what the replay names.+ A badge also records the code it verified: `verify_live.py` stores the release+ version and the cli hash of that tag, and the catalog says "verified on vX.Y.Z"+ once the shipped release carries different code. When a report names the+ version it ran, pass `--verified-version`; for an existing badge use `--bind`.+ Never copy `cli_hash_at_release` into a badge by hand: `check_registry_state.py`+ recomputes the hash from the tag and fails a binding that is not that code.+ **Beta and live-verified are mutually exclusive.** A live-verified connector+ never says Beta. Flip and revoke only through `verify_live.py`, which moves the+ registry `status` and the README / pain-point Status paragraphs with the badge+ (the docs page follows from `render_docs_page.py`). `verify_live.py --check`+ runs in CI and fails on any disagreement; `--sync` repairs the registry and the+ Status paragraphs, and a stray "Beta" elsewhere in those two files is fixed by+ hand.+   `bash tools/maintainer/verify_all.sh --changed` (or `--slug <slug>`) while+   iterating, and the full `bash tools/maintainer/verify_all.sh` once on the final+   commit after the last rebase. Its verdict (`.verify/verdict.json`) names the+   head and base SHAs it checked. See `CONTRIBUTING.md`.

  • server.json 3 fields changed
    env_vars
    PRINTING_PRESS_CLIENT_PROFILE, THREATLOCKER_API_KEY, THREATLOCKER_BASE_URL, THREATLOCKER_ORG_ID, THREATLOCKER_USER_AGENT PRINTING_PRESS_CLIENT_PROFILE, THREATLOCKER_API_KEY, THREATLOCKER_BASE_URL, THREATLOCKER_ORG_ID, THREATLOCKER_USER_AGENT, THREATLOCKER_MCP_READ_ONLY, THREATLOCKER_NO_LOCAL_DATA, THREATLOCKER_MCP_HTTP_TOKEN
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.12/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.13/threatlocker-mcp.mcpb
    version
    0.3.12 0.3.13

  • server.json 2 fields changed
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.11/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.12/threatlocker-mcp.mcpb
    version
    0.3.11 0.3.12
  • server.json 2 fields changed
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.10/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.11/threatlocker-mcp.mcpb
    version
    0.3.10 0.3.11

  • AGENTS.md +3 −2

    https://raw.githubusercontent.com/servosity/msp-skills/HEAD/AGENTS.md 

    −    mentions the flag, and it cannot see the other four requirements (one sealing−    before the seal, the `.mcpb` inside the sealing contract). Then: one tag per+    mentions the flag, and it cannot see the other five requirements (one sealing+    before the seal, the `.mcpb` inside the sealing contract, and the Windows+    binaries run on a Windows runner before the seal). Then: one tag per
  • server.json 2 fields changed
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.9/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.10/threatlocker-mcp.mcpb
    version
    0.3.9 0.3.10

  • server.json 2 fields changed
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.8/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.9/threatlocker-mcp.mcpb
    version
    0.3.8 0.3.9

  • server.json 2 fields changed
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.7/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.8/threatlocker-mcp.mcpb
    version
    0.3.7 0.3.8

  • server.json 2 fields changed
    package_identifier
    https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.6/threatlocker-mcp.mcpb https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.7/threatlocker-mcp.mcpb
    version
    0.3.6 0.3.7
ThreatLocker MCP MCP server