NodeSet Compatibility Gate
Compare an older OPC UA NodeSet2 XML release with a proposed new release. The tool flags modeled structural changes that may affect dependent clients, devices, SDK-generated types, or information models.
Free first step
Use the free MCP status and staged-upload tools to check the service and prepare large baseline/candidate XML documents. There is no browser-based XML audit; preparing an upload does not run the compatibility audit.
Small files can be supplied in one request; larger files can be sent as ordered chunks and audited after upload.
Paid audit
Commercial MCP: $0.005 USDC per compatibility audit. The paid tool returns a payment challenge before running the audit.
No prepaid web package is currently listed. The published payment route is per-call MCP pricing.
What it checks
- Node removal and NodeClass or BrowseName changes
- Variable DataType and ValueRank changes
- Structured DataType Definition changes
- Removed or redirected existing references
- Additive nodes and references, reported as information
Decision boundary
This is a static release-compatibility preflight. It does not connect to or control an OPC UA server, PLC, machine, or process. A COMPATIBLE result means no modeled breaking condition was found; it does not guarantee every downstream consumer will work.
Submit only the XML needed for the comparison. Review the product privacy notice before sending model files.
https://nodeset.regevidencehub.com/mcp · MCP setup & tools · Developer connection guidance