MCP Risk

Directory / server

cc.operandi/operandi

This directory entry reports an automated security scan of cc.operandi/operandi, scanned 2026-07-28. Trust grade C rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via package-source

C 68/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as cc.operandi/operandi. 1 finding
  • Registry entry: cc.operandi/operandi ↗
WARN Source repository is public and maintained §1.2
Repository health issues: no license. 5 findings
  • Repository ↗
  • Last push: 5 days ago
  • Stars: 0
  • License: none detected
  • Security policy (SECURITY.md): absent
FAIL Published package is consistent and attested §1.3
Integrity concerns: package repository field does not match the claimed source repo; package is only 5 days old; no PyPI trusted-publishing provenance. 5 findings
  • Package: operandi-mcp@1.0.3 ↗
  • Ecosystem: PyPI
  • Age: 5 days
  • Repo field matches source repo: false
  • Trusted-publishing provenance: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned. Capabilities detected: network-egress. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 2 findings
  • network-egress (outbound network calls): operandi_mcp_server.py
  • Detected capabilities: network-egress
INFO Transport & authentication §3

Local (stdio) server: runs with host-process privileges by design. Transport checks apply to remote servers; scrutiny shifts to §1/§2.
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for operandi-mcp @1.0.3 (PyPI).
UNVERIFIABLE Server-supplied instructions free of poisoning indicators §5.1–§5.4

No server-supplied instructions or tool descriptions were obtainable to scan.
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.