power-hmc-mcp@0.7.1
VERIFIED· not startedPublisher claims: "MCP server for IBM Power HMC partition and capacity operations" 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
HMC_PASSWORDConfiguration, not credentials: HMC_OTEL_ENDPOINT- Where it talks to
- no vendor host named in the codeAlso ibm.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 ibm.com as well as its own vendor. The guard injects HMC_PASSWORD only into requests to the host you bind (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-15 and scored it 86/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
env_file=".env",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# _env_file=None prevents Pydantic from reading a real .env on disk,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Copy `.env.example` to `.env` and set HMC connection variables before running the server. Full env reference: [`docs/operations.md`](docs/operations.md#configuration-reference).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.3. Document the new ``HMC_PROVIDER`` value in ``.env.example`` andFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.docker run --rm \Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""HMC connection settings loaded from environment variables or a .env file."""Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.&& rm -rf /var/lib/apt/lists/*Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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 power-hmc-mcp@0.7.1 as of 2 h ago. This is the package itself, not its dependencies.