Skip to content

OPC UA NodeSet Gate MCP server

io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gateChanghuLiustreamable-httpv0.1.3Scanned

Deterministic release-compatibility preflight for OPC UA NodeSet2 XML.

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

Tools: 1 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 1
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here can delete or cancel things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the OPC UA NodeSet Gate MCP server can do

The OPC UA NodeSet Gate MCP server is published by the GitHub account ChanghuLiu. It has 5 tools. It can delete or cancel things (1 tool: audit_uploaded_nodesets) and create or change data (2 tools: begin_nodeset_upload and append_nodeset_chunk). 2 tools only read.

1 tool reads private data (audit_nodeset_compatibility).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 17, 2026, version 0.1.3.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

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 2Show 2 read-only tools
  • audit_nodeset_compatibilityCompare two complete OPC UA NodeSet2 XML documents when both fit in a single request.Reads private dataNo findings

    Why it is in this group

    • The description's first verb is "compare": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "compare" and "document": it reads documents.
    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.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged untrusted-input or outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:24 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
3
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 destructive, 2 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://nodeset.regevidencehub.com/mcp: tools/list returned 5 tools to an anonymous client, including audit_uploaded_nodesets (destructive), begin_nodeset_upload (write), append_nodeset_chunk (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

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
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 or a way out, 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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as opc-ua-nodeset-compatibility-gate. Review it before you use it.

Capability tags behind 1 rule
  • mcp__opc-ua-nodeset-compatibility-gate__audit_nodeset_compatibility private-data

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate/verify?hash=86a0556cc54a17a9fb5b462780be58fa826d3b73793058def014f204e93ee20a" | jq -e '.changed == false'

Pinned hash 86a0556cc54a, from Nov 17, 2026, 09:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate
[![Anlyon Radar](https://radar.anlyon.com/badge/io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate.svg)](https://radar.anlyon.com/servers/io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate)

Source: MCP Registry · repository. Synced Oct 21, 2026, 18:15 UTC.

OPC UA NodeSet Gate MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the OPC UA NodeSet Gate MCP server safe?

No scan can promise that. What its definitions show: 5 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the OPC UA NodeSet Gate MCP server delete data?

Yes. 1 tool can delete, cancel or revoke something: audit_uploaded_nodesets.

Can the OPC UA NodeSet Gate MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the OPC UA NodeSet Gate MCP server have?

5 tools: 1 destructive, 2 write, 2 read. audit_uploaded_nodesets, begin_nodeset_upload, append_nodeset_chunk, audit_nodeset_compatibility and nodeset_compatibility_status.

Does the OPC UA NodeSet Gate MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the OPC UA NodeSet Gate MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the OPC UA NodeSet Gate MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 17, 2026.