Manufacturing Defect Mcp — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Manufacturing Defect Mcp (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A manufacturing investigation platform that combines Computer Vision outputs, Knowledge Graphs, Graph Data Science (GDS), Model Context Protocol (MCP), and Local LLM Agents to support defect analysis and engineering investigations.
The system extends traditional defect detection by providing contextual information, graph analytics, graph-based machine learning, and natural language access to manufacturing knowledge.
Traditional defect detection systems answer:
Is the product defective?
Quality engineers typically require additional context:
This project combines manufacturing telemetry, traceability data, graph analytics, and LLM reasoning to generate explainable investigation reports.
AI4I Telemetry Dataset
+
MVTec Transistor Dataset
+
Synthetic Traceability Data
↓
Data Integration Pipeline
↓
Manufacturing Dataset
↓
Neo4j Knowledge Graph
↓
Neo4j Graph Data Science
↓
FastAPI + MCP Server
↓
LLM Investigation Agent
↓
Investigation ReportManufacturing entities are represented as graph nodes.
(ProductCase)-[:PRODUCED_BY]->(Machine)
(ProductCase)-[:SUPPLIED_BY]->(Supplier)
(ProductCase)-[:BELONGS_TO_BATCH]->(Batch)
(ProductCase)-[:HAS_DEFECT]->(Defect)
(ProductCase)-[:EXHIBITS_FAILURE]->(FailureType)
(ProductCase)-[:WORKED_IN_SHIFT]->(Shift)
(ProductCase)-[:MENTIONED_IN]->(Document)Implemented using Neo4j Graph Data Science.
Identifies machines that are most influential within the manufacturing network.
Endpoint:
GET /analytics/centralityExample Insight:
Machine M5 exhibits the highest centrality score.Groups machines and suppliers with similar manufacturing behavior.
Endpoint:
GET /analytics/communitiesExample Insight:
Machines and suppliers within the same community
share similar defect patterns.Uses Neo4j GDS Node Classification Pipeline.
Workflow:
ProductCase Nodes
↓
FastRP Embeddings
↓
Logistic Regression
↓
Defect ClassificationTraining Endpoint:
POST /ml/trainPrediction Endpoint:
GET /ml/predict/{uid}Generates graph embeddings for ProductCase nodes.
Endpoint:
POST /ml/embeddingsEmbedding Size:
64 dimensionsStored as:
pc.embeddingUses cosine similarity between FastRP embeddings.
Example:
MATCH (target:ProductCase)
MATCH (other:ProductCase)
WITH target, other,
gds.similarity.cosine(
target.embedding,
other.embedding
) AS similarityEndpoint:
GET /ml/similar/{uid}Purpose:
Natural language queries are converted into Cypher using a local LLM.
Example:
Which machines have the highest defect rates?Generated Query:
MATCH ...
RETURN ...Endpoint:
POST /text-to-cypherDocuments can be ingested into the Knowledge Graph.
Supported Examples:
Endpoint:
POST /ingest-documentGenerated Knowledge:
Machine
↓
MENTIONED_IN
↓
DocumentThe MCP server exposes graph operations as tools.
Examples:
The LLM agent invokes these tools to collect evidence and generate investigation reports.
UID000001
↓
Retrieve Context
↓
Find Similar Cases
↓
Analyze Graph Patterns
↓
Collect Evidence
↓
Generate Investigation ReportExample Report Sections:
POST /syncPOST /investigate/{uid}GET /analytics/centrality
GET /analytics/communitiesPOST /ml/train
POST /ml/embeddings
GET /ml/predict/{uid}
GET /ml/similar/{uid}POST /text-to-cypherPOST /ingest-documentThis project demonstrates how Knowledge Graphs, Graph Analytics, Graph Machine Learning, MCP, and LLM Agents can be combined to transform manufacturing defect detection into explainable manufacturing investigations.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.