# MCP Task Orchestrator (oci · ghcr.io/jpicklyk/task-orchestrator)

Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates

- Trust score: 5/100 (low)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- oci · `ghcr.io/jpicklyk/task-orchestrator`: 5/100 (this document), [markdown](https://verifymcp.io/servers/jpicklyk-task-orchestrator/ghcr-io-jpicklyk-task-orchestrator.md), [page](https://verifymcp.io/servers/jpicklyk-task-orchestrator/ghcr-io-jpicklyk-task-orchestrator)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/jpicklyk/task-orchestrator`
- Version: `3.16.0`
- 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-10-22.

- **Supply Chain Security**: 0/100
  - 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.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 23/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 0/100
  - Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
- **Capabilities**: 0/100
  - Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

**Unverified: 6 categories.** Categories scored 0 because we could not verify them: 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.

## Install

### How do I install the MCP Task Orchestrator server?

MCP Task Orchestrator runs locally as a container image, launched with docker run --rm -i -e DATABASE_PATH -e USE_FLYWAY -e AGENT_CONFIG_DIR -e MCP_TRANSPORT -e MCP_HTTP_PORT -e LOG_LEVEL -e LOG_FILE ghcr.io/jpicklyk/task-orchestrator:3.16.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add jpicklyk-task-orchestrator -- docker run --rm -i -e DATABASE_PATH -e USE_FLYWAY -e AGENT_CONFIG_DIR -e MCP_TRANSPORT -e MCP_HTTP_PORT -e LOG_LEVEL -e LOG_FILE ghcr.io/jpicklyk/task-orchestrator:3.16.0
```

This image reads DATABASE_PATH, USE_FLYWAY, AGENT_CONFIG_DIR, MCP_TRANSPORT, MCP_HTTP_PORT, LOG_LEVEL and LOG_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Cursor

```json
{
  "mcpServers": {
    "jpicklyk-task-orchestrator": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DATABASE_PATH",
        "-e",
        "USE_FLYWAY",
        "-e",
        "AGENT_CONFIG_DIR",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "MCP_HTTP_PORT",
        "-e",
        "LOG_LEVEL",
        "-e",
        "LOG_FILE",
        "ghcr.io/jpicklyk/task-orchestrator:3.16.0"
      ]
    }
  }
}
```

This image reads DATABASE_PATH, USE_FLYWAY, AGENT_CONFIG_DIR, MCP_TRANSPORT, MCP_HTTP_PORT, LOG_LEVEL and LOG_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### VS Code

```json
{
  "servers": {
    "jpicklyk-task-orchestrator": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DATABASE_PATH",
        "-e",
        "USE_FLYWAY",
        "-e",
        "AGENT_CONFIG_DIR",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "MCP_HTTP_PORT",
        "-e",
        "LOG_LEVEL",
        "-e",
        "LOG_FILE",
        "ghcr.io/jpicklyk/task-orchestrator:3.16.0"
      ]
    }
  }
}
```

This image reads DATABASE_PATH, USE_FLYWAY, AGENT_CONFIG_DIR, MCP_TRANSPORT, MCP_HTTP_PORT, LOG_LEVEL and LOG_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Codex

```bash
codex mcp add jpicklyk-task-orchestrator -- docker run --rm -i -e DATABASE_PATH -e USE_FLYWAY -e AGENT_CONFIG_DIR -e MCP_TRANSPORT -e MCP_HTTP_PORT -e LOG_LEVEL -e LOG_FILE ghcr.io/jpicklyk/task-orchestrator:3.16.0
```

This image reads DATABASE_PATH, USE_FLYWAY, AGENT_CONFIG_DIR, MCP_TRANSPORT, MCP_HTTP_PORT, LOG_LEVEL and LOG_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jpicklyk-task-orchestrator": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "DATABASE_PATH",
        "-e",
        "USE_FLYWAY",
        "-e",
        "AGENT_CONFIG_DIR",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "MCP_HTTP_PORT",
        "-e",
        "LOG_LEVEL",
        "-e",
        "LOG_FILE",
        "ghcr.io/jpicklyk/task-orchestrator:3.16.0"
      ],
      "enabled": true
    }
  }
}
```

