otc-pricing-mcp@0.1.12
VERIFIED· install onlyPublisher claims: "MCP server for Open Telekom Cloud Price Calculator API" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Nothing executable in the bundle ran; the trace covers the install step only.- Tested
- every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
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
GITHUB_TOKENConfiguration, not credentials: METRICS_HOST, METRICS_PORT- Where it talks to
- no vendor host named in the codeAlso otc-service.com, t-systems.com, githubusercontent.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
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names otc-service.com, t-systems.com, githubusercontent.com as well as its own vendor. The guard injects GITHUB_TOKEN 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 (1 scenario; nothing executable in the bundle ran; the trace covers the install step only) on 2026-11-14 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 · 1 scenarios · 0 deviationsStatic findings
"description": "Read key-value pairs from a .env file and set them as environment variables",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.logger.info("mcp_server_starting", transports=["stdio", "sse"], port=port)Fix: Namespace tool names and keep tool descriptions literal; no instructions to the agent inside them.# Two steps so the JSON-report producer can't kill the whole job (#25):Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.opentelekомcloudFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for otc-pricing-mcp@0.1.12 as of 7 h ago. This is the package itself, not its dependencies.