opcua-modeler

endpoint

https://api.opcua-modeler.sterfive.io/mcp

protocol

streamable-http ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing · is it yours? claim it

karma

0 · newcomer

Is opcua-modeler live?

Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.

Is opcua-modeler free to use?

Yes — the hub reached it with no key and no payment.

What tools does opcua-modeler have?

12 tools: list_types, opcua_model_generate, opcua_model_create, get_type_details, opcua_model_validate, resolve_dependencies, find_reusable_block, search_types, ….

Is opcua-modeler safe to connect?

The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• get_dsl_reference reads open 8h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• list_namespaces reads open 8h ago

  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.

  mcp-tool

  12345

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "properties": {}
  }

  arguments 5 lines copy
• list_types reads unknown 8h ago

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "alias"
    ],
    "properties": {
      "alias": {
        "type": "string",
        "description": "Companion spec alias (e.g. \"machinery\", \"di\", \"robotics\")"
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• opcua_model_generate reads unknown 1h ago

  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.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "yaml"
    ],
    "properties": {
      "yaml": {
        "type": "string",
        "description": "The full YAML model source to generate from"
      },
      "include_docs": {
        "type": "boolean",
        "description": "Set to true to include markdown documentation (slower)"
      }
    },
    "additionalProperties": false
  }

  arguments 18 lines copy
• opcua_model_create reads unknown never probed

  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.

  mcp-tool

  123456789101112131415161718192021

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "prompt"
    ],
    "properties": {
      "prompt": {
        "type": "string",
        "description": "Natural language description of the OPC UA model to generate"
      },
      "forceSpecs": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Companion spec aliases to force (e.g. [\"di\", \"ia\"])"
      }
    },
    "additionalProperties": false
  }

  arguments 21 lines copy
• get_type_details reads unknown 11h ago

  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.

  mcp-tool

  12345678910111213141516171819

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "alias",
      "browseName"
    ],
    "properties": {
      "alias": {
        "type": "string",
        "description": "Companion spec alias where the type is defined (e.g. \"machinery\")"
      },
      "browseName": {
        "type": "string",
        "description": "The type browse name (e.g. \"MachineryItemIdentificationType\")"
      }
    },
    "additionalProperties": false
  }

  arguments 19 lines copy
• opcua_model_validate reads unknown 15h ago

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "yaml"
    ],
    "properties": {
      "yaml": {
        "type": "string",
        "description": "The full YAML model source to validate"
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• resolve_dependencies reads unknown 15h ago

  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.

  mcp-tool

  1234567891011121314151617

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "aliases"
    ],
    "properties": {
      "aliases": {
        "type": "array",
        "items": {
          "type": "string"
        },
        "description": "Companion spec aliases to resolve (e.g. [\"machineTool\", \"robotics\"])"
      }
    },
    "additionalProperties": false
  }

  arguments 17 lines copy
• find_reusable_block reads unknown 15h ago

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Member name or capability keyword (e.g. \"SerialNumber\", \"health\", \"calibration\")"
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• search_types reads unknown 11h ago

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Search keyword (e.g. \"identification\", \"temperature\", \"motion\")"
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• find_engineering_unit reads unknown 1h ago

  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.

  mcp-tool

  1234567891011121314

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "description": "Description or common name of the unit (e.g. \"revolutions per minute\", \"celsius\", \"pressure bar\")"
      }
    },
    "additionalProperties": false
  }

  arguments 14 lines copy
• opcua_model_reverse reads unknown 1h ago

  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.

  mcp-tool

  12345678910111213141516171819202122

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "xml"
    ],
    "properties": {
      "xml": {
        "type": "string",
        "description": "The NodeSet2.xml content to reverse-engineer"
      },
      "namespace_uri": {
        "type": "string",
        "description": "Target namespace URI to extract (auto-detected if omitted)"
      },
      "self_contained": {
        "type": "boolean",
        "description": "Return one self-contained .opcua.yaml stream: the model, its NodeId symbol table and dependency declarations (default: bare YAML)"
      }
    },
    "additionalProperties": false
  }

  arguments 22 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.