OPC UA Modeler
NPM · NODE-OPCUA-MODELER-MCP-SERVER · 2 COMPONENTS
OPC UA companion spec types, namespace dependencies, and engineering units for AI agents
Available components
Last scanned (12 hours ago)
Scores higher than 94% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to node-opcua/node-opcua-modeler-mcp-server). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 15 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability86
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 952 tokens (~79/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 1 Nov 26 0
- Stability: 0.97 → pass security
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 −1
- Stability: pass → 0.93 functional
- 29 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 28 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/node-opcua-modeler-mcp-server@1.6.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | node-opcua/node-opcua-modeler-mcp-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/node-opcua/node-opcua-modeler-mcp-server/.github/workflows/publish.yml@refs/tags/v1.6.1 |
| Rekor log index | 2617587944 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:bbb6597c7335c5d60be6a277a77166f95787569fd594578cf94cb34ea61f2041ad1caa53606d05efaa55df5526762b258555ec1e52b5061c0d83a8de0 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
find_engineering_unit Find an engineering unit ~73
Find the official UNECE Rec. 20 engineering unit symbol for a given description. ALWAYS call this before using any engineering unit — NEVER guess unit symbols.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Description or common name of the unit (e.g. "revolutions per minute", "celsius", "pressure bar") |
No output schema declared.
No examples provided.
find_reusable_block Find a reusable interface or AddIn ~137
Find reusable Interfaces / AddIns by capability — pass a member name or keyword (e.g. "SerialNumber", "DeviceHealth", "Location") and get the standard blocks that already expose it. PREFER applying/composing an existing block over redefining its members inline. Interfaces are applied with `interfaces:`; addins (types with a DefaultInstanceBrowseName) are composed with `addIns:`. A single property → use the Interface; a whole named sub-object → use the AddIn.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Member name or capability keyword (e.g. "SerialNumber", "health", "calibration") |
No output schema declared.
No examples provided.
get_dsl_reference Get the DSL grammar reference ~58
Get the grammar reference for the OPC UA modeler YAML DSL: file header, top-level sections, name-prefix conventions, minimal examples, and common mistakes. Call this FIRST before writing any YAML model by hand. Works without an API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_type_details Get type details ~89
Get detailed information about a specific type: its components, properties, methods, interfaces, and optional members. Use this to understand a type's structure before creating instances or subtypes.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | Companion spec alias where the type is defined (e.g. "machinery") |
| browseName | string | yes | The type browse name (e.g. "MachineryItemIdentificationType") |
No output schema declared.
No examples provided.
list_namespaces List companion specifications ~39
List all well-known OPC UA companion spec namespace aliases with their full names, URIs, and dependencies. Use this to discover what namespaces are available.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_types List types in a namespace ~67
List ALL ObjectTypes, VariableTypes, and InterfaceTypes defined in a specific companion spec namespace. ALWAYS call this before using any type from a namespace — NEVER guess type names.
| Name | Type | Req | Description |
|---|---|---|---|
| alias | string | yes | Companion spec alias (e.g. "machinery", "di", "robotics") |
No output schema declared.
No examples provided.
opcua_model_create Create a model from a description ~102
Generate an OPC UA YAML model from a natural language description using AI. Requires an API key (set OPCUA_MODELER_API_KEY env var). The AI will auto-detect relevant companion specs, generate a validated model with documentation, and auto-correct validation errors.
| Name | Type | Req | Description |
|---|---|---|---|
| forceSpecs | array | – | Companion spec aliases to force (e.g. ["di", "ia"]) |
| prompt | string | yes | Natural language description of the OPC UA model to generate |
No output schema declared.
No examples provided.
opcua_model_generate Generate NodeSet2 XML ~104
Generate OPC UA NodeSet2.xml and Symbols.CSV from a YAML model. Requires an API key (set OPCUA_MODELER_API_KEY env var). Returns base64-encoded artifacts if the model is valid, or diagnostics if validation fails. Optionally set include_docs=true to also generate markdown documentation.
| Name | Type | Req | Description |
|---|---|---|---|
| include_docs | boolean | – | Set to true to include markdown documentation (slower) |
| yaml | string | yes | The full YAML model source to generate from |
No output schema declared.
No examples provided.
opcua_model_reverse Reverse-engineer NodeSet2 XML ~87
Reverse-engineer a NodeSet2.xml file back into the YAML DSL format. Requires an API key (set OPCUA_MODELER_API_KEY env var). Optionally specify the target namespace URI to extract.
| Name | Type | Req | Description |
|---|---|---|---|
| namespace_uri | string | – | Target namespace URI to extract (auto-detected if omitted) |
| xml | string | yes | The NodeSet2.xml content to reverse-engineer |
No output schema declared.
No examples provided.
opcua_model_validate Validate an OPC UA model ~69
Validate an OPC UA YAML model for correctness. Returns diagnostics with severity (error/warning/info), codes, messages, and line numbers. Works without an API key (limited to 50 calls/day). ALWAYS validate before generating.
| Name | Type | Req | Description |
|---|---|---|---|
| yaml | string | yes | The full YAML model source to validate |
No output schema declared.
No examples provided.
resolve_dependencies Resolve namespace dependencies ~67
Given one or more companion spec namespace aliases, returns the full resolved dependency list that MUST go in the YAML `namespaces:` section. Always call this before generating the namespaces block.
| Name | Type | Req | Description |
|---|---|---|---|
| aliases | array | yes | Companion spec aliases to resolve (e.g. ["machineTool", "robotics"]) |
No output schema declared.
No examples provided.
search_types Search types across specs ~60
Search for types across ALL companion specs by keyword. Use this when you don't know which namespace defines a type. Returns matching types with their namespace alias.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Search keyword (e.g. "identification", "temperature", "motion") |
No output schema declared.
No examples provided.
How do I install the OPC UA Modeler MCP server?
OPC UA Modeler runs locally as an npm package, launched with npx -y node-opcua-modeler-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · node-opcua-modeler-mcp-server
claude mcp add node-opcua-node-opcua-modeler-mcp-server -- npx -y node-opcua-modeler-mcp-server
What is the OPC UA Modeler MCP server?
OPC UA Modeler is an MCP server listed in the public MCP registry as io.github.node-opcua/node-opcua-modeler-mcp-server. OPC UA companion spec types, namespace dependencies, and engineering units for AI agents. This page covers its npm package (node-opcua-modeler-mcp-server).
Is the OPC UA Modeler MCP server safe to use?
OPC UA Modeler scores 91 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OPC UA Modeler MCP server expose?
OPC UA Modeler exposes 12 tools: resolve_dependencies, list_namespaces, list_types, get_type_details, search_types, and 7 more. Their descriptions and schemas cost roughly 952 tokens of context every time the server is loaded.
Is the OPC UA Modeler MCP server still maintained?
OPC UA Modeler is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the OPC UA Modeler MCP server under?
OPC UA Modeler declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.