Skip to main content
Glama
dxpert UNS Tools: Sparkplug B & Unified Namespace Linter for IIoT

dxpert UNS Tools: Sparkplug B & Unified Namespace Linter for IIoT

Official

Related Servers

Alternatives to dxpert UNS Tools: Sparkplug B & Unified Namespace Linter for IIoT

  • A
    license
    A
    quality
    B
    maintenance
    Industry 4.0 / IIoT AI agents for manufacturing: explain OEE losses per shift, triage machine alarms, find downtime root causes, prepare predictive-maintenance jobs and write shift reports from Unified Namespace (UNS), MQTT or historian data. Plus an industrial AI-readiness diagnostic and a vendor-neutral digital-transformation advisor. Works in Claude Code, Codex and any MCP client.
    1
    7
    116 npm
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables validating individual MQTT topic strings against the Sparkplug B topic grammar and reviewing sets of Unified Namespace paths for naming consistency, returning structured findings with pass/fail counts.
    332 npm
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables free, read-only checks of AI agents and MCP servers for conformance, published changes, delivery evidence, and verifiable receipts without requiring an account or API key, using public or non-personal data only.
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP clients to count tokens and estimate costs, run BM25 search, compare model evaluations with paired bootstrap and McNemar tests, validate JSON Schema output, and scan for prompt injection and PII.
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    This MCP server enables AI agents to read MQTT and Sparkplug B data via tools like list_topics, get_latest, and read_all, providing read-only access to latest sensor values.
    1
    MIT

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation4/5

The three tools target distinct capabilities, and the descriptions explicitly cross-reference each other (check_uns_namespace notes it does not validate Sparkplug grammar and points to lint_sparkplug_topic), which strongly reduces misselection. However, lint_sparkplug_topic and check_uns_namespace both operate on MQTT topic strings and could be confused at a glance by an agent skimming names.

Naming Consistency5/5

All three names follow a consistent snake_case verb_noun pattern: lint_sparkplug_topic, check_uns_namespace, run_readiness_diagnostic. The verbs differ (lint/check/run) but each reflects a genuinely different action, and no camelCase or stylistic mixing appears.

Tool Count4/5

Three tools is at the low edge of the well-scoped range but each represents a substantial, distinct capability rather than a thin wrapper. The set is minimal but defensible; the readiness diagnostic sits somewhat apart in domain from the two validators, making the set feel slightly narrow for a general 'tools' server.

Completeness3/5

Coverage is diagnostic-only: you can validate Sparkplug topics, audit UNS naming, and score readiness, but there is no way to normalize/fix namespaces, generate compliant topics, or decode payloads (explicitly excluded). For a toolkit scoped to UNS/Sparkplug diagnostics this is workable, but notable gaps remain around remediation and payload-level checks.

Maintenance

ActivityMaintained
ResponsivenessLimited data