Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Deputy is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Claude Code helper: DeepSeek V4.1 Flash reviews Claude's code for bugs and gives second opinions
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user alimohammadiamirhossein-deputy-mcp '--' uvx deputy-cc serve
# 2 — ask your agent for something these tools do
# consult, review, investigate and 3 more
Deputy costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Deputy as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user alimohammadiamirhossein-deputy-mcp '--' uvx deputy-cc serveReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take DEPUTY_PROVIDER (deepinfra (DeepSeek V4.1 Flash) or xai (Grok, default model grok-4.3).), DEEPINFRA_API_KEY (DeepInfra API key (deepinfra.com, Dashboard > API Keys), for the default provider. Only sent to api.deepinfra.com.), XAI_API_KEY (xAI API key (console.x.ai), when DEPUTY_PROVIDER is xai. Only sent to api.x.ai.), DEPUTY_MODE (accuracy: Claude writes all code; Deputy reviews and consults. lean: fewest Claude tokens, little accuracy loss. balanced: Deputy takes mechanical work. partner: Deputy does all low-level work and gives ideas. savings: Deputy takes most coding.), DEPUTY_THINKING (How hard the helper model thinks.), DEPUTY_MODEL (Model id served by the endpoint.), DEPUTY_BASE_URL (Any OpenAI-compatible endpoint (https, or http on localhost for a local model).), DEPUTY_WORKSPACE (Project folder Deputy may read and edit. Defaults to the client's project folder.), DEPUTY_API_KEY (API key for a non-DeepInfra endpoint. Takes precedence over DEEPINFRA_API_KEY.) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Brainstorm with a cheaper model: ideas, risks and alternatives you may have missed.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| context | string | no | — |
| lenses | array | no | — |
| my_view | string | no | — |
| thinking | no | — | |
| project_dir | string | no | — |
Have independent cheap reviewers hunt for defects in a change, one per lens, in parallel.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| focus | string | no | — |
| diff | string | no | — |
| base | string | no | — |
| paths | array | no | — |
| lenses | array | no | — |
| thinking | no | — | |
| project_dir | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| context | string | no | — |
| thinking | no | — | |
| workdir | string | no | — |
| project_dir | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task | string | yes | — |
| context | string | no | — |
| thinking | no | — | |
| workdir | string | no | — |
| project_dir | string | no | — |
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.
Takes no parameters.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_dir | string | no | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Deputy or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (6 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| consult | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| review | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| investigate | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| delegate | external-sink | external-sink: declares readOnlyHint: false, destructiveHint: true, openWorldHint: true |
| stats | no tags | |
| status | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Deputy can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.