ddflow
OCI · GHCR.IO/DELIAN/DDFLOW-MCP · 3 COMPONENTS · SCANNED OCT 5
Work-queue kernel for AI coding agents: dependencies, worktree isolation, quality gates, recovery
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
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result. View diagnostics → Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency45
- 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
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 17520 tokens (~157/item across 111 items; 106 tools + 5 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 5 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ddflow_gate_run" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 108 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
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 ddflow MCP server?
ddflow runs locally as a container image, launched with docker run --rm -i -e DDFLOW_REPO -e DDFLOW_AGENT ghcr.io/delian/ddflow-mcp:0.2.0. 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/delian/ddflow-mcp
claude mcp add delian-ddflow-mcp -- docker run --rm -i -e DDFLOW_REPO -e DDFLOW_AGENT ghcr.io/delian/ddflow-mcp:0.2.0
This image reads DDFLOW_REPO and DDFLOW_AGENT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
{
"mcpServers": {
"delian-ddflow-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"DDFLOW_REPO",
"-e",
"DDFLOW_AGENT",
"ghcr.io/delian/ddflow-mcp:0.2.0"
]
}
}
} This image reads DDFLOW_REPO and DDFLOW_AGENT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
{
"servers": {
"delian-ddflow-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"DDFLOW_REPO",
"-e",
"DDFLOW_AGENT",
"ghcr.io/delian/ddflow-mcp:0.2.0"
]
}
}
} This image reads DDFLOW_REPO and DDFLOW_AGENT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
codex mcp add delian-ddflow-mcp -- docker run --rm -i -e DDFLOW_REPO -e DDFLOW_AGENT ghcr.io/delian/ddflow-mcp:0.2.0
This image reads DDFLOW_REPO and DDFLOW_AGENT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"delian-ddflow-mcp": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"-e",
"DDFLOW_REPO",
"-e",
"DDFLOW_AGENT",
"ghcr.io/delian/ddflow-mcp:0.2.0"
],
"enabled": true
}
}
} This image reads DDFLOW_REPO and DDFLOW_AGENT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
mcp_servers:
delian-ddflow-mcp:
command: "docker"
args: ["run", "--rm", "-i", "-e", "DDFLOW_REPO", "-e", "DDFLOW_AGENT", "ghcr.io/delian/ddflow-mcp:0.2.0"] This image reads DDFLOW_REPO and DDFLOW_AGENT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
{
"McpServers": {
"delian-ddflow-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"-e",
"DDFLOW_REPO",
"-e",
"DDFLOW_AGENT",
"ghcr.io/delian/ddflow-mcp:0.2.0"
]
}
}
} This image reads DDFLOW_REPO and DDFLOW_AGENT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
{
"mcpServers": {
"delian-ddflow-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"DDFLOW_REPO",
"-e",
"DDFLOW_AGENT",
"ghcr.io/delian/ddflow-mcp:0.2.0"
]
}
}
} This image reads DDFLOW_REPO and DDFLOW_AGENT. Set them in your client's env block for this server; docker run -e passes each one through to the container.
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.
- 5 Oct 26 +31
- Injection markers: unverified → pass ▲ security
- MCP protocol: unverified → fail ▼ functional
- Schema quality: 190 → 157 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.10 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- 4 Oct 26 −30
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: fail → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Schema quality: 190 → 157 ▲ functional
- Package version: 0.1.11 → 0.1.13 functional
- Package version: 0.1.11 → 0.1.12 functional
- 3 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.10 → 0.1.11 functional
- 2 Oct 26 39
First indexed and scored.
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 8 Oct 2026 · Analysed oci/ghcr.io/delian/ddflow-mcp@0.2.0
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 →
Vulnerabilities 12 ungraded findings
From the publisher's SBOM, not graded. These advisories match packages listed in the SBOM the publisher attached to this image. A publisher naming a vulnerable package in their own image is credible, so we show them. Nothing verifies that SBOM, though, so the Known CVEs signal does not grade the image from it.
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-6v7p-g79w-8964 | CVE-2026-57585 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| PYSEC-2026-3625 | CVE-2026-57585 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-5rjg-fvgr-3xxf | CVE-2025-47273 | high | yes | |
| GHSA-h35f-9h28-mq5c | CVE-2026-59890 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N | yes |
| PYSEC-2025-49 | CVE-2025-47273 | high | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-3447 | CVE-2026-59890 | medium | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N | yes |
| GHSA-8988-9cw3-xx77 | CVE-2026-97687 | high | yes | |
| GHSA-gh4c-6fx4-qh6g | CVE-2026-97688 | medium | yes | |
| GHSA-vxq7-64xx-v4gw | CVE-2026-97689 | high | yes | |
| PYSEC-2026-4175 | CVE-2026-97687 | none | yes | |
| PYSEC-2026-4176 | CVE-2026-97688 | none | yes | |
| PYSEC-2026-4177 | CVE-2026-97689 | none | yes |
Background: What a vulnerability scan can and cannot prove →
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 →
ddflow_wait ~280
Sleep until an item can be claimed (or, with no item, until anything is ready) and return the moment it can. Use it instead of polling or asking the operator when a claim was refused for another agent's lease or overlapping files, or an unfinished dependency someone is working on. Exit 0: claim now (it says what freed it). Exit 2: deadline passed, or waiting cannot help (done, cycle, operator hold, a dependency nobody works on) and it says what to do. The holder is told you wait.
| Name | Type | Req | Description |
|---|---|---|---|
| as_agent | string | – | A subagent's own name, this call only. |
| globs | string | – | With item: the globs you will claim with (comma-separated or a JSON array), so ready means that claim will not be refused for them. |
| item | string | – | The item to wait for (default: anything ready). |
| kind | string | – | 'task' (default) or 'phase'. |
| phase | string | – | With no item: anything ready in this phase. |
| poll | number | – | Seconds between log checks (default 2). |
| timeout | number | – | Seconds to wait (default 300, at most 1800: a client may time a tool call out, so call again to keep waiting). 0 asks without waiting. |
No output schema declared.
No examples provided.
ddflow_workflow ~115
The rules THIS project runs by, in one answer: the gates every task and phase passes in order, the completion rules, parallelism caps, reviewers, and where each value came from. Call it before your first `ddflow_claim` and after any workflow change: instructions are computed once at start. Exit 1: the workflow does not hang together (e.g. a pipeline names a gate with no definition). Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| as_agent | string | – | A subagent's own name, this call only. |
No output schema declared.
No examples provided.
ddflow_workflow_drop ~130
Take a gate out of both pipelines, and out of `required`, so it does not become a requirement that requires nothing. WRITES config. The gate's DEFINITION stays, so putting it back is one call. Exit 2: it was in neither pipeline. Ask the operator first: a gate in a pipeline is a check somebody added on purpose.
| Name | Type | Req | Description |
|---|---|---|---|
| as_agent | string | – | A subagent's own name, this call only. |
| dry_run | boolean | – | Report the change and write nothing. |
| id | string | yes | The gate id to remove from the pipelines. |
No output schema declared.
No examples provided.
ddflow_workflow_gate ~323
Define or change one gate, optionally in a pipeline. WRITES the project config. `command` makes a COMMAND gate (ddflow runs it; its exit code is the evidence); `prompt` makes an AGENT gate (you perform and record it); one is required. `into` adds it to a pipeline (`after` places it, default last); `required` blocks completion without it. Ask the operator first; prefer dry_run.
| Name | Type | Req | Description |
|---|---|---|---|
| after | string | – | Place it after this gate. Default: last. |
| applies_to | string | – | 'task', 'phase' or 'both'. |
| as_agent | string | – | A subagent's own name, this call only. |
| command | string | – | Shell command to run. Makes it a command gate. |
| cwd | string | – | 'worktree' (default) or 'repo'. |
| dry_run | boolean | – | Report the change and write nothing. |
| id | string | yes | The gate id, e.g. 'lint' or 'security_scan'. |
| into | string | – | Add to the 'task', 'phase' or 'both' pipeline(s). |
| prompt | string | – | What an agent must do. Makes it an agent gate. |
| required | boolean | – | An item cannot complete without it. |
| reviewer | string | – | 'different_family' to require a reviewer from another model family, or 'same_family_ok'. |
| timeout | integer | – | Seconds before the command counts as unavailable. |
| title | string | – | Human-readable name. |
No output schema declared.
No examples provided.
ddflow_workflow_pipeline ~161
Set the ordered list of gates a task or a phase must pass. WRITES this project's config. Validated first: a gate id with no definition is REFUSED (it would block every item that reaches it); define it with `ddflow_workflow_gate`. Ask the operator before changing a pipeline -- it governs every future item, and removing a gate removes a check somebody added on purpose. dry_run shows what it would do.
| Name | Type | Req | Description |
|---|---|---|---|
| as_agent | string | – | A subagent's own name, this call only. |
| dry_run | boolean | – | Report the change and write nothing. |
| gates | string | yes | Comma-separated gate ids, in the order they run. |
| which | string | yes | 'task' or 'phase'. |
No output schema declared.
No examples provided.
ddflow_workflow_state ~62
One-call project overview: workflow, rules, decisions, active work, queue and bugs with names and priorities, blockers, and a Mermaid gate diagram. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| as_agent | string | – | A subagent's own name, this call only. |
No output schema declared.
No examples provided.
What is the ddflow MCP server?
ddflow is an MCP server listed in the public MCP registry as io.github.delian/ddflow-mcp. Work-queue kernel for AI coding agents: dependencies, worktree isolation, quality gates, recovery. This page covers its container image (ghcr.io/delian/ddflow-mcp).
Is the ddflow MCP server safe to use?
ddflow scores 40 out of 100 on VerifyMCP. The SBOM its publisher attached lists packages with 12 known advisories as of 5 October 2026. We do not grade that SBOM, as nothing verifies it. 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 ddflow MCP server expose?
ddflow exposes 106 tools: ddflow_abandon, ddflow_bisect, ddflow_block, ddflow_board, ddflow_brief, and 101 more. Their descriptions and schemas cost roughly 16,898 tokens of context every time the server is loaded.
Is the ddflow MCP server still maintained?
ddflow is still listed as active in the MCP registry. We last reached this channel on 5 October 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 ddflow MCP server under?
ddflow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.