CMDOP Machine Care
OCI · GHCR.IO/COMMANDOPERATOR/CMDOP-CARE:V0.1.2 · SCANNED SEP 20
Read-only health and storage diagnostics for an enrolled CMDOP machine fleet.
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 → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
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 63 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 446 tokens (~111/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the CMDOP Machine Care MCP server?
CMDOP Machine Care runs locally as a container image, launched with docker run --rm -i ghcr.io/commandoperator/cmdop-care:v0.1.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/commandoperator/cmdop-care:v0.1.2
claude mcp add commandoperator-cmdop-care -- docker run --rm -i ghcr.io/commandoperator/cmdop-care:v0.1.2
{
"mcpServers": {
"commandoperator-cmdop-care": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/commandoperator/cmdop-care:v0.1.2"
]
}
}
} {
"servers": {
"commandoperator-cmdop-care": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/commandoperator/cmdop-care:v0.1.2"
]
}
}
} codex mcp add commandoperator-cmdop-care -- docker run --rm -i ghcr.io/commandoperator/cmdop-care:v0.1.2
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"commandoperator-cmdop-care": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/commandoperator/cmdop-care:v0.1.2"
],
"enabled": true
}
}
} mcp_servers:
commandoperator-cmdop-care:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/commandoperator/cmdop-care:v0.1.2"] {
"McpServers": {
"commandoperator-cmdop-care": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/commandoperator/cmdop-care:v0.1.2"
]
}
}
} {
"mcpServers": {
"commandoperator-cmdop-care": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/commandoperator/cmdop-care:v0.1.2"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 −2
- Stability: pass → 0.83 functional
- 9 Sept 26 0
- Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed oci/ghcr.io/commandoperator/cmdop-care:v0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
care_diagnose ~166
Run one bounded, typed process/startup diagnostic on a live enrolled machine. Use this to explain why a machine is slow. It never executes shell, accepts no PID or command argument, and performs no mutation. DISCLOSURE 1: if this machine requires a connection PIN, it is forwarded automatically from this host's local OS-keyring PIN cache — you cannot and do not need to supply one; if no PIN is cached for an armed machine, the call fails closed with a permission error. DISCLOSURE 2: the response includes raw OS process IDs (PIDs) and process names from the target machine — that data will reach whatever LLM/MCP client is calling this tool.
| Name | Type | Req | Description |
|---|---|---|---|
| machine | string | yes | Exact enrolled machine display name from list_machines. |
No output schema declared.
No examples provided.
care_status ~66
Read durable Machine Care facts, findings, coverage, and last-known freshness for one enrolled machine. Read-only; can work while the target is offline (it reads a stored projection, never a live round-trip).
| Name | Type | Req | Description |
|---|---|---|---|
| machine | string | yes | Exact enrolled machine display name from list_machines. |
No output schema declared.
No examples provided.
care_storage_inventory ~60
Read the latest validated cmdop-owned storage inventory for one enrolled machine. Use this to explain cmdop-related disk usage. Read-only; accepts no path argument and deletes nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| machine | string | yes | Exact enrolled machine display name from list_machines. |
No output schema declared.
No examples provided.
list_machines ~64
List the machines in the user's enrolled cmdop fleet, with each machine's online status and OS. Call this first before care_status/care_diagnose/care_storage_inventory so you know the exact machine name. Read-only. Does not return machine IDs/UUIDs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the CMDOP Machine Care MCP server?
CMDOP Machine Care is an MCP server listed in the public MCP registry as io.github.commandoperator/cmdop-care. Read-only health and storage diagnostics for an enrolled CMDOP machine fleet. This page covers its container image (ghcr.io/commandoperator/cmdop-care:v0.1.2).
Is the CMDOP Machine Care MCP server safe to use?
CMDOP Machine Care scores 53 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.
What tools does the CMDOP Machine Care MCP server expose?
CMDOP Machine Care exposes 4 tools: care_diagnose, care_status, care_storage_inventory, list_machines. Their descriptions and schemas cost roughly 356 tokens of context every time the server is loaded.
Is the CMDOP Machine Care MCP server still maintained?
CMDOP Machine Care is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.