# Deputy (pypi · deputy-cc)

Claude Code helper: DeepSeek V4.1 Flash reviews Claude's code for bugs and gives second opinions

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `deputy-cc`: 81/100 (this document), [markdown](https://verifymcp.io/servers/alimohammadiamirhossein-deputy/deputy-cc.md), [page](https://verifymcp.io/servers/alimohammadiamirhossein-deputy/deputy-cc)

## Channel facts

- Registry: `pypi`
- Package: `deputy-cc`
- Version: `0.3.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 99/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 3 of 34 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to alimohammadiamirhossein/deputy).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 9 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1313 tokens (~218/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Deputy MCP server?

Deputy runs locally as a PyPI package, launched with uvx deputy-cc serve. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add alimohammadiamirhossein-deputy -- uvx deputy-cc serve
```

### Cursor

```json
{
  "mcpServers": {
    "alimohammadiamirhossein-deputy": {
      "command": "uvx",
      "args": [
        "deputy-cc",
        "serve"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "alimohammadiamirhossein-deputy": {
      "command": "uvx",
      "args": [
        "deputy-cc",
        "serve"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add alimohammadiamirhossein-deputy -- uvx deputy-cc serve
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alimohammadiamirhossein-deputy": {
      "type": "local",
      "command": [
        "uvx",
        "deputy-cc",
        "serve"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add alimohammadiamirhossein-deputy --command uvx --arg deputy-cc --arg serve
```

### Hermes

```yaml
mcp_servers:
  alimohammadiamirhossein-deputy:
    command: "uvx"
    args: ["deputy-cc", "serve"]
```

### Netclaw

```json
{
  "McpServers": {
    "alimohammadiamirhossein-deputy": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "deputy-cc",
        "serve"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add alimohammadiamirhossein-deputy -t stdio -c uvx -a deputy-cc serve
```

### Other

```json
{
  "mcpServers": {
    "alimohammadiamirhossein-deputy": {
      "command": "uvx",
      "args": [
        "deputy-cc",
        "serve"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 79, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 64, −14)

- [security regression] Malware scan: pass → unverified

### 2026-10-29 (score 78, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 62, 0)

- [functional] Package version: 0.3.0 → 0.3.1

### 2026-10-26 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-25 (score 61, −15)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.0 → 0.3.0

## MCP tools (6)

### `consult` (~235 tokens)

Brainstorm with a cheaper model: ideas, risks and alternatives you may have missed.
Use it when you are unsure between approaches or stuck, not on every task.

question: what you are deciding, including your current plan if you have one.
context: relevant facts, constraints and what you already ruled out.
lenses: up to 4 angles, each answered independently in parallel, for example
  ["simplest approach", "edge cases and failure modes", "performance"].
my_view: your own conclusion, written BEFORE you see Deputy's ideas. It is not sent to
  Deputy, so its ideas stay independent; it is echoed back so you can compare honestly.
project_dir: absolute path of the project, only if Deputy picked the wrong folder.

The answers are UNVERIFIED suggestions from a weaker model. Weigh them below your own
analysis, check them against the code, and adopt only what holds up.

Input parameters:

- `context` (string)
- `lenses`
- `my_view` (string)
- `project_dir` (string)
- `question` (string, required)
- `thinking`

Output parameters:

- `result` (string)

### `review` (~279 tokens)

Have independent cheap reviewers hunt for defects in a change, one per lens, in parallel.
Use it for risky or large changes, not routine ones whose tests pass.
By default it reviews your uncommitted changes (git diff against HEAD, plus new files).

focus: what the change is supposed to do, so reviewers can spot mismatches.
diff: the change to review, if you do not want the automatic git diff.
base: compare against this revision instead of HEAD (for example "main").
paths: limit the review to these files or folders.
lenses: up to 4 review angles; default ["correctness and logic bugs",
  "edge cases, error handling and missing tests"].
thinking: leave it out for a fast review (low thinking by default); "high" or "max" think
  longer, for an especially risky change.
project_dir: absolute path of the project, only if Deputy picked the wrong folder.

Findings are UNVERIFIED and may be false positives. Verify each against the code; fix only
what you confirm, and tell the user which findings you rejected and why.

Input parameters:

- `base` (string)
- `diff` (string)
- `focus` (string)
- `lenses`
- `paths`
- `project_dir` (string)
- `thinking`

Output parameters:

- `result` (string)

### `investigate` (~120 tokens)

Ask Deputy a question that needs a lot of reading: where something is handled, how a flow
works, what a large log says. Deputy can only list, read and search files. Returns a compact
answer with file:line evidence. Treat it as leads: read the cited lines before acting.
project_dir: absolute path of the project, only if Deputy picked the wrong folder.

Input parameters:

- `context` (string)
- `project_dir` (string)
- `question` (string, required)
- `thinking`
- `workdir` (string)

Output parameters:

- `result` (string)

### `delegate` (~196 tokens)

Hand a well-specified coding task to Deputy. It reads and edits files and runs commands
in the workspace on its own, then returns a short report with the files it changed.
In accuracy mode, use this only when the user explicitly asks for delegation.

task: the goal, scope (files or folders), constraints and acceptance criteria.
context: facts Deputy cannot discover itself (decisions made, conventions, error messages).
thinking: "high" (default) or "max" for hard tasks.
workdir: subfolder of the workspace to treat as the root (default: whole workspace).
project_dir: absolute path of the project, only if Deputy picked the wrong folder.

Verify the result yourself before relying on it: review the changed files and run tests.

Input parameters:

- `context` (string)
- `project_dir` (string)
- `task` (string, required)
- `thinking`
- `workdir` (string)

Output parameters:

- `result` (string)

### `stats` (~39 tokens)

Show roughly how many tokens and how much money Deputy saved: this session, today, the
last 7 days and all time. Makes no network calls.

Output parameters:

- `result` (string)

### `status` (~52 tokens)

Show Deputy's mode, model, thinking level, workspace, whether a key is set, and what this
session has spent and saved. Makes no network calls to the model provider.

Input parameters:

- `project_dir` (string)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/alimohammadiamirhossein-deputy/deputy-cc#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 80
- 2026-11-02: 80
- 2026-11-01: 79
- 2026-10-31: 64
- 2026-10-30: 78
- 2026-10-29: 78
- 2026-10-28: 62
- 2026-10-27: 62
- 2026-10-26: 62
- 2026-10-25: 61
- 2026-10-24: 76

## Common questions

### What is the Deputy MCP server?

Deputy is an MCP server listed in the public MCP registry as io.github.alimohammadiamirhossein/deputy. Claude Code helper: DeepSeek V4.1 Flash reviews Claude's code for bugs and gives second opinions. This page covers its PyPI package (deputy-cc).

### Is the Deputy MCP server safe to use?

Deputy scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Deputy MCP server expose?

Deputy exposes 6 tools: consult, review, investigate, delegate, stats, status. Their descriptions and schemas cost roughly 921 tokens of context every time the server is loaded.

### Is the Deputy MCP server still maintained?

Deputy is still listed as active in the MCP registry. We last reached this channel on 5 November 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 Deputy MCP server under?

Deputy declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Deputy MCP server?

VerifyMCP ran 16 checks on Deputy, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- PyPI project: https://pypi.org/project/deputy-cc/
- Socket report: https://socket.dev/pypi/package/deputy-cc
- Repository: https://github.com/alimohammadiamirhossein/deputy
- Changelog RSS feed: https://verifymcp.io/servers/alimohammadiamirhossein-deputy/deputy-cc.xml
- Changelog JSON feed: https://verifymcp.io/servers/alimohammadiamirhossein-deputy/deputy-cc/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/alimohammadiamirhossein-deputy/deputy-cc.json
- HTML version of this page: https://verifymcp.io/servers/alimohammadiamirhossein-deputy/deputy-cc