superproductivity-mcp@2.2.1
CAUTION· not startedPublisher claims: "Superproductivity MCP server for Claude Desktop integration" 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: Caution 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
- no credential variables read in the code
- 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 under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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-19 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Access to sensitive file paths; Access to sensitive file paths; Access to sensitive file paths. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
_.file = ".env"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Modes (detected from .env on every spawn):Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Credential loading is anchored to Path.cwd()/.env — never __file__.Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.degraded No .env found → returns setup guidance from all toolsFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Add to `.env`:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.cp .env.example .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.mise trust # required once per clone — allows mise to auto-source .envFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.to prod when .env appears (two-pass transition).Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.Then use the `reload_mcp` tool in Claude Code to hot-reload after source changes — no session restart needed.Fix: Pin versions and sources; vendor anything fetched at install time.prod .env present → uvx superproductivity-mcpFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."description": "Hot-reload the MCP server from local source without disconnecting Claude Code.",Fix: Pin versions and sources; vendor anything fetched at install time.git add scripts/mcp-proxy.py .mcp.json mise.toml .env.example CLAUDE.md .gitignoreFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.return subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.await this.log(`Event send failed: ${e.message}`, 'warn');Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.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 superproductivity-mcp@2.2.1 as of 10 min ago. This is the package itself, not its dependencies.
What would make this Verified
3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim ben-elliot-nice: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Auto-update or dynamic fetch configuration≈ +4 on the totalPin versions and sources; vendor anything fetched at install time.
- Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
- File type combined with upload action≈ +2 on the totalRemove the call, or declare the host in frontmatter and explain in the README what is sent and why.