io.github.ArchiPlan-io/production-scheduling-mcp
PYPI · PRODUCTION-SCHEDULING-MCP
A small OR-Tools production scheduler for AI assistants.
Available components
Last scanned (4 hours ago)
Scores higher than 57% of PyPI servers
Category CI/CD and DevOps
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 0 of 36 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Build provenance not yet verified. View diagnostics → Unverified
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability61
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 76 tokens (~38/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 45
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 5 Nov 2026 · Analysed pypi/production-scheduling-mcp@0.1.0
Provenance Inconclusive
We could not complete the check, so nothing is claimed either way. This is a gap on our side, not a finding about the package.
| Result | Inconclusive |
|---|---|
| Ecosystem | pypi |
| Reason | Unsupported forge |
| Discovered via | Registry attestation endpoint |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 36 packages
| Packages resolved | 36 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_example ~19
Return a small example shop with CNC and assembly orders.
Input schema present but exposes no named parameters.
Structured output declared, but exposes no named fields.
No examples provided.
solve_schedule ~57
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).
| Name | Type | Req | Description |
|---|---|---|---|
| problem | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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.
pypi · production-scheduling-mcp
claude mcp add archiplan-io-production-scheduling-mcp -- uvx production-scheduling-mcp
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.