Predictive Maintenance

io.github.LGDiMaggioPublished by GitHub account LGDiMaggiov0.13.0Updated Oct 24, 2026

Industrial vibration analysis, bearing fault diagnosis, ISO 20816, and ML anomaly detection

VerifiedSTDIODesktop onlyData & AnalyticsAI & ML

Overview

AI-generated overview

Lets an assistant analyze industrial vibration data for bearing faults, ISO 20816 checks, and ML anomaly detection.

What you can do
This local MCP server exposes tools for industrial vibration analysis. Based on its description, it covers bearing fault diagnosis, assessment against the ISO 20816 vibration standard, and machine-learning anomaly detection on vibration signals. No individual tool names or parameters are published in the available material.
When to use it
Consider it when an assistant needs to help interpret machinery vibration measurements, screen rotating equipment for bearing faults, or check vibration levels against ISO 20816 limits. It is aimed at predictive-maintenance work rather than general data analysis.
Requirements
Runs as a local process on the user's machine, installed from the PyPI package predictive-maintenance-mcp over stdio, so a Python environment is needed. It is desktop only and not available as a web executable. No authentication, environment variables, or headers are declared.
Before you install
The published description does not state what data the server reads, stores, or sends anywhere, and no tool list is available, so review the package before pointing it at sensitive plant or equipment data. No credentials, payments, or write actions are declared.

Installation

In SourceWeft

  1. Open Predictive Maintenance in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.13.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.