Skip to content

OPC UA NodeSet Gate

by ChanghuLiu · remote · no sign-in to list tools · v0.1.3 · published by GitHub user ChanghuLiu

Deterministic release-compatibility preflight for OPC UA NodeSet2 XML.

Deletes · 1Changes · 2
CompareRegistry entry

5 tools: 1 can delete or cancel things, 2 change things and 2 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http opc-ua-nodeset-compatibility-gate https://nodeset.regevidencehub.com/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

5 tools

Deletes or cancels 1Claude Code: deny
  • audit_uploaded_nodesetsCompare two large NodeSet2 XML revisions after both have been fully staged with begin_nodeset_upload and append_nodeset_chunk.No findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.
    • The server marks it destructive (destructiveHint: true).
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Audit uploaded NodeSets
    • readOnlyHint: false
    • destructiveHint: true
    • idempotentHint: false
    • openWorldHint: false
Changes things 2Claude Code: ask
  • append_nodeset_chunkAppend the next unmodified text chunk to a temporary NodeSet2 upload created by begin_nodeset_upload.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Append NodeSet upload chunk
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • begin_nodeset_uploadStart one temporary in-memory upload for a large NodeSet2 XML document.No findings

    Why it is in this group

    • The name "begin_nodeset_upload" says "upload": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Begin NodeSet upload
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 2Claude Code: allow
  • audit_nodeset_compatibilityCompare two complete OPC UA NodeSet2 XML documents when both fit in a single request.No findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Audit NodeSet compatibility
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • nodeset_compatibility_statusReturn bounded service metadata for OPC UA NodeSet Compatibility Gate.No findings

    Why it is in this group

    • The name "nodeset_compatibility_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: NodeSet compatibility status
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.3. Values in angle brackets are yours to fill in.

claude mcp add --transport http opc-ua-nodeset-compatibility-gate https://nodeset.regevidencehub.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__opc-ua-nodeset-compatibility-gate__audit_nodeset_compatibility",
      "mcp__opc-ua-nodeset-compatibility-gate__nodeset_compatibility_status"
    ],
    "ask": [
      "mcp__opc-ua-nodeset-compatibility-gate__begin_nodeset_upload",
      "mcp__opc-ua-nodeset-compatibility-gate__append_nodeset_chunk"
    ],
    "deny": [
      "mcp__opc-ua-nodeset-compatibility-gate__audit_uploaded_nodesets"
    ]
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as opc-ua-nodeset-compatibility-gate. Review it before you use it.