This image reads DATABASE_PATH, USE_FLYWAY, AGENT_CONFIG_DIR, MCP_TRANSPORT, MCP_HTTP_PORT, LOG_LEVEL and LOG_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Hermes

```yaml
mcp_servers:
  jpicklyk-task-orchestrator:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "DATABASE_PATH", "-e", "USE_FLYWAY", "-e", "AGENT_CONFIG_DIR", "-e", "MCP_TRANSPORT", "-e", "MCP_HTTP_PORT", "-e", "LOG_LEVEL", "-e", "LOG_FILE", "ghcr.io/jpicklyk/task-orchestrator:3.16.0"]
```

This image reads DATABASE_PATH, USE_FLYWAY, AGENT_CONFIG_DIR, MCP_TRANSPORT, MCP_HTTP_PORT, LOG_LEVEL and LOG_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Netclaw

```json
{
  "McpServers": {
    "jpicklyk-task-orchestrator": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DATABASE_PATH",
        "-e",
        "USE_FLYWAY",
        "-e",
        "AGENT_CONFIG_DIR",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "MCP_HTTP_PORT",
        "-e",
        "LOG_LEVEL",
        "-e",
        "LOG_FILE",
        "ghcr.io/jpicklyk/task-orchestrator:3.16.0"
      ]
    }
  }
}
```

This image reads DATABASE_PATH, USE_FLYWAY, AGENT_CONFIG_DIR, MCP_TRANSPORT, MCP_HTTP_PORT, LOG_LEVEL and LOG_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

### Other

```json
{
  "mcpServers": {
    "jpicklyk-task-orchestrator": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "DATABASE_PATH",
        "-e",
        "USE_FLYWAY",
        "-e",
        "AGENT_CONFIG_DIR",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "MCP_HTTP_PORT",
        "-e",
        "LOG_LEVEL",
        "-e",
        "LOG_FILE",
        "ghcr.io/jpicklyk/task-orchestrator:3.16.0"
      ]
    }
  }
}
```

This image reads DATABASE_PATH, USE_FLYWAY, AGENT_CONFIG_DIR, MCP_TRANSPORT, MCP_HTTP_PORT, LOG_LEVEL and LOG_FILE. Set them in your client's env block for this server; docker run -e passes each one through to the container.

## 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-10-02 (score 5)

First indexed and scored.

## MCP tools (0)

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/jpicklyk-task-orchestrator/ghcr-io-jpicklyk-task-orchestrator#diagnostics

## Score history

- 2026-10-22: 5
- 2026-10-21: 5
- 2026-10-20: 5
- 2026-10-19: 5
- 2026-10-18: 5
- 2026-10-17: 5
- 2026-10-16: 5
- 2026-10-15: 5
- 2026-10-14: 5
- 2026-10-13: 5
- 2026-10-12: 5
- 2026-10-10: 5
- 2026-10-08: 5
- 2026-10-06: 5
- 2026-10-04: 5
- 2026-10-03: 5
- 2026-10-02: 5

## Common questions

### What is the MCP Task Orchestrator server?

MCP Task Orchestrator is listed in the public MCP registry as io.github.jpicklyk/task-orchestrator. Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates. This page covers its container image (ghcr.io/jpicklyk/task-orchestrator).

### Is the MCP Task Orchestrator server safe to use?

MCP Task Orchestrator scores 5 out of 100 on VerifyMCP. 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.

### Is the MCP Task Orchestrator server still maintained?

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

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

## Links

- GitHub Container Registry: https://ghcr.io/jpicklyk/task-orchestrator
- Changelog RSS feed: https://verifymcp.io/servers/jpicklyk-task-orchestrator/ghcr-io-jpicklyk-task-orchestrator.xml
- Changelog JSON feed: https://verifymcp.io/servers/jpicklyk-task-orchestrator/ghcr-io-jpicklyk-task-orchestrator.json
- HTML version of this page: https://verifymcp.io/servers/jpicklyk-task-orchestrator/ghcr-io-jpicklyk-task-orchestrator