# io.github.ArchiPlan-io/production-scheduling-mcp (pypi · production-scheduling-mcp)

A small OR-Tools production scheduler for AI assistants.

- Trust score: 60/100 (medium)
- Change this week: +15
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- pypi · `production-scheduling-mcp`: 60/100 (this document), [markdown](https://verifymcp.io/servers/archiplan-io-production-scheduling-mcp/production-scheduling-mcp.md), [page](https://verifymcp.io/servers/archiplan-io-production-scheduling-mcp/production-scheduling-mcp)

## Channel facts

- Registry: `pypi`
- Package: `production-scheduling-mcp`
- Version: `0.1.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-11-05.

- **Supply Chain Security**: 100/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.
  - 0 of 36 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 19/100
  - Repository check failed: no source repository is declared.
  - Build provenance not yet verified.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 76 tokens (~38/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 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.

**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.

## Install

### How do I install the io.github.ArchiPlan-io/production-scheduling-mcp server?

io.github.ArchiPlan-io/production-scheduling-mcp runs locally as a PyPI package, launched with uvx production-scheduling-mcp. 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 archiplan-io-production-scheduling-mcp -- uvx production-scheduling-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "archiplan-io-production-scheduling-mcp": {
      "command": "uvx",
      "args": [
        "production-scheduling-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "archiplan-io-production-scheduling-mcp": {
      "command": "uvx",
      "args": [
        "production-scheduling-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add archiplan-io-production-scheduling-mcp -- uvx production-scheduling-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "archiplan-io-production-scheduling-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "production-scheduling-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add archiplan-io-production-scheduling-mcp --command uvx --arg production-scheduling-mcp
```

### Hermes

```yaml
mcp_servers:
  archiplan-io-production-scheduling-mcp:
    command: "uvx"
    args: ["production-scheduling-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "archiplan-io-production-scheduling-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "production-scheduling-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add archiplan-io-production-scheduling-mcp -t stdio -c uvx -a production-scheduling-mcp
```

### Other

```json
{
  "mcpServers": {
    "archiplan-io-production-scheduling-mcp": {
      "command": "uvx",
      "args": [
        "production-scheduling-mcp"
      ]
    }
  }
}
```

## 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-05 (score 60, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-29 (score 45)

First indexed and scored.

## MCP tools (2)

### `solve_schedule` (~57 tokens)

Schedule ordered shop-floor work across machines and machine downtime.

Provide machines (name and optional down_times in hours) and orders (name,
optional due_hour and priority, plus ordered steps with hours and eligible machines).

Input parameters:

- `problem` (object, required)

### `get_example` (~19 tokens)

Return a small example shop with CNC and assembly orders.

## Diagnostics

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

## Score history

- 2026-11-05: 60
- 2026-11-04: 45
- 2026-11-03: 45
- 2026-11-02: 45
- 2026-11-01: 45
- 2026-10-31: 45
- 2026-10-30: 45
- 2026-10-29: 45

## Common questions

### What is the io.github.ArchiPlan-io/production-scheduling-mcp server?

io.github.ArchiPlan-io/production-scheduling-mcp is listed in the public MCP registry as io.github.ArchiPlan-io/production-scheduling-mcp. A small OR-Tools production scheduler for AI assistants. This page covers its PyPI package (production-scheduling-mcp).

### Is the io.github.ArchiPlan-io/production-scheduling-mcp server safe to use?

io.github.ArchiPlan-io/production-scheduling-mcp scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 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 io.github.ArchiPlan-io/production-scheduling-mcp server expose?

io.github.ArchiPlan-io/production-scheduling-mcp exposes 2 tools: solve_schedule, get_example. Their descriptions and schemas cost roughly 76 tokens of context every time the server is loaded.

### Is the io.github.ArchiPlan-io/production-scheduling-mcp server still maintained?

io.github.ArchiPlan-io/production-scheduling-mcp 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 io.github.ArchiPlan-io/production-scheduling-mcp server under?

io.github.ArchiPlan-io/production-scheduling-mcp 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 io.github.ArchiPlan-io/production-scheduling-mcp server?

VerifyMCP ran 13 checks on io.github.ArchiPlan-io/production-scheduling-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 9 more. 3 items could not be completed, a gap on our side rather than a finding about io.github.ArchiPlan-io/production-scheduling-mcp: Provenance, Security disclosure and Stability. One category scores 0 for that reason, because we only credit what we can confirm. 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/production-scheduling-mcp/
- Socket report: https://socket.dev/pypi/package/production-scheduling-mcp
- Changelog RSS feed: https://verifymcp.io/servers/archiplan-io-production-scheduling-mcp/production-scheduling-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/archiplan-io-production-scheduling-mcp/production-scheduling-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/archiplan-io-production-scheduling-mcp/production-scheduling-mcp.json
- HTML version of this page: https://verifymcp.io/servers/archiplan-io-production-scheduling-mcp/production-scheduling-mcp