mcp@0.0.1-beta.14752
VERIFIED· startup onlyPublisher claims: "Product Brain — MCP server for AI-assisted product knowledge management" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
API_KEY_FORMAT_LINEAPI_KEY_PREFIXOAUTH_REDIRECT_HOST_ALLOWLISTPRODUCTBRAIN_API_KEYConfiguration, not credentials: AGENT_KEY_PREFIX, CLAUDE_CODE_SESSION_ID, CODEX_TUI_SESSION_LOG_PATH, CONNECT_PAGE_PATH, CONVEX_FALLBACK_URLS, CONVEX_SITE_URL, CORS_ORIGINS, CURSOR_CONVERSATION_ID, MCP_DEBUG, MCP_PORT, PB_CONVERSATION_ID, PRODUCTBRAIN_APP_URL, PRODUCTBRAIN_URL- Where it talks to
- productbrain.io (its own)Also claude.ai, claude.com, chatgpt.com, cursor.com, partner.example — 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
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names claude.ai, claude.com, chatgpt.com, cursor.com, partner.example as well as its own vendor. The guard injects API_KEY_FORMAT_LINE, API_KEY_PREFIX, OAUTH_REDIRECT_HOST_ALLOWLIST, PRODUCTBRAIN_API_KEY only into requests to productbrain.io (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; startup only; authenticated tool behavior not tested) on 2026-11-11 and scored it 80/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 · 31 s · 2 scenarios · 0 deviationsStatic findings
const apiKey = await prompt(` Paste your API key (${API_KEY_PREFIX} or ${AGENT_KEY_PREFIX}): `);Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`API key is valid but no workspace is associated. Run \`npx ${MCP_NPX_PACKAGE} setup\` or regenerate your key.`Fix: Pin versions and sources; vendor anything fetched at install time.const envPath = resolve(process.cwd(), ".env.mcp");Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.".env.mcp.example"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 @productbrain/mcp@0.0.1-beta.14752 as of 3d ago. This is the package itself, not its dependencies.