mseep-mcp-openstack-ops@0.0.0
VERIFIED· not startedPublisher claims: "OpenStack operations automation MCP server" 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
OS_AUTH_HOSTOS_AUTH_PORTOS_PASSWORDREMOTE_AUTH_ENABLEREMOTE_SECRET_KEYConfiguration, not credentials: ALLOW_MODIFY_OPERATIONS, FASTMCP_HOST, FASTMCP_PORT, FASTMCP_TYPE, MCP_LOG_LEVEL, OS_COMPUTE_PORT, OS_HEAT_STACK_CFN_PORT, OS_HEAT_STACK_PORT, OS_IDENTITY_API_VERSION, OS_IMAGE_PORT, OS_NETWORK_PORT, OS_PLACEMENT_PORT, OS_PROJECT_DOMAIN_NAME, OS_PROJECT_NAME, OS_REGION_NAME, OS_USER_DOMAIN_NAME, OS_USERNAME, OS_VOLUME_PORT- 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 OS_AUTH_HOST, OS_AUTH_PORT, OS_PASSWORD, REMOTE_AUTH_ENABLE, REMOTE_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-12 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
logger.error("Please ensure your .env file contains OpenStack authentication credentials")Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.To enable modify operations, set the following in your .env file:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.logger.error("Please check your OpenStack credentials in .env file")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 mseep-mcp-openstack-ops@0.0.0 as of 2d ago. This is the package itself, not its dependencies.