TacticalRMM
PYPI · TRMM-MCP · SCANNED AUG 23
Read your TacticalRMM fleet; run commands only after per-command human approval.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- Known CVEs were checked across the 37 of 39 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- Runs setuptools.build_meta at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 37 of 39 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency35
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 3 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
- Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Capabilities0
- Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified
Unverified: 4 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the TacticalRMM MCP server?
TacticalRMM runs locally as a PyPI package, launched with uvx trmm-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · trmm-mcp
claude mcp add shin2344234-trmm-mcp -- uvx trmm-mcp
{
"mcpServers": {
"shin2344234-trmm-mcp": {
"command": "uvx",
"args": [
"trmm-mcp"
]
}
}
} {
"servers": {
"shin2344234-trmm-mcp": {
"command": "uvx",
"args": [
"trmm-mcp"
]
}
}
} codex mcp add shin2344234-trmm-mcp -- uvx trmm-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shin2344234-trmm-mcp": {
"type": "local",
"command": [
"uvx",
"trmm-mcp"
],
"enabled": true
}
}
} openclaw mcp add shin2344234-trmm-mcp --command uvx --arg trmm-mcp
mcp_servers:
shin2344234-trmm-mcp:
command: "uvx"
args: ["trmm-mcp"] {
"McpServers": {
"shin2344234-trmm-mcp": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"trmm-mcp"
]
}
}
} assistant mcp add shin2344234-trmm-mcp -t stdio -c uvx -a trmm-mcp
{
"mcpServers": {
"shin2344234-trmm-mcp": {
"command": "uvx",
"args": [
"trmm-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Aug 26 0
- Stability: Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare. security
- Security disclosure: fail → pass ▲ functional
- Schema quality: Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess. functional
- Capabilities: Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake. functional
- Tool coverage: Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess. functional
- 20 Aug 26 0
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Capabilities: Protocol version not yet verified: we do not have a sandbox capture of the MCP handshake this version of the package performs yet. functional
- Tool coverage: Tool coverage not yet verified: we do not have a sandbox capture of the tool definitions this version of the package serves yet. functional
- Schema quality: Schema quality not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. functional
- Package version: 1.0.1 → 1.1.0 functional
- 14 Aug 26 0
- Package version: 1.0.0 → 1.0.1 functional
- 13 Aug 26 36
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 23 Aug 2026 · Analysed pypi/trmm-mcp@1.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Dependencies 37 packages
| Packages resolved | 37 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the TacticalRMM MCP server?
TacticalRMM is an MCP server listed in the public MCP registry as io.github.shin2344234/trmm-mcp. Read your TacticalRMM fleet; run commands only after per-command human approval. This page covers its PyPI package (trmm-mcp).
Is the TacticalRMM MCP server safe to use?
TacticalRMM scores 36 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Is the TacticalRMM MCP server still maintained?
TacticalRMM is still listed as active in the MCP registry. We last reached this channel on 23 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.