get_statsLABSCO SUMMARY
Task Manager shows you now; this answers about earlier.
The value is in the join: the server that knows a process pinned the GPU also knows whether that binary is signed, who signed it, when it first appeared on the machine, and whether you were even at the keyboard — so "the fan was roaring while I was away" becomes an answerable question.
What it is
A local, read-only bridge to the history the AppControl Windows app keeps: tracked binaries and their signatures, running processes, code-signing publishers, quarantine rules, security events, and time-series resource and temperature data.
What you get
- get_monitoring returns time-series resource metrics — CPU, memory, disk, GPU and temperatures — system-wide or per binary, with top-N and minimum-value filters for finding the heavy consumer
- list_binaries filters tracked binaries by signature status, running state, first-seen date, path substring or publisher; get_binary returns path, hash, signature, publisher and first-seen time for one or several at once
- query_history searches the security event log — first-seen binaries, quarantine blocks, alerts and process starts — by event type, time range or binary
- list_processes reports what is running now with binary ID, PID, path and start time; list_publishers reports the signing identities behind those binaries and how many are linked to each
- list_rules shows the quarantine rules in force: which binaries and publishers are blocked, the rule type, and when it was created
- get_stats reports service uptime and the on, off and idle intervals of the machine — what turns a bare timestamp into "while I was away"
- get_hardware reports the CPU, GPU and temperature sensors being monitored
- Every tool reads. The server cannot change a rule, block or unblock a binary, or alter the service configuration
Requirements
Windows, with the AppControl desktop app installed, running, and its MCP API enabled. Install it as an MCPB package into Claude Desktop, through the Claude Code plugin marketplace, or as a standalone executable your client launches.
Setup effort
Follow the published steps
USE CASES
Explaining a slowdown that has already ended
Pull per-binary resource history across the window, rank by the metric that spiked, then look up the top consumer's signature and publisher.
Auditing what turned up on the machine recently
List binaries first seen after a date, filter to the unsigned ones, and check whether any are running from a temp or downloads path.
Reviewing what got blocked and why
Query the quarantine and alert events over the last day, then read the rules that produced them.
Working out what ran while nobody was there
Read the machine's on, off and idle intervals, then line the security events and resource history up against them.
Checking whether a heat problem is software
Read which temperature sensors are being monitored, then put the temperature series next to per-binary CPU and GPU use over the same period.
9 tools
Listed in project docs. Your client may show a different list.
list_binariesget_binarylist_processeslist_publisherslist_rulesquery_historyget_monitoringget_hardwareBEFORE YOU INSTALL
What to know first
Tools you get
9 tools named in the project's documentation.
Requires
- Windows
- AppControl (https://www.appcontrol.com) running with its MCP API enabled
INSTALLATION
Connect your client
Server setup
Download appcontrol-mcp.exe from the latest release at https://github.com/AppControlLabs/appcontrol-mcp-go/releases/latest (the Claude Code plugin downloads it for you)
Place it somewhere permanent, e.g. C:\MCP\appcontrol-mcp.exe, then configure your client as shown below
MCP Clients
Claude Code — plugin
In Claude Code, add the marketplace: /plugin marketplace add appcontrollabs/appcontrol-mcp-go
Install the plugin: /plugin install appcontrol-mcp@appcontrollabs
Reload plugins: /reload-plugins
Claude Code
claude mcp add appcontrol C:\MCP\appcontrol-mcp.exeCodex
codex mcp add appcontrol C:\MCP\appcontrol-mcp.exeGemini CLI
{
"mcpServers": {
"appcontrol": {
"command": "C:/MCP/appcontrol-mcp.exe",
"args": [],
"timeout": 15000
}
}
}Cursor, Windsurf
{
"mcpServers": {
"appcontrol": {
"command": "C:/MCP/appcontrol-mcp.exe"
}
}
}VS Code — GitHub Copilot
{
"servers": {
"appcontrol": {
"command": "C:/MCP/appcontrol-mcp.exe"
}
}
}