mcp-bitbucket-dc@1.0.1
CAUTION· not startedPublisher claims: "MCP server for Bitbucket Data Center — code search, file browsing, PRs, commits, and more." 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
Code inventory arrives with this version's next honeypot run.- It will ask for
- unknown until the next run
- Where it talks to
- unknown until the next run
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Not enough was observed to say yet. Not started: dependency install failed; the server itself was not observed. This version's code has not been inventoried for credentials and hosts either; both arrive with its next honeypot run (popular servers first). `vet-skills try mcp-bitbucket-dc` runs it now and prints the full answer.
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-07 and scored it 73/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: References a credential file in the home directory; Privileged sudo command; 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
gh repo deploy-key add ~/.ssh/id_rsa.pub \Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.curl -fsSL https://cli.github.com/packages/githubcli-archive-keyring.gpg | sudo dd of=/usr/share/keyrings/githubcli-archive-keyring.gpgFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.gh gpg-key add ~/.ssh/id_rsa.pubFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.sudo apt install ghFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/githubcli-archive-keyring.gpg] https://cli.github.com/packages stable main" | sudo tee /etc/apt/sources.list.d/github-cli.lisFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.sudo apt updateFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.gh ssh-key add ~/.ssh/id_rsa.pub --title "My laptop"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.gh ssh-key add ~/.ssh/id_ed25519.pub --type "authentication"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.gh gpg-key add ~/.ssh/id_rsa.pubFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.gh ssh-key add ~/.ssh/id_rsa.pub --title "My laptop"Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.gh repo deploy-key add ~/.ssh/id_rsa.pub \Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.gh ssh-key add ~/.ssh/id_ed25519.pub --type "authentication"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 mcp-bitbucket-dc@1.0.1 as of 35 h ago. This is the package itself, not its dependencies.
What would make this Verified
7 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim christopherekfeldt: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- 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.