OPC UA NodeSet Gate

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Deterministic release-compatibility preflight for OPC UA NodeSet2 XML.

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "OPC UA NodeSet Gate": {
      "url": "https://nodeset.regevidencehub.com/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (5)

• audit_nodeset_compatibility read-only

  Compare two complete OPC UA NodeSet2 XML documents when both fit in a single request. Pass old_nodeset_xml as the full baseline revision and new_nodeset_xml as the full candidate revision. The deterministic report returns result (COMPATIBLE, REVIEW_REQUIRED, BREAKING, or INSUFFICIENT_INPUT), old_node_count, new_node_count, issue_count, a summary keyed by change code, and issues containing code, severity, node_id and detail. Examples include NODE_ADDED, NODE_REMOVED, DATA_TYPE_CHANGED and reference changes. For large XML documents use begin_nodeset_upload + append_nodeset_chunk for each revision, then audit_uploaded_nodesets instead.

  Parameters:

  • old_nodeset_xml (required) — string
  • new_nodeset_xml (required) — string

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• nodeset_compatibility_status read-only

  Return bounded service metadata for OPC UA NodeSet Compatibility Gate. Use this only to discover deployment stage, deterministic static-analysis scope, production availability and payment status; do not use it to compare NodeSets. The result includes the shared MCP endpoint and explicitly lists which tool calls are free and which require x402 payment.

  Hints: read-only yes · destructive no · idempotent yes · open-world no

• begin_nodeset_upload

  Start one temporary in-memory upload for a large NodeSet2 XML document. Call this once for the old baseline and once for the new candidate when the complete XML documents are too large for audit_nodeset_compatibility. It returns upload_id and max_total_chars. Append that document's chunks in original order with append_nodeset_chunk. Uploads expire after 15 minutes and the service allows at most four active uploads; this tool stores only temporary process memory and does not modify an external system.

  Hints: read-only no · destructive no · idempotent no · open-world no

• append_nodeset_chunk

  Append the next unmodified text chunk to a temporary NodeSet2 upload created by begin_nodeset_upload. Pass upload_id exactly as returned by begin_nodeset_upload and chunk as the next consecutive XML text segment; send every chunk in original order without overlap, omission or reformatting. On success the result returns status=OK, upload_id and cumulative received_chars; UNKNOWN_UPLOAD_ID or UPLOAD_TOO_LARGE indicates the upload cannot continue. This tool only stages XML in temporary memory and does not parse or compare it yet.

  Parameters:

  • upload_id (required) — string
  • chunk (required) — string

  Hints: read-only no · destructive no · idempotent no · open-world no

• audit_uploaded_nodesets destructive

  Compare two large NodeSet2 XML revisions after both have been fully staged with begin_nodeset_upload and append_nodeset_chunk. Pass old_upload_id for the baseline revision and new_upload_id for the candidate revision. This call consumes both upload IDs, so do not reuse them afterward. The report has the same shape as audit_nodeset_compatibility: result (COMPATIBLE, REVIEW_REQUIRED, BREAKING, or INSUFFICIENT_INPUT), old/new node counts, issue_count, summary by change code, and issues with code, severity, node_id and detail. Use the direct audit tool instead when both complete XML documents fit in a single request.

  Parameters:

  • old_upload_id (required) — string
  • new_upload_id (required) — string

  Hints: read-only no · destructive yes · idempotent no · open-world no

Repository

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.