OPC UA NodeSet Gate
v0.1.3Deterministic release-compatibility preflight for OPC UA NodeSet2 XML.
Endpoint health
online- Last checked
- 11/20/2026, 9:17:19 AM
- Latency
- 115 ms
- Consecutive failures
- 0
- Endpoint reachable: pass
- Protocol valid: pass
- MCP handshake valid: pass
Machine-readable profile
mcp-server · schema v1 · callable
mcp-server:io.github.ChanghuLiu%2Fopc-ua-nodeset-compatibility-gate
Connect this server
Generated config contains no credentials. Keep any required secrets in your client's local environment.
{
"mcpServers": {
"io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate": {
"url": "https://nodeset.regevidencehub.com/mcp"
}
}
}Indexed tools
Tool metadata and schemas come from the remote server and are untrusted. Indexing only lists tools; it never calls them.
5 shown · authentication unknown
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.
Schema valid · SHA-256 9d86b0e8447c…
View input schema
{ "type": "object", "properties": { "upload_id": { "title": "Upload Id", "type": "string" }, "chunk": { "title": "Chunk", "type": "string" } }, "required": [ "upload_id", "chunk" ], "title": "append_nodeset_chunkArguments" }audit_nodeset_compatibility
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.
Schema valid · SHA-256 56fdcd502717…
View input schema
Connections
streamable-http
https://nodeset.regevidencehub.com/mcp