origin-mcp@0.1.4
VERIFIED· not startedPublisher claims: "Local MCP server that lets AI assistants automate Origin/OriginPro for data import, worksheet editing, plotting, analysis, and export on Windows." 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
ORIGIN_MCP_BRIDGE_TOKENConfiguration, not credentials: ORIGIN_MCP_ALLOWED_ROOTS, ORIGIN_MCP_BRIDGE_HANDSHAKE, ORIGIN_MCP_BRIDGE_HOST, ORIGIN_MCP_BRIDGE_MAX_TASKS, ORIGIN_MCP_BRIDGE_PORT, ORIGIN_MCP_BRIDGE_STATUS, ORIGIN_MCP_BRIDGE_TIMEOUT, ORIGIN_MCP_DEBUG, ORIGIN_MCP_KEEP_EXTERNAL, ORIGIN_MCP_LOG_FILE, ORIGIN_MCP_NATURE_PALETTE, ORIGIN_MCP_PALETTE, ORIGIN_MCP_TEMPLATE_DIR, ORIGIN_MCP_TOOL_PROFILE- Where it talks to
- originlab.com (its own)Also lcpmgh.com — not the publisher's domain; check what for before connecting.
- 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, and read the third-party hosts first. The code names lcpmgh.com as well as its own vendor. The guard injects ORIGIN_MCP_BRIDGE_TOKEN only into requests to originlab.com (and its subdomains) and refuses the rest.
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-14 and scored it 89/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
result = subprocess.run(check.command, cwd=ROOT, check=False)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."a structured smoke-report.json with origin_doctor output on failure. For "Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.result = subprocess.run(command, cwd=ROOT, text=True, check=False)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(check.command, cwd=ROOT, check=False)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 origin-mcp@0.1.4 as of 4 h ago. This is the package itself, not its dependencies.