quality-control-plan-mcp

MCPcommunity
v0.1.0Imnoo AGMITUpdated 16d agonpmGitHub

MCP server that generates quality control plans and inspection reports from technical-drawing PDFs — automatic extraction of tolerances, fits, threads, GD&T and surface finishes, balloon numbering, acceptance limits, ballooned drawing PDF and Excel measur

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
227Downloads/wk
16d agoLast update
Reads these credentials
  • IMNOO_ACCESS_TOKENAPI keyoptional

    Optional. Your Imnoo account token (the id token of your quality-check-protocol.imnoo.com login). Raises the analysis limit from 1 free drawing per day per IP to your plan's quota. Everything except…

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
AuthorImnoo AG
LicenseMIT
Version0.1.0
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface6 tools · none privileged
Security scan✓ Cleanv0.1.0 · 19d agoHow well does this scan work?
CODEdist/index.jsVery large base64-looking blob in source
EvalsNone
IndexedSep 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

6 tools · none privileged
Statically extracted from the published packagev0.1.0 · 19d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

quality-control-planNo description published

This tool published no description. Forge does not invent one.

analyze_drawingNo description published

This tool published no description. Forge does not invent one.

load_analysisOpen 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…

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…

No input schema was published for this tool.

build_quality_planNo description published

This tool published no description. Forge does not invent one.

export_quality_plan_excelNo description published

This tool published no description. Forge does not invent one.

export_inspection_pdfNo description published

This tool published no description. Forge does not invent one.

1 of 6 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server that generates quality control plans and inspection reports from technical-drawing PDFs — automatic extraction of tolerances, fits, threads, GD&T and surface finishes, balloon numbering, acceptance limits, ballooned drawing PDF and Excel measur

Keywords
mcpmodel-context-protocolmcp-serverquality-control-planquality-controlinspection-planinspection-reportfirst-article-inspectionballooningballooned-drawingtechnical-drawingengineering-drawingpdftolerancesgd&tmanufacturingcncquality-assuranceimnoo
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-14 — observed resolution, not a publisher declaration.

60 packages resolved · 5 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

49 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+37 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in documents & pdfs