edt-bridge-mcp@0.36.0
VERIFIED· not startedPublisher claims: "stdio MCP front-end for the edt-bridge 1C:EDT plugin: EDT's own diagnostics, metadata and types, query validation, write tools, infobases and a debugger; proxies to a running EDT, or auto-starts a headless one" 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try edt-bridge-mcp` runs it now and prints the full answer.
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-06 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
child = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.raw = subprocess.run(["powershell", "-NoProfile", "-Command", query],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.self._headless_process = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.run(["ps", "-eo", "pid=,ppid=,args="], capture_output=True, text=True,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.process = subprocess.Popen(argv, cwd=log.parent, env=env, stdin=subprocess.DEVNULL, stdout=output,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.raw = subprocess.run(["powershell", "-NoProfile", "-Command", query],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."en": "kill the headless session when it does not stop within the timeout",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# so without it the shell reports - and force would kill - its own process.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.state, output = tmp_path / "state.json", tmp_path / "output.log"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."description": "kill the headless session when it does not stop in time "Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."p=subprocess.Popen(json.loads(sys.argv[1]),stdin=subprocess.DEVNULL,"Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.The manual routine this replaces is: find 1cedtcli in the task manager, kill it, start EDT. So theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(["taskkill", "/PID", str(pid), "/T", "/F"],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.out = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.state, output = tmp_path / "state.json", tmp_path / "output.log"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.search let shutdown --force for one bridge kill the EDT of another. The workspace is theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.line is already handled as non-JSON, and a log message must never kill the process.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run([sys.executable, "-c", parent, json.dumps(command)],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.state, output = tmp_path / "state.json", tmp_path / "output.log"Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.manager. Without --force the command says which pids are left rather than kill them."""Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""The keepalive shell goes first - it is the CLI's parent, so a tree kill from belowFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.run = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.looking for the text `subprocess.run(` at the head of a call looks straight past a callableFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."rerun with --force to kill it")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.holder = subprocess.Popen([sys.executable, "-c", code, str(lock)], stdin=subprocess.PIPE,Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(argv, capture_output=True, text=True, encoding="utf-8",Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.run = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 edt-bridge-mcp@0.36.0 as of 8d ago. This is the package itself, not its dependencies.