cc.operandi/operandi
PYPI · OPERANDI-MCP · SCANNED SEP 20
Grounded, safety-checked appliance operation packages for robots and agents. Zero-config trial.
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 Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
- 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: the license (Proprietary) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 59 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 397 tokens (~99/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 Management90
- Stability observed for 27 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 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the cc.operandi/operandi MCP server?
cc.operandi/operandi runs locally as a PyPI package, launched with uvx operandi-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 · operandi-mcp
claude mcp add cc-operandi-operandi -- uvx operandi-mcp
{
"mcpServers": {
"cc-operandi-operandi": {
"command": "uvx",
"args": [
"operandi-mcp"
]
}
}
} {
"servers": {
"cc-operandi-operandi": {
"command": "uvx",
"args": [
"operandi-mcp"
]
}
}
} codex mcp add cc-operandi-operandi -- uvx operandi-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"cc-operandi-operandi": {
"type": "local",
"command": [
"uvx",
"operandi-mcp"
],
"enabled": true
}
}
} openclaw mcp add cc-operandi-operandi --command uvx --arg operandi-mcp
mcp_servers:
cc-operandi-operandi:
command: "uvx"
args: ["operandi-mcp"] {
"McpServers": {
"cc-operandi-operandi": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"operandi-mcp"
]
}
}
} assistant mcp add cc-operandi-operandi -t stdio -c uvx -a operandi-mcp
{
"mcpServers": {
"cc-operandi-operandi": {
"command": "uvx",
"args": [
"operandi-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.
- 20 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.
- 18 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.
- 17 Sept 26 −3
- Stability: pass → 0.80 functional
- 16 Sept 26 0
- Stability: 0.97 → pass security
- 15 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.
- 14 Sept 26 −15
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- 11 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.
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 pypi/operandi-mcp@1.0.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
find_by_capability ~73
Find appliances by what they DO (e.g. 'heat', 'wash', 'brew', 'defrost') — useful when an agent has a goal but not a specific model in mind.
| Name | Type | Req | Description |
|---|---|---|---|
| capability | string | yes | A function tag, e.g. 'heat' / 'wash' / 'brew'. |
No output schema declared.
No examples provided.
get_operation_package ~126
Get the robot-executable operation package for an appliance: model-exact ordered procedures, a control map with grounding (where each control is + how it is actuated), per-step verification signals, a recovery state machine, and a safety envelope (hazards / interlocks / never-do). This is the grounded knowledge a general model hallucinates without. Optionally target one procedure (e.g. 'defrost').
| Name | Type | Req | Description |
|---|---|---|---|
| procedure | string | – | Optional procedure name/id (default: the primary task). |
| ref | string | yes | Catalog slug or model id from identify_appliance. |
No output schema declared.
No examples provided.
identify_appliance ~152
Resolve which appliance an agent/robot is looking at, from observed text or panel labels, to an OPERANDI catalog object. Call this first, then get_operation_package with the returned slug. Returns ranked matches with confidence.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Optional brand hint if known. |
| category | string | – | Optional category hint, e.g. 'microwave_oven'. |
| limit | integer | – | Max matches (1-20, default 5). |
| panel_labels | array | – | Optional control labels OCR'd off the panel (helps when the nameplate is hidden). |
| query | string | yes | Observed nameplate / model text (e.g. 'Samsung ME20H705MSS'). |
No output schema declared.
No examples provided.
list_appliances ~46
Browse the appliances OPERANDI can operate, optionally filtered by category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Optional category filter. |
| limit | integer | – | Max results (default 25). |
No output schema declared.
No examples provided.
What is the cc.operandi/operandi MCP server?
cc.operandi/operandi is an MCP server listed in the public MCP registry as cc.operandi/operandi. Grounded, safety-checked appliance operation packages for robots and agents. Zero-config trial. This page covers its PyPI package (operandi-mcp).
Is the cc.operandi/operandi MCP server safe to use?
cc.operandi/operandi scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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 cc.operandi/operandi MCP server expose?
cc.operandi/operandi exposes 4 tools: identify_appliance, get_operation_package, list_appliances, find_by_capability. Their descriptions and schemas cost roughly 397 tokens of context every time the server is loaded.
Is the cc.operandi/operandi MCP server still maintained?
cc.operandi/operandi 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.
What licence is the cc.operandi/operandi MCP server under?
cc.operandi/operandi declares the Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.