OPC UA Modeler
REMOTE · API.OPCUA-MODELER.STERFIVE.IO · 2 COMPONENTS
OPC UA companion spec types, namespace dependencies, and engineering units for AI agents
Available components
Last scanned (11 hours ago)
Scores higher than 96% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security77
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1155 tokens (~96/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
- Structured output schemas are declared (8% of tools); any adoption earns full credit.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.
- 22 Oct 26 0
- Server version: 1.6.1 → 1.7.1 functional
- 21 Oct 26 0
- Tool “opcua_model_generate” rewrote its description, which is the text the model reads security
- Schema quality: 84 → 96 ▼ functional
- Tool “opcua_model_generate” now declares an output schema ▲ functional
- First check of Tool coverage: 8 functional
- “opcua_model_generate” added an optional parameter “mode” cosmetic
- “opcua_model_generate” added an optional parameter “symbols_csv” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 0
- Stability: 0.97 → pass security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Tool “get_type_details” rewrote its description, which is the text the model reads security
- 11 Sept 26 0
- “opcua_model_reverse” added an optional parameter “self_contained” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 28 Aug 26 0
- Stability: unverified → 0.03 ▲ 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 · Probed https://api.opcua-modeler.sterfive.io/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.opcua-modeler.sterfive.io | CN=YE2,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 66877c7299839dce6e0f97f4625da8c053e |
| SANs: api.opcua-modeler.sterfive.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.opcua-modeler.sterfive.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| sterfive.io. | present | 58640 | 8 | Verified |
| api.opcua-modeler.sterfive.io. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.opcua-modeler.sterfive.io/api/mcp | Verified | 200 | |
| http (plaintext) | http://api.opcua-modeler.sterfive.io/api/mcp | HTTPS enforced | 308 | https://api.opcua-modeler.sterfive.io/api/mcp |
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 ~117
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. `specRef`, on the type and on a member, is the link to the section of the specification that defines it: cite it.
| 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 ~244
Generate OPC UA NodeSet2.xml and the symbols CSV from a YAML model. Requires an API key (set OPCUA_MODELER_API_KEY env var). NodeIds stay stable only if each regeneration passes back the symbols of the previous one: pass symbols_csv, or mode "new" for a first generation, or mode "renumber" to change ids on purpose. A call with none of these is refused with SYMBOLS_DECISION_REQUIRED. Returns base64-encoded artifacts if the model is valid. The result lists symbol counts (reused/new/dropped), hints and next steps.
| Name | Type | Req | Description |
|---|---|---|---|
| include_docs | boolean | – | Set to true to include markdown documentation (slower) |
| mode | string | – | "new": first generation, no symbols yet. "update": regeneration, symbols required. "renumber": allocate new NodeIds on purpose. Omit when passing symbols. |
| symbols_csv | string | – | The symbols CSV of the previous generation (the content of <name>.model.symbols.csv, or the base64 symbols_csv a previous call returned). Keeps NodeIds stable. |
| yaml | string | yes | The full YAML model source to generate from |
| Name | Type | Req | Description |
|---|---|---|---|
| artifacts | object | – | – |
| diagnostics | array | yes | – |
| files | array | – | – |
| hints | array | yes | – |
| mode | string | yes | – |
| next_steps | array | yes | – |
| symbols | – | yes | – |
| symbols_source | string | yes | – |
| valid | boolean | yes | – |
No examples provided.
opcua_model_reverse Reverse-engineer NodeSet2 XML ~122
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) |
| self_contained | boolean | – | Return one self-contained .opcua.yaml stream: the model, its NodeId symbol table and dependency declarations (default: bare YAML) |
| 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 is a hosted endpoint at https://api.opcua-modeler.sterfive.io/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.opcua-modeler.sterfive.io
claude mcp add --transport http node-opcua-node-opcua-modeler-mcp-server 'https://api.opcua-modeler.sterfive.io/api/mcp'
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 hosted endpoint (https://api.opcua-modeler.sterfive.io/api/mcp).
Is the OPC UA Modeler MCP server safe to use?
OPC UA Modeler scores 88 out of 100 on VerifyMCP. 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 1,155 tokens of context every time the server is loaded.
Does the OPC UA Modeler MCP server require authentication?
No. We connected to OPC UA Modeler without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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.