# Node Opcua Modeler MCP server

Source: https://glimind.com/server/mcp-registry%2Fio.github.node-opcua%2Fnode-opcua-modeler-mcp-server
Registry id: `mcp-registry/io.github.node-opcua/node-opcua-modeler-mcp-server`
Status: live (checked 2026-10-27T02:27:59.818Z)

## Verdict

Node Opcua Modeler MCP server answered 99.95% of Glimind's liveness checks over 30 days, better than 35% of MCP servers, with 1517 ms median handshake and 3 outages in 90 days. Its agent-readiness grade is A (96/100) across 12 tools, costing an agent about 2,082 tokens to load. Checked every few minutes; no tool is ever called.

## Measurements (30 days)

| Metric | Value | Better than |
|---|---|---|
| Uptime, 30 days | 99.95% | 35% of MCP servers |
| Median handshake latency | 1517 ms | 9% of MCP servers |
| p95 handshake latency | 3669 ms | — |
| Checks in 30 days | 4,927 | — |
| Outages, 90 days | 3 | — |
| Median recovery | 5 min | — |
| Agent-readiness score | 96/100 (A) | 82% of MCP servers |
| Tools | 12 | — |
| Tool-list size for an agent | ~2,082 tokens | 52% of MCP servers |
| Days observed | 29 | — |

## Install

```json
{
  "mcpServers": {
    "node-opcua-modeler-mcp-server": {
      "type": "http",
      "url": "https://api.opcua-modeler.sterfive.io/api/mcp"
    }
  }
}
```

Claude Code:

```sh
claude mcp add --transport http node-opcua-modeler-mcp-server https://api.opcua-modeler.sterfive.io/api/mcp
```

## Tools (12)

- `find_engineering_unit`: 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.
- `find_reusable_block`: Find reusable Interfaces / AddIns by capability — pass a member name or keyword (e.g. "SerialNumber", "DeviceHealth", "Location") and get the standard blocks th
- `get_dsl_reference`: 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
- `get_type_details`: Get detailed information about a specific type: its components, properties, methods, interfaces, and optional members. Use this to understand a type's structure
- `list_namespaces`: 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.
- `list_types`: List ALL ObjectTypes, VariableTypes, and InterfaceTypes defined in a specific companion spec namespace. ALWAYS call this before using any type from a namespace 
- `opcua_model_create`: 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 rel
- `opcua_model_generate`: 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 re
- `opcua_model_reverse`: 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 names
- `opcua_model_validate`: Validate an OPC UA YAML model for correctness. Returns diagnostics with severity (error/warning/info), codes, messages, and line numbers. Works without an API k
- `resolve_dependencies`: 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 b
- `search_types`: 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

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.