Tracepass MCP Server vs Predictive Maintenance MCP Server
A side-by-side look at the Tracepass MCP Server and Predictive Maintenance MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Tracepass MCP Server for industrial & iot work as a local process; choose Predictive Maintenance MCP Server for industrial & iot as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Tracepass MCP Server when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TRACEPASS_API_KEY, TRACEPASS_BASE_URL. - You want tools like
tracepass_products, tracepass_passports, tracepass_passport_fields.
Choose Predictive Maintenance MCP Server when
- You need dedicated capabilities in the Industrial & IoT domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_signals, generate_test_signal, load_signal.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Industrial & IoT | Industrial & IoT |
| Quality signal | 64/100 · Good | 63/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | TRACEPASS_API_KEYTRACEPASS_BASE_URL | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 105 |
| Directory activity | 3 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 6 | 34 |
| Full listing | View Tracepass MCP Server | View Predictive Maintenance MCP Server |
Tools & capabilities
Tracepass MCP Server tools 6
tracepass_productsManage the TracePass product catalogue. A product is the catalogue layer — one product can have many passports (one per serialised unit). Products are not billable on their own. Actions (pass via `action`, with `args`): - list — args: { page?, limit? (≤100), category?, status?, search? }. Read-only. - get — args: { id }. Read-only. - create — args: { name, model, category, description? }. `category` is one of: battery, textile, electronics, construction, steel, detergents, paints-coatings, packaging, furniture, tyres, jewelry, toys, fmcg. - update — args: { id, name?, model?, description? }; pass at least one field to change. - create_batch — args: { products: [ { name, model, category, description? }, … ] }, up to 100. Partial-success: the response carries a per-item status, so some items can be created while others error. The whole batch consumes N writes upfront; if that would exceed the daily cap NOTHING is created (429). - archive — args: { id }. Soft-archive a product. Blocked with 409 while any non-archived passport still references it — archive those passports first. This is reversible and is NOT deletion.tracepass_passportsManage Digital Product Passports — create, read, and run lifecycle actions. IMPORTANT: `create` consumes a DPP slot on the account's plan and IS BILLABLE. Creating a passport beyond the included quota incurs a per-passport overage charge; if over quota the tool returns a 402-style message — only re-run with args.confirmOverage=true after the user explicitly agrees to the charge. `archive` is IRREVERSIBLE (the public QR permanently 404s); prefer `suspend` when a change might be undone. Actions (pass via `action`, with `args`): - list — args: { page?, limit? (≤100), productId?, status?, search? }. status ∈ draft|in_review|approved|published|suspended|expired|archived. Read-only. - get — args: { id, format? (summary|full), lang? }. Read-only. - get_by_serial — args: { serial, format?, lang?, gtin? }. Read-only. Addresses the passport by your own serial. A serial is unique only WITHIN a GTIN — if the same serial exists under two GTINs in your account the call returns 409 ambiguous_serial; pass `gtin` (or use the by-id action) to resolve exactly. - compliance — args: { id }. Read-only. Returns a three-tier compliance verdict (compliant | compliant_with_warnings | incomplete) with regulation-cited findings — use to gap-check a passport against the rules for its category, fix the cited fields/parties, then re-check. - registry_readiness — args: { id }. Read-only. Returns { ready, findings[] } — whether the passport would pass the EU DPP Registry's FORMAL submission gate (mandatory fields present, correct formatting, a resolvable public link, item-level granularity via a serial number, and a well-formed commodity code where the category carries one). This is the registry's mechanical pre-submission check, NOT the substantive compliance verdict; a passport can be registry-ready yet not substantively compliant. Battery passports only. - create — args: { productId, gtin, serialNumber, confirmOverage? }. BILLABLE. - suspend — args: { id }. Reversible — public QR shows 'suspended'. - suspend_by_serial — args: { serial, gtin? }. Same as suspend, addressed by your serial. 409 ambiguous_serial if the serial isn't unique in your account — pass `gtin`. - archive — args: { id }. IRREVERSIBLE — confirm with the user first. - archive_by_serial — args: { serial, gtin? }. IRREVERSIBLE, addressed by your serial — confirm first. 409 ambiguous_serial if the serial isn't unique — pass `gtin`. - get_qr — args: { id, format? (svg|png) }. Read-only. - get_qr_by_serial — args: { serial, format? (svg|png), gtin? }. Read-only. Same as get_qr, addressed by your own serial. A serial is unique only WITHIN a GTIN — if the same serial exists under two GTINs in your account the call returns 409 ambiguous_serial; pass `gtin` (or use get_qr by id) to resolve exactly.tracepass_passport_fieldsUpdate field values on a Digital Product Passport. Every change is recorded in the passport's audit trail, tagged as an API-key update. Actions (pass via `action`, with `args`): - update — args: { id, fieldKey, value }. `value` type matches the field's dataType (string, number, boolean, array, object). - update_by_serial — args: { serial, fieldKey, value, gtin? }. Same as update, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in your account the call returns 409 ambiguous_serial; pass `gtin` (or use update by id) to resolve exactly.tracepass_passport_partiesManage the economic-operator parties on a passport — manufacturer, importer, authorisedRepresentative, distributor, recycler, producerResponsibilityOrg. Each party carries a legal name and ideally a validated 13-digit GS1 GLN. Actions (pass via `action`, with `args`): - set — args: { id, role, legalName, gln?, country?, legacyOperatorId? }. Sets or updates one role. - remove — args: { id, role }. Clears one role.tracepass_epcisGS1 EPCIS 2.0 supply-chain events. `export` is included on Starter plans and up; `capture`, `capture_job`, and `query` require the paid EPCIS add-on (those actions return a 403-style message without it). Actions (pass via `action`, with `args`): - export — args: { id }. Export a passport's events as an EPCIS 2.0 JSON-LD document. Read-only. - export_by_serial — args: { serial, gtin? }. Same as export, addressed by your own serial. A serial is unique only WITHIN a GTIN — if it isn't unique in your account the call returns 409 ambiguous_serial; pass `gtin` (or use export by id). Read-only. - capture — args: { events }. `events` is an EPCISDocument, a single event, or an array of events (JSON-LD). Returns a 202 with a captureJobId. - capture_job — args: { jobId }. Poll an async capture job. Read-only. - query — args: { params? }. `params` is a key/value map of standard EPCIS query parameters (EQ_bizStep, GE_eventTime, MATCH_epc, …). Read-only.tracepass_templatesDiscover the regulatory field schema for each DPP category — what a COMPLIANT passport must contain, per the governing EU regulation. Read-only reference data. Use this to advise on requirements before creating products/passports, and to gap-check a draft against the rules. Actions (pass via `action`, with `args`): - list — args: {}. Lists all 13 categories with their field count, required-field count, and governing regulation (name + number + effective/mandatory dates). - get — args: { category }. Full field schema for one category: every field's key, label, dataType, whether it is REQUIRED, its access level (public/restricted/authority), enum options, validation bounds, and — where known — the regulation article/annex that mandates it. `category` is one of: battery, textile, electronics, construction, steel, detergents, paints-coatings, packaging, furniture, tyres, jewelry, toys, fmcg. BATTERY — required-ness is per-category, so `required` alone is the wrong answer. Resolve it in this order: 1. SCOPE FIRST. Only EV, LMT and industrial_gt_2kwh batteries owe a passport at all (Art. 77(1), Reg (EU) 2023/1542). For portable, SLI or industrial_lte_2kwh, NO field is required — do not list mandatory fields for them; say the battery is out of scope. 2. Then `requiredBy[batteryCategory]` where the field carries that map (required | conditional | notApplicable). 3. Then fall back to `required`. The map is keyed ONLY by the three in-scope categories, so skipping step 1 falls through to `required` and invents an obligation the Regulation does not impose. Note also that EV and LMT report state-of-health through MUTUALLY EXCLUSIVE field sets — an EV battery must leave the remaining-capacity cluster empty and an LMT battery must leave stateOfCertifiedEnergy empty, so no single battery ever fills every field.
Predictive Maintenance MCP Server tools 34
list_signalsList signal files on disk or signals loaded in the repository. scope='disk' (default): files under data/signals/ that load_signal can open — use before loading. scope='memory': signals currently cached in the in-memory repository with their metadata (signal_id, sampling_rate, declared unit) — use to see which signal_ids are available for analysis. Args: ctx: MCP context. Unused — see this module's docstring on logging. scope: 'disk' for loadable files, 'memory' for loaded signal_ids. Returns: Dict with scope, count, and either 'files' (relative paths, disk) or 'signals' (StoredSignalInfo entries, memory).generate_test_signalGenerate a synthetic test signal, save it, and load it into the repository. The signal is written to data/signals/ with a timestamped filename and a companion _metadata.json declaring sampling_rate and signal_unit='g' (synthetic acceleration), then auto-registered in the repository — the returned signal_id is immediately usable by every analysis, diagnosis, and ISO severity tool with no manual steps. Signal content: 'bearing_fault' = 10 Hz impacts modulating a 1 kHz carrier; 'gear_fault' = 200 Hz mesh tone + harmonics; 'imbalance' = 25 Hz (1500 RPM) tone; 'normal' = broadband noise. Args: signal_type: Synthetic fault pattern to generate. duration: Signal duration in seconds (10 s gives 0.1 Hz resolution). sampling_rate: Sampling frequency in Hz. noise_level: Additive white-noise amplitude. random_seed: Seed for reproducible noise (None = non-deterministic). ctx: MCP context. Unused — see this module's docstring on logging. Returns: StoredSignalInfo of the auto-loaded signal (signal_id, declared sampling_rate and unit 'g').load_signalLoad one signal — or a batch — into the in-memory repository. Once loaded, reference the signal by its signal_id in every analysis, diagnosis, report, and prognostics tool (the load -> analyze -> diagnose -> report flow uses signal_id as the single handle). Batch form: pass a LIST of file paths (e.g. for training sets). The batch is fail-fast and atomic — all paths and derived ids are validated up front, and on the first problem ONE error names the offending entries and nothing is loaded. One declared sampling_rate/ signal_unit applies to all files; per-file metadata wins only when the parameter is omitted. Custom signal_id is not allowed for a batch (ids derive from each file's relative path). signal_id default: the path relative to data/signals/ with separators replaced by underscores — 'real_train/baseline_1.csv' loads as 'real_train_baseline_1', so same-named files in different folders never collide silently. Re-loading a path whose id already exists is an explicit error unless overwrite=True. Signal unit discipline: ISO 20816-3 severity verdicts require a DECLARED unit — either via this parameter or a 'signal_unit' field in the companion _metadata.json (explicit parameter wins). Units are never guessed from signal amplitude; without a declared unit the ISO severity block is refused with a structured reason and remedy. Raw binary files (.bin/.raw/.dat): a headerless raw waveform loads only with a declared decode contract — sample_format AND sampling_rate are REQUIRED, either as explicit parameters here or as fields of the companion <stem>_metadata.json next to the file (explicit parameter wins). The other raw parameters carry documented defaults, applied by the repository after that merge: byte_order 'little', n_channels 1, channel_index 0, header_offset 0, no scale_factor. Integer sample formats (int16/int32) decode to raw ADC counts — declare scale_factor to convert counts into the declared physical unit (there is no implicit normalization). In a batch the raw parameters broadcast to ALL files, exactly like sampling_rate. Declaring raw parameters for a self-describing format (.csv, .npy, ...) is refused as a contradiction. With n_channels > 1 each load extracts ONE channel and the DERIVED id gains a _ch<channel_index> suffix; an explicit signal_id is used verbatim — no suffix applies. Args: ctx: MCP context. Unused — see this module's docstring on logging. filepath: Filename relative to data/signals/ or absolute path — or a list of such paths for an atomic batch load. signal_id: Custom ID (single-file loads only; default derives from the relative path). sampling_rate: Sampling rate in Hz (overrides metadata file). Required for raw binary files (here or in the companion). signal_unit: Declared signal unit — 'g' or 'm/s2' (acceleration), 'mm/s' or 'm/s' (velocity). Overrides the metadata file. overwrite: Replace existing entries on signal_id collision instead of raising. sample_format: Raw files only — declared sample dtype ('float32', 'float64', 'int16', 'int32'). REQUIRED for .bin/.raw/.dat (here or in the companion metadata). byte_order: Raw files only — declared endianness ('little' or 'big'); documented default 'little'. n_channels: Raw files only — interleaved channel count in the file; documented default 1. channel_index: Raw files only — 0-based channel to extract; documented default 0. header_offset: Raw files only — bytes to skip before the first sample; documented default 0. scale_factor: Raw files only — optional multiplier applied after decoding (e.g. ADC counts -> physical unit); default: no scaling. Returns: StoredSignalInfo for a single load; a list of StoredSignalInfo (input order) for a batch. Raw loads record the effective decode parameters under raw_format. Raises: ValueError: If signal_unit is invalid, the signal data cannot be loaded, a signal_id collides without overwrite=True, a batch contains any invalid entry (nothing is loaded), a raw binary file is missing a required declaration (ONE message names everything missing plus both remedies), or raw parameters are declared for a self-describing format.get_signal_infoGet metadata for a stored signal without loading the full array. Includes the COMPLETE companion-metadata dict (source_metadata: rpm/ shaft_speed, reference frequencies, ...) alongside the repository fields (sampling_rate, declared signal_unit, shape, timestamps). Args: ctx: MCP context. Unused — see this module's docstring on logging. signal_id: ID of a signal previously loaded via load_signal. Returns: StoredSignalInfo with source_metadata populated from the companion _metadata.json (empty dict when the file has none). Raises: ValueError: If the signal_id is not in the repository.clear_signalsRemove one signal — or all signals — from the in-memory repository. Args: ctx: MCP context. Unused — see this module's docstring on logging. signal_id: ID to remove; None (default) clears the whole cache. Returns: Dict with cleared_count, plus signal_id and status ('removed' or 'not_found') for single-signal calls.analyze_fftPerform FFT (Fast Fourier Transform) analysis on a stored signal. FFT analysis converts the signal from time domain to frequency domain, allowing identification of harmonic components and faults that manifest at specific frequencies. Requires the signal loaded via load_signal() first; the sampling rate comes from the stored signal metadata. By default analyzes the LEADING 1.0-second segment (deterministic: two identical calls return identical results). Set segment_duration=None to analyze the entire signal, or pass random_seed to sample a seeded random segment position instead. Args: ctx: MCP context. Unused — see this module's docstring on logging. signal_id: ID of the stored signal (from load_signal). max_frequency: Maximum frequency to analyze (default: Nyquist frequency) segment_duration: Duration in seconds to analyze (default: leading 1.0 s). Set to None to analyze the full signal. random_seed: Seed for random segment position (default: None = deterministic leading segment). Returns: FFTResult with top peaks, dominant peak, and spectrum stats. Raises: ValueError: If the signal_id is not loaded, or the stored signal has no sampling rate.analyze_envelopeEnvelope-spectrum analysis of a stored signal (bearing fault screening). THE unified envelope tool: bandpass filter -> Hilbert envelope -> mean subtraction + Hann window -> FFT -> top peaks. The mean subtraction/window step is an intentional U9 fix: the envelope's DC leakage used to bury the low-frequency FTF zone. Requires the signal loaded via load_signal() first; the sampling rate comes from the stored signal metadata. The requested band must fit the signal: an invalid band (low <= 0, low >= high, high > Nyquist) raises a ValueError — it is NEVER silently clamped. The band used is echoed in the result. By default analyzes the LEADING 1.0-second segment (deterministic: two identical calls return identical results). Set segment_duration=None to analyze the entire signal, or pass random_seed to sample a seeded random segment position instead. No reference bearing frequencies are assumed: compare the returned peaks against frequencies computed for the actual bearing and shaft speed (check_bearing_faults or calculate_bearing_characteristic_frequencies). Args: ctx: MCP context. Unused — see this module's docstring on logging. signal_id: ID of the stored signal (from load_signal). filter_low: Bandpass low edge in Hz (default: 500). filter_high: Bandpass high edge in Hz (default: 5000). Must not exceed the signal's Nyquist frequency. num_peaks: Number of top peaks to return (default: 5). segment_duration: Duration in seconds to analyze (default: leading 1.0 s). None analyzes the full signal. random_seed: Seed for random segment position (default: None = deterministic leading segment). Returns: EnvelopeResult with the band actually used, top peaks, and comparison guidance. Raises: ValueError: If the signal_id is not loaded, the stored signal has no sampling rate, or the band is invalid vs Nyquist.analyze_statisticsCalculate statistical parameters of a stored signal for diagnostics. Statistical parameters are key indicators for diagnostics: - RMS: Effective value, correlated to signal energy - Crest Factor: Indicates presence of impulses (high = possible faults) - Kurtosis: Measures impulsiveness (excess kurtosis; >0 = non-Gaussian, >3 = strong impulses) - Peak-to-Peak: Signal range Requires the signal loaded via load_signal() first. Statistical parameters are screening indicators, not definitive diagnostics — combine with frequency-domain evidence. **Signal units:** all values are in the signal's native unit. The unit is reported only when DECLARED — load_signal(signal_unit=...) or the companion _metadata.json — and never guessed from signal amplitude. ISO 20816-3 severity tools refuse to produce a verdict until the unit is declared. Args: signal_id: ID of the stored signal (from load_signal). Returns: StatisticalResult with all statistical parameters Raises: ValueError: If the signal_id is not loaded.extract_features_from_signalExtract time-domain features from a stored signal using sliding windows. Segments the signal into overlapping windows and extracts 17 statistical features from each segment. Features include: mean, std, RMS, kurtosis, crest factor, entropy, etc. Requires the signal loaded via load_signal() first; the sampling rate comes from the stored signal metadata. Returns an in-memory summary only — no CSV is written to data/signals/. Args: signal_id: ID of the stored signal (from load_signal). segment_duration: Duration of each segment in seconds (default: 0.1) overlap_ratio: Overlap between segments, 0-1 (default: 0.5 = 50%) ctx: MCP context. Unused — see this module's docstring on logging. Returns: FeatureExtractionResult with features matrix and metadata Raises: ValueError: If the signal_id is not loaded, or the stored signal has no sampling rate. Example: extract_features_from_signal( "healthy_motor", segment_duration=0.2, overlap_ratio=0.5 )compute_power_spectral_densityCompute Power Spectral Density (Welch method) for a stored signal. Requires signal loaded via load_signal() first. Args: signal_id: ID of the stored signal. nperseg: Samples per FFT segment (default 256). noverlap: Overlap between segments (default 128). window: Window function (default 'hann').compute_spectrogram_stftCompute STFT spectrogram for a stored signal. Returns time-frequency summary (no full 2D array). Use for detecting time-varying frequency content (transient faults, speed changes). Args: signal_id: ID of the stored signal. nperseg: Samples per STFT segment (default 256). noverlap: Overlap between segments (default 128). window: Window function (default 'hann').assess_severityAssess vibration severity (ISO 20816-3 zones A-D) and alert level. THE unified severity tool: ISO zone assessment and alert classification in one call. Zone boundary values are those of ISO 10816-3:2009 (ISO 20816-3:2022 merges zones A/B — provenance is noted in the result). Scope: machines rated above 15 kW; a declared machine_power_kw below 15 kW is refused. Input routes (exactly ONE required): - signal_id: a stored signal (load_signal first). Sampling rate AND declared unit come from the stored metadata; an undeclared unit is refused, never guessed from amplitude. - rms_velocity_mm_s: a direct broadband RMS velocity reading in mm/s (e.g. from a portable instrument) — no unit declaration needed. Args: ctx: MCP context. Unused — see this module's docstring on logging. signal_id: ID of the stored signal (mutually exclusive with rms_velocity_mm_s). rms_velocity_mm_s: Direct broadband RMS velocity in mm/s (mutually exclusive with signal_id). machine_group: 1 (large, >300 kW) or 2 (medium, 15-300 kW). Ignored when custom thresholds are given. Default 2. support_type: 'rigid' or 'flexible'. Ignored when custom thresholds are given. Default 'rigid'. thresholds: Optional custom zone boundaries {'warning': A/B, 'alarm': B/C, 'danger': C/D} in mm/s, strictly increasing — replaces the ISO table for this call. machine_power_kw: Rated machine power, if known. Declared values below 15 kW are refused (out of ISO scope); None means unknown and is not refused. rpm: Operating speed in RPM (signal route only: selects the 2 Hz band lower edge below 600 RPM). Returns: VibrationSeverityResult (status='assessed') with zone, severity, boundaries, derived alert_level/exceeded_threshold, and threshold provenance. Raises: ValueError: On route misuse (both/neither inputs), undeclared signal unit, missing sampling rate, Nyquist below the ISO band, declared power below 15 kW, negative RMS, or invalid custom thresholds.- +22 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Tracepass MCP Server
{
"mcpServers": {
"malinoto-tracepass-mcp-server": {
"command": "npx",
"args": [
"-y",
"tracepass-mcp-server"
],
"env": {
"TRACEPASS_API_KEY": "YOUR_TRACEPASS_API_KEY_HERE",
"TRACEPASS_BASE_URL": "YOUR_TRACEPASS_BASE_URL_HERE"
}
}
}
}
Predictive Maintenance MCP Server
{
"mcpServers": {
"predictive-maintenance-mcp-server": {
"command": "uvx",
"args": [
"predictive-maintenance-mcp"
]
}
}
}
Frequently asked questions
Tracepass MCP Server is categorized under Industrial & IoT and uses a local stdio subprocess. Predictive Maintenance MCP Server belongs to Industrial & IoT and uses a local stdio subprocess. Pick Tracepass MCP Server for industrial & iot work and Predictive Maintenance MCP Server for industrial & iot.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Tracepass MCP Server has no declared pricing — check the project's own site. Auth: api key required. Predictive Maintenance MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add malinoto-tracepass-mcp-server and predictive-maintenance-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Tracepass MCP Server has a quality signal of 64/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Predictive Maintenance MCP Server has 63/100 (Good) with 1 views, 0 installs and 105 GitHub stars.