OPC UA NodeSet Gate
io-github-changhuliu-opc-ua-nodeset-compatibility-gate declares 5 capabilities across 5 tools, with 2 critical issues.
Issues
5 of 5 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.
1 tool is classified as irreversible and declares no limit.
5 of 5 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.
5 of 5 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.
2 tools can modify data and declare no limit.
2 tools can read data and declare no limit.
Declared capabilities
| Tool | Read as | Basis |
|---|---|---|
audit_nodeset_compatibility | read |
declared |
nodeset_compatibility_status | read |
declared |
begin_nodeset_upload | write |
inferred |
append_nodeset_chunk | write |
inferred |
audit_uploaded_nodesets | destructive |
declared |
Record history
| Recorded | Exposure | Source |
|---|---|---|
| 2026-10-11 | 30 | tools/list on https://nodeset.regevidencehub.com/mcp, published in the official MCP registry as io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate 0.1.3 |
tools/list response and it will be re-scored and dated.
Corrections are published alongside the original, not in place of it.