# Quality Control Plan Generator (npm · quality-control-plan-mcp)

Quality control plans from drawing PDFs: auto-extracted tolerances, balloons, Excel + PDF reports.

- Trust score: 75/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-22

## Components

- npm · `quality-control-plan-mcp`: 75/100 (this document), [markdown](https://verifymcp.io/servers/com-imnoo-quality-control-plan/quality-control-plan-mcp.md), [page](https://verifymcp.io/servers/com-imnoo-quality-control-plan/quality-control-plan-mcp)

## Channel facts

- Registry: `npm`
- Package: `quality-control-plan-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-09-22.

- **Supply Chain Security**: 97/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 47 of 117 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/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 11 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1506 tokens (~301/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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.

## Install

### How do I install the Quality Control Plan Generator MCP server?

Quality Control Plan Generator runs locally as an npm package, launched with npx -y quality-control-plan-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 com-imnoo-quality-control-plan -- npx -y quality-control-plan-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-imnoo-quality-control-plan": {
      "command": "npx",
      "args": [
        "-y",
        "quality-control-plan-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-imnoo-quality-control-plan": {
      "command": "npx",
      "args": [
        "-y",
        "quality-control-plan-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-imnoo-quality-control-plan -- npx -y quality-control-plan-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-imnoo-quality-control-plan": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "quality-control-plan-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-imnoo-quality-control-plan --command npx --arg -y --arg quality-control-plan-mcp
```

### Hermes

```yaml
mcp_servers:
  com-imnoo-quality-control-plan:
    command: "npx"
    args: ["-y", "quality-control-plan-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-imnoo-quality-control-plan": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "quality-control-plan-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-imnoo-quality-control-plan -t stdio -c npx -a -y quality-control-plan-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-imnoo-quality-control-plan": {
      "command": "npx",
      "args": [
        "-y",
        "quality-control-plan-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-09-22 (score 75, +1)

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

### 2026-09-19 (score 74, +1)

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

### 2026-09-18 (score 73, +3)

- [functional improvement] Stability: unverified → 0.23

### 2026-09-14 (score 70, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-09-13 (score 70, 0)

- [functional regression] Security disclosure: fail → unverified

### 2026-09-12 (score 70, +15)

- [security improvement] Malware scan: unverified → pass

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

First indexed and scored.

## MCP tools (5)

### `analyze_drawing` (~336 tokens)

Analyse a drawing PDF (Imnoo drawing analysis)

Upload a technical-drawing PDF to Imnoo's drawing analysis and return every inspection characteristic it detects — dimensional tolerances (⌀50 ±0.05, 12 +0.2/-0.1), ISO fit classes (H7 drills, g6 shafts), threads and fine threads, geometric tolerances (GD&T frames) and surface finishes (Ra/Rz) — each with a feature id, value, PDF page, position and the balloon number printed on the drawing when there is one, plus the title block (drawing/article number, material, general tolerance). Analysis takes roughly 20–120 s; the call waits up to timeout_seconds and otherwise returns status "processing" with the drawing_id to resume with. analyze_drawing uploads the PDF to Imnoo's drawing analysis (the service behind the web app): 1 free analysis per day per IP address, more when signed in; uploaded files are deleted automatically after a short retention period and nothing else is stored. Use save_analysis_to to keep the analysis JSON for offline reuse with load_analysis.

Input parameters:

- `drawing_id` (string): instead of pdf_path: the drawing_id of an earlier upload that returned status "processing" — keeps waiting for it without a new upload
- `pdf_path` (string): path to the drawing PDF to analyse (vector or scanned, ≤ 30 MB)
- `save_analysis_to` (string): write the analysis JSON to this path (re-open it later with load_analysis, no upload needed)
- `timeout_seconds` (integer): how long to wait for the analysis before returning "processing" (default 180)

### `load_analysis` (~140 tokens)

Open a saved drawing analysis (offline)

Open a drawing analysis JSON saved earlier (analyze_drawing with save_analysis_to, or the Imnoo FileStore analysis document) and register it as a drawing for the plan and export tools. Fully offline — no upload, no daily credit. Pass pdf_path as well so the drawing exports can draw on the original PDF and write next to it.

Input parameters:

- `analysis_path` (string, required): path to the analysis JSON
- `drawing_id` (string): id to register the drawing under (default: the analysis id, else the file name)
- `pdf_path` (string): path to the matching drawing PDF (needed for the ballooned/package PDF exports)

### `build_quality_plan` (~184 tokens)

Build the quality control plan

Turn an analysed drawing into the quality control plan the documents will print: one row per characteristic with its balloon number (numeric, padded or type-prefixed; printed drawing numbers kept by default), acceptance limits computed from nominal ± tolerance (dimensional tolerances only — fits, threads, GD&T and surface finishes are judged with gauges), the default measuring instrument per type, the inspection class/rate, and the section order. Deterministic and offline: adjust the plan options and call again until the plan is right, then pass the same options to the export tools.

Input parameters:

- `drawing_id` (string, required): from analyze_drawing or load_analysis
- `plan` (object): Plan settings — shared by build_quality_plan and both export tools; pass the same object to every call so the documents match the reviewed plan. Everything is optional; defaults reproduce the web app…

### `export_quality_plan_excel` (~240 tokens)

Export the Excel measurement and inspection report

Write the quality plan as the "Measurement and inspection report" workbook (.xlsx): headline with the inspection class, header block (article name, ET-No., batch number, inspection rate), the visual-inspection checklist (a–e), the dimensional-conformity table (Insp. dim. no. · nominal dimension or thread size · tolerance range · measuring instrument · actual dimension · deviation · date · inspector), change-tracking footnotes and the special-release/signature block — cell for cell the report the Imnoo calculator produces. Default location: next to the drawing PDF as <drawing number>_<inspection class>.xlsx.

Input parameters:

- `drawing_id` (string, required): from analyze_drawing or load_analysis
- `output_path` (string): target .xlsx path, or a directory (default: next to the drawing PDF, else the working directory)
- `overwrite` (boolean): allow replacing an existing file
- `plan` (object): Plan settings — shared by build_quality_plan and both export tools; pass the same object to every call so the documents match the reviewed plan. Everything is optional; defaults reproduce the web app…

### `export_inspection_pdf` (~277 tokens)

Export the ballooned drawing / inspection package PDF

Write the inspection PDF. variant "package" (default): the original drawing pages with translucent boxes on every selected characteristic, numbered balloons and optional leader arrows, followed by the printed plan (general-information form, feature table with colored number chips, instrument and sample fill-in lines, acceptance criteria and result checkboxes, final approval). "ballooned": the marked-up drawing pages only. "plan": the plan document only (no drawing pages, no PDF needed). The source PDF is never modified. Default location: next to the drawing PDF as <drawing number>_inspection-package.pdf / _ballooned.pdf / _quality-plan.pdf.

Input parameters:

- `drawing_id` (string, required): from analyze_drawing or load_analysis
- `output_path` (string): target .pdf path, or a directory (default: next to the drawing PDF, else the working directory)
- `overwrite` (boolean): allow replacing an existing file
- `pdf_path` (string): the original drawing PDF when the server does not know it yet (load_analysis without pdf_path)
- `plan` (object): Plan settings — shared by build_quality_plan and both export tools; pass the same object to every call so the documents match the reviewed plan. Everything is optional; defaults reproduce the web app…
- `variant` (string): default package

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-imnoo-quality-control-plan/quality-control-plan-mcp#diagnostics

## Score history

- 2026-09-22: 75
- 2026-09-21: 74
- 2026-09-20: 74
- 2026-09-19: 74
- 2026-09-18: 73
- 2026-09-17: 70
- 2026-09-16: 70
- 2026-09-15: 70
- 2026-09-14: 70
- 2026-09-13: 70
- 2026-09-12: 70
- 2026-09-11: 55

## Common questions

### What is the Quality Control Plan Generator MCP server?

Quality Control Plan Generator is an MCP server listed in the public MCP registry as com.imnoo/quality-control-plan. Quality control plans from drawing PDFs: auto-extracted tolerances, balloons, Excel + PDF reports. This page covers its npm package (quality-control-plan-mcp).

### Is the Quality Control Plan Generator MCP server safe to use?

Quality Control Plan Generator scores 75 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. It declares no install or post-install scripts. 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 Quality Control Plan Generator MCP server expose?

Quality Control Plan Generator exposes 5 tools: analyze_drawing, load_analysis, build_quality_plan, export_quality_plan_excel, export_inspection_pdf. Their descriptions and schemas cost roughly 1,177 tokens of context every time the server is loaded.

### Is the Quality Control Plan Generator MCP server still maintained?

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

Quality Control Plan Generator 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

- npm package: https://www.npmjs.com/package/quality-control-plan-mcp
- Socket report: https://socket.dev/npm/package/quality-control-plan-mcp
- Repository: https://github.com/imnoo-team/quality-control-plan-mcp
- Website: https://quality-check-protocol.imnoo.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-imnoo-quality-control-plan/quality-control-plan-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-imnoo-quality-control-plan/quality-control-plan-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-imnoo-quality-control-plan/quality-control-plan-mcp