io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate
REMOTE · NODESET.REGEVIDENCEHUB.COM · SCANNED SEP 28
Deterministic release-compatibility preflight for OPC UA NodeSet2 XML.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (audit_uploaded_nodesets). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 195 tokens (~39/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage53
- 80% of tools have a non-trivial description (not blank, and not just the tool's name).Partial
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
How do I install the io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate MCP server?
io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate is a hosted endpoint at https://nodeset.regevidencehub.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · nodeset.regevidencehub.com
claude mcp add --transport http changhuliu-opc-ua-nodeset-compatibility-gate 'https://nodeset.regevidencehub.com/mcp'
{
"mcpServers": {
"changhuliu-opc-ua-nodeset-compatibility-gate": {
"url": "https://nodeset.regevidencehub.com/mcp"
}
}
} {
"servers": {
"changhuliu-opc-ua-nodeset-compatibility-gate": {
"type": "http",
"url": "https://nodeset.regevidencehub.com/mcp"
}
}
} [mcp_servers.changhuliu-opc-ua-nodeset-compatibility-gate] url = "https://nodeset.regevidencehub.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"changhuliu-opc-ua-nodeset-compatibility-gate": {
"type": "remote",
"url": "https://nodeset.regevidencehub.com/mcp",
"enabled": true
}
}
} openclaw mcp add changhuliu-opc-ua-nodeset-compatibility-gate --url 'https://nodeset.regevidencehub.com/mcp' --transport streamable-http
mcp_servers:
changhuliu-opc-ua-nodeset-compatibility-gate:
url: "https://nodeset.regevidencehub.com/mcp" {
"McpServers": {
"changhuliu-opc-ua-nodeset-compatibility-gate": {
"Transport": "http",
"Url": "https://nodeset.regevidencehub.com/mcp"
}
}
} assistant mcp add changhuliu-opc-ua-nodeset-compatibility-gate -t streamable-http -u 'https://nodeset.regevidencehub.com/mcp'
{
"mcpServers": {
"changhuliu-opc-ua-nodeset-compatibility-gate": {
"type": "http",
"url": "https://nodeset.regevidencehub.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 59
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 28 Sept 2026 · Probed https://nodeset.regevidencehub.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nodeset.regevidencehub.com | CN=YR2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | RSA 2048 | SHA256-RSA | 5383b6265f0adee0e71e9ad332573957a96 |
| SANs: nodeset.regevidencehub.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of nodeset.regevidencehub.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| regevidencehub.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://nodeset.regevidencehub.com/mcp | Verified | 200 | |
| http (plaintext) | http://nodeset.regevidencehub.com/mcp | HTTPS enforced | 301 | https://nodeset.regevidencehub.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
append_nodeset_chunk ~45
Append the next text chunk to a temporary NodeSet upload. Send chunks in original order without modification.
| Name | Type | Req | Description |
|---|---|---|---|
| chunk | string | yes | – |
| upload_id | string | yes | – |
No output schema declared.
No examples provided.
audit_nodeset_compatibility ~50
Compare two OPC UA NodeSet2 XML documents and report deterministic release-compatibility changes.
| Name | Type | Req | Description |
|---|---|---|---|
| new_nodeset_xml | string | yes | – |
| old_nodeset_xml | string | yes | – |
No output schema declared.
No examples provided.
audit_uploaded_nodesets ~53
Audit two NodeSets previously uploaded with begin_nodeset_upload and append_nodeset_chunk. Upload IDs are consumed after this call.
| Name | Type | Req | Description |
|---|---|---|---|
| new_upload_id | string | yes | – |
| old_upload_id | string | yes | – |
No output schema declared.
No examples provided.
begin_nodeset_upload ~38
Start a temporary in-memory NodeSet XML upload and return an upload_id. Use for large NodeSets that should be sent in multiple chunks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
nodeset_compatibility_status ~9
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate MCP server?
io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate is an MCP server listed in the public MCP registry as io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate. Deterministic release-compatibility preflight for OPC UA NodeSet2 XML. This page covers its hosted endpoint (https://nodeset.regevidencehub.com/mcp).
Is the io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate MCP server safe to use?
io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate scores 59 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate MCP server expose?
io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate exposes 5 tools: audit_nodeset_compatibility, nodeset_compatibility_status, begin_nodeset_upload, append_nodeset_chunk, audit_uploaded_nodesets. Their descriptions and schemas cost roughly 195 tokens of context every time the server is loaded.
Does the io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate MCP server require authentication?
No. We connected to io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate MCP server still maintained?
io.github.ChanghuLiu/opc-ua-nodeset-compatibility-gate is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.