opcua-mcp-server@0.6.0
VERIFIED· not startedPublisher claims: "MCP server exposing OPC UA read/write/browse/method/history tools (MCPServer + python-opcua)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
OPCUA_PASSWORDor--store-password-in-configConfiguration, not credentials: OPCUA_SERVER_URL- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for OPCUA_PASSWORD and talks to its vendor. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-13 and scored it 82/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
BEGIN GENERATED: tool-reference from contract/tools.json by packages/server-node/scripts/config-artifacts.mjs. Do not edit by hand: edit the source, then run `nFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.* :func:`plan_write` — ``tests/fixtures/write-plan.json``: send this node's writeFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.lines += ["", f"[mcp_servers.{SERVER_KEY}.env]"]Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.f"(mode {_octal(info.st_mode)}); chmod 600 it"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.BEGIN GENERATED: config-reference from contract/config.json by packages/server-node/scripts/config-artifacts.mjs. Do not edit by hand: edit the source, then runFix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent."chmod 600 it"Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for opcua-mcp-server@0.6.0 as of 19 h ago. This is the package itself, not its dependencies.