DXPert MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to dxpert keyed industrial advisor and UNS agents: Do free allowances and Pro agent permissions remain explicit for the supplied account key?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Industrial AI advisory, UNS agents and diagnostics for manufacturing/IIoT data.

What we know

Authenticated dxpert.ai MCP for curated industrial advisory plus UNS agents/diagnostics and conversion of day-one CSV exports. Public descriptions include OEE loss, alarm triage, downtime RCA, predictive-maintenance prep and shift reporting from UNS/MQTT/historian data.

Maintenance / activity evidence

@dxpert/mcp 0.2.0 published 2026-10-05T02:18:31.559Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Industrial advisory/data-analysis authority; no direct control-system write action established. Complete write authority is not verified.
dxpert API key.
Sensitive access: Industrial operational data, Alarm/OEE/downtime data, API key

Industrial context is high-value/sensitive, but reviewed evidence supports advisory/analysis rather than machine control.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do free allowances and Pro agent permissions remain explicit for the supplied account key?

The bounded review of the publisher's documented dxpert keyed industrial advisor and UNS agents and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Industrial context is high-value/sensitive, but reviewed evidence supports advisory/analysis rather than machine control.
Industrial advisory/data-analysis authority; no direct control-system write action established.
dxpert API key.
Industrial diagnostic/UNS/historian-derived data sent to dxpert APIs where tools call hosted service.
Sensitive access: Industrial operational data, Alarm/OEE/downtime data, API key
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
retention/privacy
full tool inventory
exact CSV conversion behavior
Requires dxpert API key.
Public materials emphasize advisory/analysis; no evidence here of direct PLC/SCADA control writes.
Exact data-retention and detailed per-tool input/output authority remain to be checked.

Original activity observations

@dxpert/mcp 0.2.0 published 2026-10-05T02:18:31.559Z

Technical identity

npm/@dxpert/mcp

Exact implementation source: https://www.npmjs.com/package/@dxpert/mcp ↗
Reviewed resource type: MCP Server
Repository identity: dxpert-ai/dxpert-mcp
Package identity: npm:@dxpert/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry metadata ↗
@dxpert/mcp
Recorded package identity, distribution or download evidence.
Evidence source ↗
www.npmjs.com/~dxpert.ai
Source material retained for this review.
Includes references whose attribution is not established.
GitHub repository ↗
dxpert-ai/dxpert-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
DXPERT_API_KEY required; publisher also provides Codex config TOML.
publisher install or stdio launch · Claude Code only · Publisher instructions
claude mcp add dxpert --env DXPERT_API_KEY="$DXPERT_API_KEY" -- npx -y @dxpert/mcp
Configure / authenticate
MCP100 setup guide
Publisher `claude mcp add dxpert --env DXPERT_API_KEY=<key> -- npx -y @dxpert/mcp`.
Check connection
Suggested check
Use `get_runtime_manifest` read-only to confirm API/version; do not start purchase flow.
Remove / uninstall / revoke
MCP100 setup guide
For a Claude Code registration named `dxpert-mcp`, run `claude mcp remove dxpert-mcp`; otherwise remove the exact entry in the chosen MCP client settings and restart/reconnect. This client-host removal command is MCP100-composed from Claude Code lifecycle documentation, not a vendor-authored uninstall. With `npx`, a separate global package uninstall normally is unnecessary. Do not delete provider data or credentials by default.
Client unregister, package uninstall, data deletion, and OAuth/API token/wallet permissions are distinct.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove dxpert-mcp

Official Documentation & Sources

What it does

Authenticated dxpert.ai MCP for curated industrial advisory plus UNS agents/diagnostics and conversion of day-one CSV exports. Public descriptions include OEE loss, alarm triage, downtime RCA, predictive-maintenance prep and shift reporting from UNS/MQTT/historian data.

Capability: AI & Reasoning
Resource type: MCP Server
Industry: Manufacturing & Industrial
Best fit: Industrial AI advisory, UNS agents and diagnostics for manufacturing/IIoT data.

Representative uses

Ask dxpert industrial advisory questions
Run UNS agents
Run industrial AI-readiness diagnostics
Prepare OEE/alarm/downtime analyses
Convert CSV exports for agent workflows

Limitations

Requires dxpert API key.
Public materials emphasize advisory/analysis; no evidence here of direct PLC/SCADA control writes.
Exact data-retention and detailed per-tool input/output authority remain to be checked.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: dxpert API key.
Permissions: Industrial advisory/data-analysis authority; no direct control-system write action established.
Data handling: Industrial diagnostic/UNS/historian-derived data sent to dxpert APIs where tools call hosted service.
Cost: plan_based
Risk and cautions: Industrial context is high-value/sensitive, but reviewed evidence supports advisory/analysis rather than machine control.

Access scope and cautions

Write actions: Not verified
Sensitive access: Industrial operational data Alarm/OEE/downtime data API key
Risk level: moderate

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Ask dxpert industrial advisory questions; Run UNS agents; Run industrial AI-readiness diagnostics; Prepare OEE/alarm/downtime analyses; Convert CSV exports for agent workflows.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @dxpert/mcp. Recorded transport: stdio. Recorded environment-variable notes: DXPERT_API_KEY; DXPERT_API_BASE (optional). No configuration values are supplied here. Prerequisites: MCP client; dxpert account/key. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: dxp_ API key.

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. Recorded permission context: Industrial advisory/data-analysis authority; no direct control-system write action established.

What data-handling boundary should I consider?

Industrial diagnostic/UNS/historian-derived data sent to dxpert APIs where tools call hosted service. Recorded sensitive-access context: Industrial operational data; Alarm/OEE/downtime data; API key.

What limitations and risks should I check before use?

Industrial context is high-value/sensitive, but reviewed evidence supports advisory/analysis rather than machine control. Requires dxpert API key. Public materials emphasize advisory/analysis; no evidence here of direct PLC/SCADA control writes. Exact data-retention and detailed per-tool input/output authority remain to be checked. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

What cost model is recorded?

The reviewed cost model is plan based. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.