# Orchestrator (pypi · orchestrator-mcp-server)

Let one coding-agent CLI consult another: Codex, Claude Code, OpenCode, Copilot or Antigravity.

- Trust score: 57/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-04

## Components

- pypi · `orchestrator-mcp-server`: 57/100 (this document), [markdown](https://verifymcp.io/servers/crak1644-orchestrator-mcp/orchestrator-mcp-server.md), [page](https://verifymcp.io/servers/crak1644-orchestrator-mcp/orchestrator-mcp-server)

## Channel facts

- Registry: `pypi`
- Package: `orchestrator-mcp-server`
- Version: `0.11.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-04.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - 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.
  - 1 of 29 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 35 tokens (~35/item across 1 items; 1 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

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

Orchestrator runs locally as a PyPI package, launched with uvx orchestrator-mcp-server. 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 crak1644-orchestrator-mcp -- uvx orchestrator-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "crak1644-orchestrator-mcp": {
      "command": "uvx",
      "args": [
        "orchestrator-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "crak1644-orchestrator-mcp": {
      "command": "uvx",
      "args": [
        "orchestrator-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add crak1644-orchestrator-mcp -- uvx orchestrator-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "crak1644-orchestrator-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "orchestrator-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add crak1644-orchestrator-mcp --command uvx --arg orchestrator-mcp-server
```

### Hermes

```yaml
mcp_servers:
  crak1644-orchestrator-mcp:
    command: "uvx"
    args: ["orchestrator-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "crak1644-orchestrator-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "orchestrator-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add crak1644-orchestrator-mcp -t stdio -c uvx -a orchestrator-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "crak1644-orchestrator-mcp": {
      "command": "uvx",
      "args": [
        "orchestrator-mcp-server"
      ]
    }
  }
}
```

## 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-04 (score 57, 0)

- [security improvement] Malware scan: unverified → pass
- [functional] Package version: 0.10.4 → 0.11.0

### 2026-10-03 (score 57, +1)

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

### 2026-10-01 (score 56, +1)

- [functional] Package version: 0.10.3 → 0.10.4

### 2026-09-30 (score 55, 0)

- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.10.0 → 0.10.3
- [functional] Package version: 0.10.0 → 0.10.2
- [functional] Package version: 0.10.0 → 0.10.1

### 2026-09-29 (score 55)

First indexed and scored.

## MCP tools (1)

### `orchestrator_setup` (~35 tokens)

Say how to finish setting up orchestrator: this server started without a
config, so none of its other tools exist yet.

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/crak1644-orchestrator-mcp/orchestrator-mcp-server#diagnostics

## Score history

- 2026-10-04: 57
- 2026-10-03: 57
- 2026-10-02: 56
- 2026-10-01: 56
- 2026-09-30: 55
- 2026-09-29: 55

## Common questions

### What is the Orchestrator MCP server?

Orchestrator is an MCP server listed in the public MCP registry as io.github.crAK1644/orchestrator-mcp. Let one coding-agent CLI consult another: Codex, Claude Code, OpenCode, Copilot or Antigravity. This page covers its PyPI package (orchestrator-mcp-server).

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

Orchestrator scores 57 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 October 2026. 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 Orchestrator MCP server expose?

Orchestrator exposes 1 tool: orchestrator_setup. Their descriptions and schemas cost roughly 35 tokens of context every time the server is loaded.

### Is the Orchestrator MCP server still maintained?

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

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

- PyPI project: https://pypi.org/project/orchestrator-mcp-server/
- Socket report: https://socket.dev/pypi/package/orchestrator-mcp-server
- Repository: https://github.com/crAK1644/orchestrator-mcp
- Changelog RSS feed: https://verifymcp.io/servers/crak1644-orchestrator-mcp/orchestrator-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/crak1644-orchestrator-mcp/orchestrator-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/crak1644-orchestrator-mcp/orchestrator-mcp-server