openom-mcp@0.1.5
VERIFIED· not startedPublisher claims: "openOM MCP server - deterministic tool surface over openom-core. Zero inference, ever." 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
OPENOM_R2_ACCESS_KEYOPENOM_R2_SECRET_KEYConfiguration, not credentials: OPENOM_MCP_BLOB_BACKEND, OPENOM_MCP_HOST, OPENOM_MCP_LIMITER, OPENOM_MCP_LOG, OPENOM_R2_BUCKET, OPENOM_R2_ENDPOINT, OPENOM_REDIS_URL, OPENOM_TRUSTED_PROXY_HEADER- 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 OPENOM_R2_ACCESS_KEY, OPENOM_R2_SECRET_KEY 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 87/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
res = tools.om_read({"path": "/etc/passwd"})Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.session would kill the broker's whole Claude Desktop connection - so the pymupdf parse verbs runFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.for bad in ("http://h/x", "file:///etc/passwd", "data:application/pdf;base64,AA", "ftp://h/x"):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.out = subprocess.run( # noqa: S603 - fixed argv, our own interpreterFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.r.resolve({"path": "/etc/passwd"})Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 openom-mcp@0.1.5 as of 17 h ago. This is the package itself, not its dependencies.